As assured in my previous post, my post is here to explain about the “Manager Hierarchy” in workflow setups.
One of the common business requirements for the workflow approvals is to route the specific business document to the requesters’ managers for approvals. Ex: Purchase requisitions or Expense requests.
Scenario: client’s requirement is to configure the workflow in such a way that “When a purchase requisition is submitted by an employee, it must be routed to the person to whom the employee reports to”.
Let’s consider that the below screen shot is the reporting hierarchy for the employee. We are considering “James” persona for this demonstration. As per our example, we are configuring the workflow to route the Purchase requisition to Adam who is an immediate manager to James.
As you already knew, we are obviously going to configure it using the “Managerial Hierarchy”.
-Managerial Hierarchy works based on the “position hierarchy” that is defined in the organization.
-Make sure that the employees used in the position hierarchy are linked with the corresponding Ax users in System administration>users form
-Position hierarchy will be built based on the “reports to position” field of the corresponding Position. To know how to create the position hierarchy – click this – Position Hierarchy
“Stop when the following condition is met”:
Basically, “Managerial hierarchy” routes the document to immediate reporting position. Once it is approved, it will be routed to the next manager, so it keeps routing it to the next manager in the hierarchy.
Using the “Stop when the following condition is met”, we should specify where it must stop the assignment. So, as per our position hierarchy, if James submits requisition, it goes to Adam, next to Alex and next to Sunny.
We are stopping the assignment using the “line manager level” condition which is set to 1 i.e. employee.line manager level = 1.
Above stop condition stops the assignment by assigning only to line manager of level1. The PR will be assigned only to the immediate position. As per the considered position hierarchy, it will be assigned to employee “Adam” and once Adam approves it the “PR status” will be shown as “Approved”
If the stop condition is set to “stop where employee.Line manager level =2”, the PR will be routed to Adam, and once Adam approves it, it will be routed to “Alex”.
Note: above explanation is in accordance with “Hierarchy options – “Assign to all users retrieved”.
Let’s go with below example.
If the stop condition is set to “stop where employee.Line manager level =2”, the PR will be routed to directly to Alex and it will not be routed to “Adam”. As the last user retrieved with hierarchy based on the above condition is “Alex”.
You have different options that can be used in “stop condition” as per the requirements.
Hope this post clearly explains how you can use the “Managerial hierarchy” in your workflows. Your suggestions and feedback are most welcoming.
Keep visiting and keep DAXing!!
In the next post, we are going to see how we can efficiently use the approval limits with Managerial hierarchies.
My next post addresses the below scenario which is requested by “Bhav” (one of the blog visitors). Below is Bhav’s requirement for your reference.
Have you tried to use an organisational hierarchy in a workflow? For example i’ve set up 3 users and assigned jobs, positions etc. and i assigned Spending limits to them through the policies in Org Admin (Trainee – upto $1000, Team Leader – More than $1000 but less than $5000, and Manager more than $5000 and upto $10,000). I was trying to replicate that if a requisition created by a trainee of $6000 it would bypass the second approver and go straight to the 3rd approver and stop there. This was only a demo, but i’m trying to replicate this with 5 levels of hierarchy. If you could help out with that, it would be fantastic!