Skip to main content

Cascading approvals

Approvals vary depending on the Case Type. An auto insurance Case Type might need approval from the company underwriter. Some Case Types, such as a purchase request or an expense report, may require a series of approvals. Cascading approvals model a series of approvals. 

When configuring a cascading approval, consider the following questions:

  • Who needs to perform the approval?
  • How many approvals are required?
  • Is approval by the entire reporting structure required, or only a subset of the hierarchy?
  • Are approvals outside the reporting structure required?

The two cascading approval models are reporting structure and authority matrix

Cascading approvals with a reporting structure

Cascading approvals based on reporting structure require the approval of a user's direct manager, as well as higher-level managers. You can also configure business logic to set thresholds to determine the number of required approvals.

For example, an expense report requires manager approval before the accounting department can process the payment. As shown in the following figure, depending on the total of the expenses submitted, the expense request may also need approval by a senior manager, a director, and a vice president. If the expense report is USD 3000, the Manager, Senior Manager, Director, and VP must all review the report.

Cascading approval with a reporting structure

Cascading approvals with a reporting structure options

You configure cascading approvals in Dev Studio by adding an Approve/Reject Step to the Case Life Cycle and selecting the Cascading option. You select the Reporting structure option to configure a cascading approval based on the reporting structure.

In the following image, click the + icons to learn more about the reporting structure cascading approval options:

Cascading approvals with an authority matrix

A cascading approval based on an authority matrix is more flexible than a reporting structure. You use the authority matrix model when configuring a Process that requires approvals from multiple entities, with at least one entity outside of the reporting structure. A set of Rules directs the approval chain to entities outside of the reporting structure, within and external to the user's organization. 

For example, the following image shows an expense report that requires approvals outside of the reporting hierarchy to accounts payable, and uses an authority matrix model:

Cascading approval with an authority matrix

Authority matrix data structure population

A cascading approval with an authority matrix requires configuration of a data structure that identifies the approvers. The application queries the structure for each approval until the listed approvals are exhausted. Pega Platform provides several ways of populating the data structure: a Decision table, Data Page, activity, or Data Transform.

One common approach is to configure a Decision table to identify the approval levels and corresponding parties. The application evaluates the Decision table to populate the data structure. Each satisfied row or Condition adds the results to a list of approvers. Approval Assignments are routed to approvers in the order of list appearance.

In the expense report example, which is shown in the following image, the Decision table identifies each party in the approval Process as well as the Conditions that determine when each party must provide approval. The first Condition states that Accounts Payable must approve any billable expense. The three When Conditions that follow are based on the expense amount. If a consultant submits an expense report for USD 700 that includes billable time, the application creates an authority matrix with three approvals: Accounts Payable, the manager of the consultant, and the director who oversees the consulting department.

Decision table for expense report
Tip: When using a Decision table with an authority matrix, set the Decision table to Evaluate all rows to return a list of results. Otherwise, the Decision table returns only one result.

Cascading approvals with an authority matrix options

In Dev Studio, in an Approve/Reject Step, you select the Cascading and Authority matrix options to configure a cascading approval based on an authority matrix.

In the following image, click the + icons to learn more about the authority matrix cascading approval options:

Check your knowledge with the following interaction:


This Topic is available in the following Module:

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