Configuring the Case summary feature
The Case summary feature contains a detailed view of the stages, steps, and the most relevant data for a case across its lifecycle.
The process of onboarding a new customer can vary depending on factors, such as the customer type, their location, and the products they use. Increasing regulation in the financial services industry adds pressure to understand the progress of ongoing work, related information, and those main parties involved in onboarding activities. This context-specific view of the overall parent case or separate units of related work must provide relevant data to the user to help them continue their task or understand blockers to progress.
For more information about how the Case summary feature is configured, see Case summary.
To configure this feature, do the following tasks.
Customizing the color of the progress gauge
The progress gadget shows the percentage of completion of the case and the status. By default, the indicator is red if the task is delayed and green if the task in on track. If you want to modify the colors, do the following steps.
In the Dev Studio header search text field, enter simple-percentage-chart and select the HTML or CSS file.
Save both rules into your implementation layer. For additional information about locked and unlocked rulesets, see Copying a rule or data instance.
In the CSS file, change the color properties to a color of your choice.
Click Save.
Configuring the progress percent value
The progress gadget shows the percentage of completion of the case and the status. You can configure at which percentage of completion a case is considered delayed.
In the Dev Studio header search text field, enter CalculateNavigationProgress and select the activity rule.
Save the rule into your implementation layer. For additional information about locked and unlocked rulesets, see Copying a rule or data instance.
Modify the Calculation if case not complete method parameters.
Click Save.
Configuring the passed deadline conditions
The progress gadget shows the percentage of completion of the case and the status. You can configure the conditions for when the deadline for completion has passed.
In the Dev Studio header search text field, enter SLADeadlineIsPast and select the when rule.
Save the rule into your implementation layer. For additional information about locked and unlocked rulesets, see Copying a rule or data instance.
Select the Advanced tab and modify the conditions of the when rule, as needed.
Click Save.
Configuring data categories
You can configure which data categories appear on the Case summary. To modify these categories, edit the data transform and when rules for the categories.
In the Dev Studio header search text field, enter SetAllDataStatusValue and select the data transform rule.
Save the rule into your implementation layer. For additional information about locked and unlocked rulesets, see Copying a rule or data instance.
Modify the action and the associated when rule, as necessary.
Click Save.
Modifying related cases
If you are using parallel fulfillment, the system creates the related sibling fulfillment cases for a jurisdiction when all due diligence activities for that jurisdiction are completed.
The related cases are displayed based on the ObjectType property which equals pzinskey from the main Pega Client Lifecycle Management for Financial Services case.
If you want to change the condition on which related cases should be visible, modify the data page and report definitions.
In the Dev Studio header search text field, enter D_SiblingRelatedCasesByObjectTypeLink and select the data page rule.
Save the rule into your implementation layer. For additional information about locked and unlocked rulesets, see Copying a rule or data instance.
Modify the data page rule, as necessary.
Click Save.
Open the RelatedCasesByObjectType report definition and modify the properties, as necessary.
Click Save.
If you want to change the related cases display properties, open the RelatedCaseUnit section rule and modify the section properties.
Configuring pending requirements
At the end of the Capture stage the system creates a unique requirement case for every requirement. You can view a list of pending requirements in the bottom-right corner of the Case summary screen from the Enrich stage onwards.
Depending on the conditions configured in the requirement set rule, the respective requirements are only applicable to the customer.
If you want to update the applicability of the requirement, do the following steps.
In the Dev Studio header search text field, enter OnboardOrganizationBasic and select the requirement set rule.
Save the rule into your implementation layer. For additional information about locked and unlocked rulesets, see Copying a rule or data instance.
Modify the requirements, as needed.
Click Save.
If you want to apply new requirements for any customer, create appropriate requirement rules in the respective requirement set rule.
Previous topic Data traceability Next topic Configuring event-driven architecture