When your case requires one or more people to approve an action using the approval
step gives you a simple way to configure the approval and handle the outcome of the
approval
“Iamnobody89757” Understanding the Mysterious of Digital Identity.pdf
Case Approvals in PEGA
1. PEGA UAP - “Tech Show Time”
CASE APPROVALS
(Team: 02)
D. SWATHI
B. PRASHANTH
K. SAI CHARAN TEJ
2. Routi
ng
A process that distribute work
efficiently within an
organization.
It involves determining the best
user for the task based on their
skills, availability and which
team they are part of.
You can route a step to a single
user or worklist or work queue
or use business logic to route
work based on certain condition
3. Case approvals
Case approvals are decision points at which one or more users decide whether to approve or reject
employee submits a request for an equipment upgrade. Equipment upgrade requests are sent to a
rejects the request.
4. Approve/
Reject
Approvals in Pega Platform™
are configured by using the
Approve/Reject step.
To configure an Approve/Reject
step, LSA will define who is
assigned to the approval and
how the case proceeds if the
case is approved or rejected.
To achieve this, they will
configure the Approve/Reject
step routing and flow.
The Approve/Reject step
5. Cascading approval
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,
Cascading (A list of approvers will be looped through and each approver will be assigned to approve
Example : An employee submits a request for an equipment upgrade. Equipment upgrade requests
approves or rejects the request. If the manager approves the request and the upgrade costs more
manager also needs to approve the request.
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 are
i)Reporting Structure
ii)Authority Matrix
Cascading approvals based on reporting structure require the approval of a user's direct manager and
6. The Single level Approval (A single user will be
assigned the task of approving or rejecting the
Route to:
• Specific use
–> User name
–> User reference field
–> Reporting manager
–> Participant (work party)
• Work queue
7. Realtime Example:
An Student submits a request for a leave. leave requests is
Incharge, who either approves or rejects the request.
Actions for approved and rejected:
• If APPROVED then • If REJECTED then
– Continue – Resolve
– Change Stage – Continue
– Change Stage
9. Head of Electrical Department
Head of Electronics
Department
Head of Computer Science
Department
Head of Information
Technology Department
Head of Mechanical
Department
Mirjam Nilsson
Principal
Dean of Academics
Dean of Academics
Mentor
Respective Faculty
Dean of Academics
Dean of Academics
Mentor
Dean of Academics
Mentor
Respective Faculty
Dean of Academics
Head of Chemical Technology
Department
Organization chart
Reporting Structure
Student
Mentor
Respective Faculty
Respective Faculty
Student
Mentor
Respective Faculty
Student
Student
Mentor
Respective Faculty
Student
10. Cascading approvals with a reporting structure
The operator reporting structure is used to identify to whom the
operator reports. And it is used in creating reports, sending
notifications, correspondences, approval functionality in pega
-->Approval to be completed by
• Determines which operator is the starting point in the
reporting structure
• Reporting manager
– Reporting manager of current user
• Workgroup manager
– Manager of the current user’s default workgroup
13. Authority Matrix
• A data structure that supplies an ordered list of approvers used by an approval
shape’s cascading approval feature.
• More flexible than reporting structure.
• It supports routing to other entities outside of the reporting structure
Authority matrix – Used when a set of rules directs the approval chains to individuals
both inside and outside the organization of the submitter
Cascading Approval with Authority Matrix:
14. Finance
Committe
Governing
Body
Authority Matrix
Organization structure
Chairman
Principal
BOE, COE,CDC
Controller of
Examinations
Respective
Faculty
HOD ECE
Mentor
Student
Library
Committee,
Sports and Games
Coordinator CCA,
ECA & SC/ST
Committe
Academic Audit
Committe
Academic
Committee, Dean
IQAC
Alumni Committe
Placement and
Trainining Cell
R & D
Talent Sprint
Team
PEGA
Training
Committe
Patent Cell
15. Set Evaluate all rows option and configure the logic
• The first page of the authority matrix page list will be
value of the first true row from the decision table each
another page with the given approver.
• The otherwise row will only add an approver if none of the
false.
17. Here we create:
Page list Property (Holds the data) Mandatory
Decision Table(For Populating Page list) Optional,
because we can go with other options.
Approver property(eg: .User ID)===>Mandatory
Authority Matrix
18. <APPEND>: To add an element to the end (highest index value) a Value List or Page List property
<CURRENT>In that context, the index identifies the index value for the current iteration
<INSERT> Use the keyword followed by an integer to insert a new element and its value into a
Page List property at a numeric index position. Any elements with the same or higher index value
are "pushed down"
<LAST>To set or retrieve an element value from the end (highest index value) a Value List or Page
List property
<PREPEND>Use the keyword insert a new element and its value into a Page List property as the
first element. All existing elements are "pushed down" by on
PEGA provides a set of symbolic indexes to access items in a page list without
using an explicit index number