Selection of requirements in Pega Client Lifecycle Management
You can access a party's requirements in three ways:
- Requirements gadget: shows the Contracting Party and Related Party requirement cases, by party and Requirement set.
- Customer 360: shows all the requirement cases for a particular party.
- My cases: shows all cases related to the operator.
Requirements gadget
You can access Contracting Party and relevant Related Party requirements cases in the Requirements gadget, which is located in the right pane of both the Enrich and Due Diligence stages.
The following example shows the requirements gadget for a contracting party with a related organization and related individuals:
The requirements are organized first by party and then by requirement set. The requirements for the contractive party are always listed first, followed by related organizations in alphabetical order and related individuals in alphabetical order. Along with each party, there is a number of pending requirement cases so that the user can set the focus in what is remaining to complete the document collection. Expanding a given party shows the party roles in relation to the contractive party, the requirement sets (in bold) and their associated requirements, with the stage in which each of those requirement is in.
Customer 360
Starting in Pega Client Lifecycle Management for Financial Services version 8.5, the Customer 360 view includes the Requirements tab, which shows all requirement cases applicable to the selected party. The following example shows the list of requirement cases for a specific party:
Pega CLM uses the latest Pega Platform grid capabilities, which support searching for matching text across all fields, grouping by field, adding fields, and changing the density of each row.
Selecting a requirement case ID launches the requirement case within the context of the parent customer journey case, and a case summary is displayed in which users can review the information and open any non-completed case that the user has permission to perform work on.
My Cases
For users to quickly focus on the most urgent cases, requirements are routed to work baskets so that users can view the cases in their worklists.
In the example below, the parent customer journey case lists the requirement cases as sub-cases, along with important information such as urgency, service level agreement due dates, and status.
Selecting a requirement case ID launches the requirement case within the context of the parent customer journey case, and a case summary is shown where users can review the information and open a non-completed case the user has permission to perform work.
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.
Want to help us improve this content?