Skip to main content

Configuring cascading approvals with an authority matrix

2 Tasks

10 mins

Visible to: All users
Beginner
Pega Platform '24.2
Case Management
English

Scenario

As the repair service grows, GoGoRoad stakeholders want to allow Territory Managers to submit new vendors as service providers for approval. If the vendor is The Automobile Association (TAA), which has an existing relationship with GoGoRoad, the New vendor Case is routed to the Manager of the Territory Manager for approval. The Case is then routed to a Compliance Officer, who ensures the request adheres to the agreement between TAA and GoGoRoad. If the vendor is not TAA, the New vendor Case is routed to the Manager, and then the Director for approval. Create a Decision table to ensure the approval is routed appropriately. Add an Approval Step to the New vendor Case Type to support the described behavior.

The following table provides the credentials you need to complete the challenge.

Role User name Password
Application Developer author@gogoroad pega123!
Note:  The challenge walkthrough video is coming soon. 

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

Challenge Walkthrough

Detailed Tasks

1 Configure the Approve vendor Step

  1. In the Pega instance for the challenge, enter the following credentials:
    1. In the User name field, enter author@gogoroad.
    2. In the Password field, enter pega123!.
  2. Switch to Dev Studio, and in the navigation pane, click Case Types.

  3. Select the New Vendor Case Type, and click the Workflow tab. 

  4. In the Approval Process, click Step > Approve/Reject.
  5. Name the Step Approve vendor.
  6. Click and drag the Approve vendor Step to precede the Save Data Page Step.
    Approve vendor step in the Approval stage of the New Vendor case type
  7. With the Approve vendor Step selected, on the General tab of the properties pane, in the Approval flow type list, select Cascading.
  8. In the Approval based on list, select Authority matrix.
  9. In the Page list property field, enter or select .VendorApprovals as the page list property to hold the list of approvers.
  10. In the Approver property field, enter or select .ApproverID as an element of the page list to identify each approver in the list.
  11. In the Decision table for matrix field, enter VendorApprovals as the Decision table that determines the Conditions for populating the page list.
  12. To the right of the Decision table for matrix field, click the Open icon to open and configure the Decision table.
    Approve vendor

2 Configure the VendorApprovals Decision table

  1. On the Create Decision Table form, click Create and open.
  2. Click the Results tab.
  3. In the Delegation options section, select the Evaluate all rows check box.
    Decision table Results tab with Evaluate all rows option selected
  4. Click the Table tab.
  5. In the Conditions column, click the first cell heading to display the Select a Property dialog box.
    First heading cell in the decision table
  6. In the Property field, enter or select .NewVendor.Name to specify the Condition property.
  7. In the Label field, enter Vendor name.
  8. Keep the default operator as =.
  9. Click Save to finish configuring the Condition.
    Select a condition for the condition heading in a decision table
  10. Under Actions, click the cell heading to specify the Condition property as .VendorApprovals(<APPEND>).ApproverID.
  11. In the Label field, enter Vendor approvals.

  12. Keep the default operator as =.
  13. Click Save to finish configuring the Condition.
    Configuration of the Actions header in the Vendor Approvals decision table
  14. Click an empty cell in the table, and then click the Insert Row after icon to insert two additional rows.
    Insert row after button
  15. Click each cell in the Decision table, and then enter the following values:
      Vendor name Vendor approvals
    When   "manager@gogoroad"
    When !=TAA "director@gogoroad"
    When TAA "complianceofficer@gogoroad"
    Otherwise   ""
    Vendor approvals decision table configured
  16. Click Save to save the Decision table.
  17. Return to the New Vendor Case Type, and then click Save to save the changes to the workflow.

Confirm your work

  1. Switch to App Studio and click Preview.
  2. From the Web Portal, click Create New Vendor.
  3. In the Create New Vendor dialog box, in the Name field, enter TAA.
  4. Click Submit.
  5. Expand the Assignments section of the Case.
  6. In the Assignments section, to the right of Get Approval, click Go to display the first approval.
  7. In the Get Approval View, verify that the open Assignment is assigned to the Manager.
    Get Approval from Manager
  8. Click Approve.
  9. In the Assignments section of the Case, to the right of Get Approval, click Go to display the second approval.
  10. In the Get Approval View, verify that the open Assignment is assigned to the Compliance officer.
    Get Approval from Compliance officer
  11. Click Approve to resolve the case.
  12. Create a New vendor Case instance.
  13. In the Create New Vendor dialog box, in the Name field, enter Pega Towing.
  14. Click Submit.
  15. In the Assignments section of the Case, to the right of Get Approval, click Go to display the first approval.
  16. In the Get Approval View, verify that the open Assignment is assigned to the Manager.
  17. Click Approve.
  18. In the Assignments section of the Case, to the right of Get Approval, click Go to display the second approval.
  19. In the Get Approval View, verify that the open Assignment is assigned to the Director.
    Get Approval from Director
  20. Click Approve to resolve the case.

This Challenge is to practice what you learned in the following Module:


Available in the following mission:

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice