Trust everyone's doing great today. While working with the new version (4) of our beloved ERPNext, I encountered an issue which I'm hoping someone else has been able to find a way around.
Question: how do you get a user with a certain role to see only a portion of a list which is relevant to them? I'll give a common scenario below.
Managers of various departments need to give authorization for several documents (Expense Claims, Leave Applications etc) before it gets to the final approver which could be a General Manager or CEO.
In version 3, all we needed to do was:
1. Insert 'Department' field into relevant docs
2. Create 'Manager' role
3. Add Department value (e.g Sales, HR, Logistics) in user properties for all employees
4. In Permission Manager, select 'Department' as condition for Manager role in the relevant docs.
With these steps, each manager would be able to view and manage documents from employees only within their departments/units. This also ensured that once an employee's department was changed, his new manager would automatically have access to his documents.
How is this achieved in version 4?
Kind regards, Olawale
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
Trust everyone's doing great today. While working with the new version (4) of our beloved ERPNext, I encountered an issue which I'm hoping someone else has been able to find a way around.
Question: how do you get a user with a certain role to see only a portion of a list which is relevant to them? I'll give a common scenario below.
Managers of various departments need to give authorization for several documents (Expense Claims, Leave Applications etc) before it gets to the final approver which could be a General Manager or CEO.
In your previous version, what did Employee select for Approver in their Leave Application or Expense Claim? Was it immediate Manager of employee, or GM/CEO who ultimately approves it? As per the standard approval system Expense Claim and Leave Application, only Approver as defined by the Employee can Approve or Reject request made by Employee.
Assigning role of "Expense Approver" and "Leave Approver" will be suffice, if that manager has authority for Approving or Rejecting.
3. Add Department value (e.g Sales, HR, Logistics) in user properties for all employees .
You should create User Property to define Department for each Employee. User Property to also be created for Manager listing Department they will have access to.
4. In Permission Manager, select 'Department' as condition for Manager role in the relevant docs.
In the upgrade Permission Manager, if "Apply User Permission" is checked in Role Permission Manage for specific Role, all the User Property created for that user will be applied.
If you don't particular User Property applied, you should check "Ignore User Permission" for that field from Customize Form. Check following link for more information on this.
With these steps, each manager would be able to view and manage documents from employees only within their departments/units. This also ensured that once an employee's department was changed, his new manager would automatically have access to his documents.
If you want multiple level approval system working (Employee-Manager-CEO/GM) using standard approval system only, following steps should be followed:
Employee should select CEO/GM as approver in their Leave Application or Expense Claim.
The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
Since CEO/GM who will be defined as Approver already will Approve/Reject request submitted by Employee.
How is this achieved in version 4?
Kind regards, Olawale
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
Thanks for your reply. The issue is at step 2 in your outline:
2. The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
The last part of your statement does not happen in version 4! The user properties defined based on Department do NOT get applied on managers... at least not visibly.
The reason could be because those documents already have permissions that restrict users with other fields like "From Employee".
There should be a way to let the system override the 'From Employee' restriction for a particular role (in this case, manager role) without ignoring user permissions for that field. If user permission for the 'From Employee' field is ignored then it means all employees would be able to view all Expenses which is obviously not what we want!
I hope you're seeing the issue now. Any suggestions?
Trust everyone's doing great today. While working with the new version (4) of our beloved ERPNext, I encountered an issue which I'm hoping someone else has been able to find a way around.
Question: how do you get a user with a certain role to see only a portion of a list which is relevant to them? I'll give a common scenario below.
Managers of various departments need to give authorization for several documents (Expense Claims, Leave Applications etc) before it gets to the final approver which could be a General Manager or CEO.
In your previous version, what did Employee select for Approver in their Leave Application or Expense Claim? Was it immediate Manager of employee, or GM/CEO who ultimately approves it? As per the standard approval system Expense Claim and Leave Application, only Approver as defined by the Employee can Approve or Reject request made by Employee.
Assigning role of "Expense Approver" and "Leave Approver" will be suffice, if that manager has authority for Approving or Rejecting.
3. Add Department value (e.g Sales, HR, Logistics) in user properties for all employees .
You should create User Property to define Department for each Employee. User Property to also be created for Manager listing Department they will have access to.
4. In Permission Manager, select 'Department' as condition for Manager role in the relevant docs.
In the upgrade Permission Manager, if "Apply User Permission" is checked in Role Permission Manage for specific Role, all the User Property created for that user will be applied.
If you don't particular User Property applied, you should check "Ignore User Permission" for that field from Customize Form. Check following link for more information on this.
With these steps, each manager would be able to view and manage documents from employees only within their departments/units. This also ensured that once an employee's department was changed, his new manager would automatically have access to his documents.
If you want multiple level approval system working (Employee-Manager-CEO/GM) using standard approval system only, following steps should be followed:
Employee should select CEO/GM as approver in their Leave Application or Expense Claim.
The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
Since CEO/GM who will be defined as Approver already will Approve/Reject request submitted by Employee.
How is this achieved in version 4?
Kind regards, Olawale
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
Thanks for your reply. The issue is at step 2 in your outline:
2. The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
The last part of your statement does not happen in version 4! The user properties defined based on Department do NOT get applied on managers... at least not visibly.
Please verify two things:
User Property should be set for Manager on Department.
In Role Permission Manager, "Apply User Permission" should be checked for the Manager's role.
The reason could be because those documents already have permissions that restrict users with other fields like "From Employee".
There should be a way to let the system override the 'From Employee' restriction for a particular role (in this case, manager role) without ignoring user permissions for that field. If user permission for the 'From Employee' field is ignored then it means all employees would be able to view all Expenses which is obviously not what we want!
Ignoring Permission on "From Employee" field is not required, because User Property for Manager will be have Employees defined in it. Have you define User Permission for Manager - Employee?
I hope you're seeing the issue now. Any suggestions?
Trust everyone's doing great today. While working with the new version (4) of our beloved ERPNext, I encountered an issue which I'm hoping someone else has been able to find a way around.
Question: how do you get a user with a certain role to see only a portion of a list which is relevant to them? I'll give a common scenario below.
Managers of various departments need to give authorization for several documents (Expense Claims, Leave Applications etc) before it gets to the final approver which could be a General Manager or CEO.
In your previous version, what did Employee select for Approver in their Leave Application or Expense Claim? Was it immediate Manager of employee, or GM/CEO who ultimately approves it? As per the standard approval system Expense Claim and Leave Application, only Approver as defined by the Employee can Approve or Reject request made by Employee.
Assigning role of "Expense Approver" and "Leave Approver" will be suffice, if that manager has authority for Approving or Rejecting.
Add Department value (e.g Sales, HR, Logistics) in user properties for all employees .
You should create User Property to define Department for each Employee. User Property to also be created for Manager listing Department they will have access to.
In Permission Manager, select 'Department' as condition for Manager role in the relevant docs.
In the upgrade Permission Manager, if "Apply User Permission" is checked in Role Permission Manage for specific Role, all the User Property created for that user will be applied.
If you don't particular User Property applied, you should check "Ignore User Permission" for that field from Customize Form. Check following link for more information on this.
With these steps, each manager would be able to view and manage documents from employees only within their departments/units. This also ensured that once an employee's department was changed, his new manager would automatically have access to his documents.
If you want multiple level approval system working (Employee-Manager-CEO/GM) using standard approval system only, following steps should be followed:
Employee should select CEO/GM as approver in their Leave Application or Expense Claim.
The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
Since CEO/GM who will be defined as Approver already will Approve/Reject request submitted by Employee.
How is this achieved in version 4?
Kind regards, Olawale
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
Yes, the 2 conditions you mentioned have been set accordingly
No, the user properties for manager does not have employees defined because as per your outline, the final approving authority (ie GM/CEO) is the one set as approving authority.
I do not welcome the idea of manually adding employees to manager properties because it doesn't seem like a workable/sustainable solution. What it implies is that if a department (e.g Sales) has 100 employees, then we need to individually add 100 employee IDs to the manager's user permissions!
What of in a scenario where employees are transferred from one department to another (this happens quite often)? The system will still allow the former manager to see/approve expenses until the employee IDs are manually deleted from one manager's profile and added to the other??
Why can't this just work like version 3 where you could simply set a condition for the manager to view docs for all employees whose department matches his own?
This was a much more graceful solution and it had the added advantage that once an employee's department changes, the new manager automatically gets access to his docs and the former manager stops seeing them.
Thanks for your reply. The issue is at step 2 in your outline:
2. The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
The last part of your statement does not happen in version 4! The user properties defined based on Department do NOT get applied on managers... at least not visibly.
Please verify two things:
User Property should be set for Manager on Department.
In Role Permission Manager, "Apply User Permission" should be checked for the Manager's role.
The reason could be because those documents already have permissions that restrict users with other fields like "From Employee".
There should be a way to let the system override the 'From Employee' restriction for a particular role (in this case, manager role) without ignoring user permissions for that field. If user permission for the 'From Employee' field is ignored then it means all employees would be able to view all Expenses which is obviously not what we want!
Ignoring Permission on "From Employee" field is not required, because User Property for Manager will be have Employees defined in it. Have you define User Permission for Manager - Employee?
I hope you're seeing the issue now. Any suggestions?
Trust everyone’s doing great today. While working with the new version (4) of our beloved ERPNext, I encountered an issue which I’m hoping someone else has been able to find a way around.
Question: how do you get a user with a certain role to see only a portion of a list which is relevant to them? I’ll give a common scenario below.
Managers of various departments need to give authorization for several documents (Expense Claims, Leave Applications etc) before it gets to the final approver which could be a General Manager or CEO.
In your previous version, what did Employee select for Approver in their Leave Application or Expense Claim? Was it immediate Manager of employee, or GM/CEO who ultimately approves it? As per the standard approval system Expense Claim and Leave Application, only Approver as defined by the Employee can Approve or Reject request made by Employee.
Assigning role of "Expense Approver" and "Leave Approver" will be suffice, if that manager has authority for Approving or Rejecting.
Add Department value (e.g Sales, HR, Logistics) in user properties for all employees .
You should create User Property to define Department for each Employee. User Property to also be created for Manager listing Department they will have access to.
In Permission Manager, select ‘Department’ as condition for Manager role in the relevant docs.
In the upgrade Permission Manager, if “Apply User Permission” is checked in Role Permission Manage for specific Role, all the User Property created for that user will be applied.
If you don’t particular User Property applied, you should check “Ignore User Permission” for that field from Customize Form. Check following link for more information on this.
With these steps, each manager would be able to view and manage documents from employees only within their departments/units. This also ensured that once an employee’s department was changed, his new manager would automatically have access to his documents.
If you want multiple level approval system working (Employee-Manager-CEO/GM) using standard approval system only, following steps should be followed:
Employee should select CEO/GM as approver in their Leave Application or Expense Claim.
The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
Since CEO/GM who will be defined as Approver already will Approve/Reject request submitted by Employee.
How is this achieved in version 4?
Kind regards, Olawale
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
Maybe this can be linked directly to the Department / Branch for Leave and Expenses. Maybe create a table where you can set employee and whether that employee is a leave / expense manager and that would define the rules for approval...
Yes, the 2 conditions you mentioned have been set accordingly
No, the user properties for manager does not have employees defined because as per your outline, the final approving authority (ie GM/CEO) is the one set as approving authority.
I do not welcome the idea of manually adding employees to manager properties because it doesn't seem like a workable/sustainable solution. What it implies is that if a department (e.g Sales) has 100 employees, then we need to individually add 100 employee IDs to the manager's user permissions!
What of in a scenario where employees are transferred from one department to another (this happens quite often)? The system will still allow the former manager to see/approve expenses until the employee IDs are manually deleted from one manager's profile and added to the other??
Why can't this just work like version 3 where you could simply set a condition for the manager to view docs for all employees whose department matches his own?
This was a much more graceful solution and it had the added advantage that once an employee's department changes, the new manager automatically gets access to his docs and the former manager stops seeing them.
Thanks for your reply. The issue is at step 2 in your outline:
2. The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
The last part of your statement does not happen in version 4! The user properties defined based on Department do NOT get applied on managers... at least not visibly.
Please verify two things:
User Property should be set for Manager on Department.
In Role Permission Manager, "Apply User Permission" should be checked for the Manager's role.
The reason could be because those documents already have permissions that restrict users with other fields like "From Employee".
There should be a way to let the system override the 'From Employee' restriction for a particular role (in this case, manager role) without ignoring user permissions for that field. If user permission for the 'From Employee' field is ignored then it means all employees would be able to view all Expenses which is obviously not what we want!
Ignoring Permission on "From Employee" field is not required, because User Property for Manager will be have Employees defined in it. Have you define User Permission for Manager - Employee?
I hope you're seeing the issue now. Any suggestions?
Trust everyone’s doing great today. While working with the new version (4) of our beloved ERPNext, I encountered an issue which I’m hoping someone else has been able to find a way around.
Question: how do you get a user with a certain role to see only a portion of a list which is relevant to them? I’ll give a common scenario below.
Managers of various departments need to give authorization for several documents (Expense Claims, Leave Applications etc) before it gets to the final approver which could be a General Manager or CEO.
In your previous version, what did Employee select for Approver in their Leave Application or Expense Claim? Was it immediate Manager of employee, or GM/CEO who ultimately approves it? As per the standard approval system Expense Claim and Leave Application, only Approver as defined by the Employee can Approve or Reject request made by Employee.
Assigning role of "Expense Approver" and "Leave Approver" will be suffice, if that manager has authority for Approving or Rejecting.
Add Department value (e.g Sales, HR, Logistics) in user properties for all employees .
You should create User Property to define Department for each Employee. User Property to also be created for Manager listing Department they will have access to.
In Permission Manager, select ‘Department’ as condition for Manager role in the relevant docs.
In the upgrade Permission Manager, if “Apply User Permission” is checked in Role Permission Manage for specific Role, all the User Property created for that user will be applied.
If you don’t particular User Property applied, you should check “Ignore User Permission” for that field from Customize Form. Check following link for more information on this.
With these steps, each manager would be able to view and manage documents from employees only within their departments/units. This also ensured that once an employee’s department was changed, his new manager would automatically have access to his documents.
If you want multiple level approval system working (Employee-Manager-CEO/GM) using standard approval system only, following steps should be followed:
Employee should select CEO/GM as approver in their Leave Application or Expense Claim.
The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
Since CEO/GM who will be defined as Approver already will Approve/Reject request submitted by Employee.
How is this achieved in version 4?
Kind regards, Olawale
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
Or perhaps option of Role-wise "Ignore User Permission" will do it.
If we can Ignore User Permission check on "For Employee" field just for the Managers Role, there will be no need to create User Property for each Approver-Employee.
Currently "Ignore User Permission" option in the Customize form is applied for all the users.
On Wed, Aug 20, 2014 at 6:33 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Maybe this can be linked directly to the Department / Branch for Leave and Expenses. Maybe create a table where you can set employee and whether that employee is a leave / expense manager and that would define the rules for approval...
Yes, the 2 conditions you mentioned have been set accordingly
No, the user properties for manager does not have employees defined because as per your outline, the final approving authority (ie GM/CEO) is the one set as approving authority.
I do not welcome the idea of manually adding employees to manager properties because it doesn't seem like a workable/sustainable solution. What it implies is that if a department (e.g Sales) has 100 employees, then we need to individually add 100 employee IDs to the manager's user permissions!
What of in a scenario where employees are transferred from one department to another (this happens quite often)? The system will still allow the former manager to see/approve expenses until the employee IDs are manually deleted from one manager's profile and added to the other??
Why can't this just work like version 3 where you could simply set a condition for the manager to view docs for all employees whose department matches his own?
This was a much more graceful solution and it had the added advantage that once an employee's department changes, the new manager automatically gets access to his docs and the former manager stops seeing them.
Thanks for your reply. The issue is at step 2 in your outline:
2. The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
The last part of your statement does not happen in version 4! The user properties defined based on Department do NOT get applied on managers… at least not visibly.
Please verify two things:
User Property should be set for Manager on Department.
In Role Permission Manager, "Apply User Permission" should be checked for the Manager's role.
The reason could be because those documents already have permissions that restrict users with other fields like "From Employee".
There should be a way to let the system override the 'From Employee' restriction for a particular role (in this case, manager role) without ignoring user permissions for that field. If user permission for the 'From Employee' field is ignored then it means all employees would be able to view all Expenses which is obviously not what we want!
Ignoring Permission on "From Employee" field is not required, because User Property for Manager will be have Employees defined in it. Have you define User Permission for Manager - Employee?
I hope you're seeing the issue now. Any suggestions?
Trust everyone's doing great today. While working with the new version (4) of our beloved ERPNext, I encountered an issue which I'm hoping someone else has been able to find a way around.
Question: how do you get a user with a certain role to see only a portion of a list which is relevant to them? I'll give a common scenario below.
Managers of various departments need to give authorization for several documents (Expense Claims, Leave Applications etc) before it gets to the final approver which could be a General Manager or CEO.
In your previous version, what did Employee select for Approver in their Leave Application or Expense Claim? Was it immediate Manager of employee, or GM/CEO who ultimately approves it? As per the standard approval system Expense Claim and Leave Application, only Approver as defined by the Employee can Approve or Reject request made by Employee.
Assigning role of "Expense Approver" and "Leave Approver" will be suffice, if that manager has authority for Approving or Rejecting.
Add Department value (e.g Sales, HR, Logistics) in user properties for all employees .
You should create User Property to define Department for each Employee. User Property to also be created for Manager listing Department they will have access to.
In Permission Manager, select 'Department' as condition for Manager role in the relevant docs.
In the upgrade Permission Manager, if "Apply User Permission" is checked in Role Permission Manage for specific Role, all the User Property created for that user will be applied.
If you don't particular User Property applied, you should check "Ignore User Permission" for that field from Customize Form. Check following link for more information on this.
With these steps, each manager would be able to view and manage documents from employees only within their departments/units. This also ensured that once an employee's department was changed, his new manager would automatically have access to his documents.
If you want multiple level approval system working (Employee-Manager-CEO/GM) using standard approval system only, following steps should be followed:
Employee should select CEO/GM as approver in their Leave Application or Expense Claim.
The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
Since CEO/GM who will be defined as Approver already will Approve/Reject request submitted by Employee.
How is this achieved in version 4?
Kind regards, Olawale
–
You received this message because you are subscribed to the Google Groups "ERPNext User's Forum" group.
Thanks for the input. I however think that would be a very limited solution. Don't forget that the principles apply with most any document. Many organizations work with several documents that go through various approval processes. In version 3, it was fairly easy to map most processes using a combination of workflow and permission manager.
I think you need something similar to the version 3 approach where we could give access based on a link within the docs matching user properties of certain roles
Maybe this can be linked directly to the Department / Branch for Leave and Expenses. Maybe create a table where you can set employee and whether that employee is a leave / expense manager and that would define the rules for approval...
Yes, the 2 conditions you mentioned have been set accordingly
No, the user properties for manager does not have employees defined because as per your outline, the final approving authority (ie GM/CEO) is the one set as approving authority.
I do not welcome the idea of manually adding employees to manager properties because it doesn't seem like a workable/sustainable solution. What it implies is that if a department (e.g Sales) has 100 employees, then we need to individually add 100 employee IDs to the manager's user permissions!
What of in a scenario where employees are transferred from one department to another (this happens quite often)? The system will still allow the former manager to see/approve expenses until the employee IDs are manually deleted from one manager's profile and added to the other??
Why can't this just work like version 3 where you could simply set a condition for the manager to view docs for all employees whose department matches his own?
This was a much more graceful solution and it had the added advantage that once an employee's department changes, the new manager automatically gets access to his docs and the former manager stops seeing them.
Thanks for your reply. The issue is at step 2 in your outline:
2. The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
The last part of your statement does not happen in version 4! The user properties defined based on Department do NOT get applied on managers... at least not visibly.
Please verify two things:
User Property should be set for Manager on Department.
In Role Permission Manager, "Apply User Permission" should be checked for the Manager's role.
The reason could be because those documents already have permissions that restrict users with other fields like "From Employee".
There should be a way to let the system override the 'From Employee' restriction for a particular role (in this case, manager role) without ignoring user permissions for that field. If user permission for the 'From Employee' field is ignored then it means all employees would be able to view all Expenses which is obviously not what we want!
Ignoring Permission on "From Employee" field is not required, because User Property for Manager will be have Employees defined in it. Have you define User Permission for Manager - Employee?
I hope you're seeing the issue now. Any suggestions?
Trust everyone’s doing great today. While working with the new version (4) of our beloved ERPNext, I encountered an issue which I’m hoping someone else has been able to find a way around.
Question: how do you get a user with a certain role to see only a portion of a list which is relevant to them? I’ll give a common scenario below.
Managers of various departments need to give authorization for several documents (Expense Claims, Leave Applications etc) before it gets to the final approver which could be a General Manager or CEO.
In your previous version, what did Employee select for Approver in their Leave Application or Expense Claim? Was it immediate Manager of employee, or GM/CEO who ultimately approves it? As per the standard approval system Expense Claim and Leave Application, only Approver as defined by the Employee can Approve or Reject request made by Employee.
Assigning role of "Expense Approver" and "Leave Approver" will be suffice, if that manager has authority for Approving or Rejecting.
Add Department value (e.g Sales, HR, Logistics) in user properties for all employees .
You should create User Property to define Department for each Employee. User Property to also be created for Manager listing Department they will have access to.
In Permission Manager, select ‘Department’ as condition for Manager role in the relevant docs.
In the upgrade Permission Manager, if “Apply User Permission” is checked in Role Permission Manage for specific Role, all the User Property created for that user will be applied.
If you don’t particular User Property applied, you should check “Ignore User Permission” for that field from Customize Form. Check following link for more information on this.
With these steps, each manager would be able to view and manage documents from employees only within their departments/units. This also ensured that once an employee’s department was changed, his new manager would automatically have access to his documents.
If you want multiple level approval system working (Employee-Manager-CEO/GM) using standard approval system only, following steps should be followed:
Employee should select CEO/GM as approver in their Leave Application or Expense Claim.
The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
Since CEO/GM who will be defined as Approver already will Approve/Reject request submitted by Employee.
How is this achieved in version 4?
Kind regards, Olawale
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.
Or perhaps option of Role-wise "Ignore User Permission" will do it.
If we can Ignore User Permission check on "For Employee" field just for the Managers Role, there will be no need to create User Property for each Approver-Employee.
Currently "Ignore User Permission" option in the Customize form is applied for all the users.
On Wed, Aug 20, 2014 at 6:33 PM, Rushabh Mehta <rm...@gmail.com> wrote:
Maybe this can be linked directly to the Department / Branch for Leave and Expenses. Maybe create a table where you can set employee and whether that employee is a leave / expense manager and that would define the rules for approval...
Yes, the 2 conditions you mentioned have been set accordingly
No, the user properties for manager does not have employees defined because as per your outline, the final approving authority (ie GM/CEO) is the one set as approving authority.
I do not welcome the idea of manually adding employees to manager properties because it doesn't seem like a workable/sustainable solution. What it implies is that if a department (e.g Sales) has 100 employees, then we need to individually add 100 employee IDs to the manager's user permissions!
What of in a scenario where employees are transferred from one department to another (this happens quite often)? The system will still allow the former manager to see/approve expenses until the employee IDs are manually deleted from one manager's profile and added to the other??
Why can't this just work like version 3 where you could simply set a condition for the manager to view docs for all employees whose department matches his own?
This was a much more graceful solution and it had the added advantage that once an employee's department changes, the new manager automatically gets access to his docs and the former manager stops seeing them.
Thanks for your reply. The issue is at step 2 in your outline:
2. The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
The last part of your statement does not happen in version 4! The user properties defined based on Department do NOT get applied on managers… at least not visibly.
Please verify two things:
User Property should be set for Manager on Department.
In Role Permission Manager, "Apply User Permission" should be checked for the Manager's role.
The reason could be because those documents already have permissions that restrict users with other fields like "From Employee".
There should be a way to let the system override the ‘From Employee’ restriction for a particular role (in this case, manager role) without ignoring user permissions for that field. If user permission for the ‘From Employee’ field is ignored then it means all employees would be able to view all Expenses which is obviously not what we want!
Ignoring Permission on "From Employee" field is not required, because User Property for Manager will be have Employees defined in it. Have you define User Permission for Manager - Employee?
I hope you’re seeing the issue now. Any suggestions?
Trust everyone’s doing great today. While working with the new version (4) of our beloved ERPNext, I encountered an issue which I’m hoping someone else has been able to find a way around.
Question: how do you get a user with a certain role to see only a portion of a list which is relevant to them? I’ll give a common scenario below.
Managers of various departments need to give authorization for several documents (Expense Claims, Leave Applications etc) before it gets to the final approver which could be a General Manager or CEO.
In your previous version, what did Employee select for Approver in their Leave Application or Expense Claim? Was it immediate Manager of employee, or GM/CEO who ultimately approves it? As per the standard approval system Expense Claim and Leave Application, only Approver as defined by the Employee can Approve or Reject request made by Employee.
Assigning role of "Expense Approver" and "Leave Approver" will be suffice, if that manager has authority for Approving or Rejecting.
Add Department value (e.g Sales, HR, Logistics) in user properties for all employees .
You should create User Property to define Department for each Employee. User Property to also be created for Manager listing Department they will have access to.
In Permission Manager, select ‘Department’ as condition for Manager role in the relevant docs.
In the upgrade Permission Manager, if “Apply User Permission” is checked in Role Permission Manage for specific Role, all the User Property created for that user will be applied.
If you don’t particular User Property applied, you should check “Ignore User Permission” for that field from Customize Form. Check following link for more information on this.
With these steps, each manager would be able to view and manage documents from employees only within their departments/units. This also ensured that once an employee’s department was changed, his new manager would automatically have access to his documents.
If you want multiple level approval system working (Employee-Manager-CEO/GM) using standard approval system only, following steps should be followed:
Employee should select CEO/GM as approver in their Leave Application or Expense Claim.
The Expense or Leave Approver (or Manager in your case) should be given only read permission on Expense Claims and Leave Applications respectively. After reviewing, they will escalate Claim or Leave request to CEO/GM. The User Properties define based on Department will be applied on managers.
Since CEO/GM who will be defined as Approver already will Approve/Reject request submitted by Employee.
How is this achieved in version 4?
Kind regards, Olawale
–
You received this message because you are subscribed to the Google Groups “ERPNext User’s Forum” group.