Cascading approvals with a reporting structure
Approvals vary depending on the case type. An auto insurance case type may need one approval from the company underwriter. Some case types, such as a purchase request or an expense report, may require a series of approvals — aprocess configures 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?
The two cascading approval models areand . Cascading approvals based on reporting structure require the approval of a user's direct manager and higher. 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. 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.
Reporting structure cascading approval options
You configure cascading approvals in Dev Studio.
Reporting structure cascading approval options include:
|The operator that completes the approval||The reporting structure approval generates a set of approvers using the information on the user's operator ID record. Either the user's Reporting manager or the Workgroup manager completes the approval. At run time, Pega Platform™ looks up the appropriate approver based on the current user.|
|The number of approvers in the structure||
Reporting structure custom approval level
An expense report reimbursement request requires approvals based on the reporting structure and approvals shown in the following image. The number of approvals depends on the amount of the request.
Check your knowledge with the following interaction.