Requirement: In “Role Assignment to User” scenario, supervisors of affect users will approve the CR. In case there are multiple users having different supervisors; supervisor must only be allowed to approve Change Items (CIs) for their subordinates. They must not be allowed to approve CIs for those who are not their subordinates.
Is there a way to fulfill this requirement?
Thanks william
Does this satisfy the req. that supervisors can only approve for their subordinates and they cannot approve/disapprove for subordinates of other supervisors?
I have not tested this solution, so I couldn’t tell you for sure. Currently my role approvals are all done by a single individual.
To add on top what William mentioned.
If your approval configuration looks like this:
And the configuration of the approval workflow is configured to group by Supervisor
When adding new users to a role, the approval will be split between the supervisors.
Each supervisor will approve only his subordinates.
Here is an example:
Approval is split to 2 approvers. There are total of 4 users requested to be added to a role.
Approver #1 sees 2 users to approve
Approver #2 get to approve 2 different users
You ca n group by user also. For each user separate instance of approval WF will be invoked and hence it will go to respective supervisor for approval.
Indeed it's possible to group by user, but when you will be adding 10 users to a role (let's assume with the same supervisor), the supervisor will be assigned 10 different tasks for each user.
Here is an example:
Thanks for your feedback. Grouping by supervisor is a good approach but it is not enough in our case.
Here is my business flow for approval,
1- Requestor creates Role Assignment (add user to role) request
Requestor is one of the following users = Role Owner, BRPM (Business Role Portfolio Management) Team Members, Line Managers
2- Supervisors of affected users approves for their subordinates.
Here each supervisor should only be able to approve for their subordinates
3- Role Owner approves for All Affected Users
Here role owner should recieve only 1 approval task for all affected users
4- BRPM team members approves for All Affected Users
Here BRPM team should recieve only 1 approval task for all affected users
According to suggested approach, how do you fulfill above mentioned approval steps?
Should we put 2 approval phase nodes in Request WF such that;
- In the first approval phase node, the items will be grouped by supervisors
- In the second approval phase node, one job will be created to process all changes?
Will this work?
Have you tried selecting Supervisors in the approval node of the approval workflow?
(Approval Node -> Resources Tab -> Include Box -> Select -> Supervisors)
I have not implemented supervisor approvals, but we use a similar process for Role Owners to approve.