Cascading Approval in Pega- Based on Authority Matrix
Approval based on Authority Matrix
This model works when the approval chain is directed by a set of rules to individuals both in and out of the submitters organization.The approvals proceed sequentially through the hierarchy.
For eg. In a Claim application, let us assume an employee submits his travel expenses, the approval will be routed based on conditions defined as follows: amounts greater than or equal 2500, it is routed to Manager.,For amounts greater than or equal 5000, it is routed to Senior manager and for amounts greater than or equal 10000 it is routed to director.
Now, let us take same case type "Time off" as in our previous post and see approval based on authority matrix. In authority matrix, it is based on decision table or you can use data transform where it populates the list of approvers based on the conditions.
Step 1
First, let us create a Page List property which holds the list of approvers. I have provided class "Data-Admin-Operator-ID" as page definition.(You can give any page definition for list of approvers according to your application requirement.)
Step 2
Next, I have designed below decision table which holds the conditions and populates the list with approvers. Under the actions column, map the pagelist property with approver property in the below format:
Make sure you have selected "Evaluate All Rows" in the Results tab of decision table rule so that it will evaluate all rows of decision table and populates the list.
Step 3
Add the above configured Page List property and decision table in the approval step of case type. The approver name is stored in "Approver property" configured as below.
Now, let us try to create case and see it's output.
Here in this case, leave is applied for 25 days. As per decision table configuration, it should route to Manager and SrManager.
You could see details in the Audit tab of case to see it's routing.
Hope the posts on Cascading approval is helpful. You can quickly build cascading approval easily using above approach. We can also route the approval based on skill ,to workbasket too.
Happy Learning. 🙂
This model works when the approval chain is directed by a set of rules to individuals both in and out of the submitters organization.The approvals proceed sequentially through the hierarchy.
For eg. In a Claim application, let us assume an employee submits his travel expenses, the approval will be routed based on conditions defined as follows: amounts greater than or equal 2500, it is routed to Manager.,For amounts greater than or equal 5000, it is routed to Senior manager and for amounts greater than or equal 10000 it is routed to director.
Now, let us take same case type "Time off" as in our previous post and see approval based on authority matrix. In authority matrix, it is based on decision table or you can use data transform where it populates the list of approvers based on the conditions.
Step 1
First, let us create a Page List property which holds the list of approvers. I have provided class "Data-Admin-Operator-ID" as page definition.(You can give any page definition for list of approvers according to your application requirement.)
Next, I have designed below decision table which holds the conditions and populates the list with approvers. Under the actions column, map the pagelist property with approver property in the below format:
pagelistproperty(<APPEND>).approverproperty
Append keyword is used to add the approvers to the list after evaluating the When condition.Add the above configured Page List property and decision table in the approval step of case type. The approver name is stored in "Approver property" configured as below.
Here in this case, leave is applied for 25 days. As per decision table configuration, it should route to Manager and SrManager.
You could see details in the Audit tab of case to see it's routing.
Hope the posts on Cascading approval is helpful. You can quickly build cascading approval easily using above approach. We can also route the approval based on skill ,to workbasket too.
Happy Learning. 🙂
