Troubleshooting a Pega Platform application
1 Task
35 mins
Beginner
DevOps
English
Scenario
In the Travel Management Customer Support (TMCS) application, the Complaint Resolution Case Type creates a Refund Processing child Case during the Fulfillment Stage. Based on conversations with U+ Hotels stakeholders and the Lead System Architect, the application is expected to copy the value of the Compensation Amount field from the parent Complaint Resolution Case to the Refund amount field of the Refund Processing child Case, so that the refund team can disburse the agreed amount without rekeying data.
During testing, the value of the Refund amount field on the Refund Processing Case does not match the Compensation Amount value on the parent Complaint Resolution Case. The Service Manager flagged the issue to the Lead System Architect, who assigned the troubleshooting work to you.
As an Application Developer on the TMCS team, you must use the Tracer tool that the Pega Platform provides to isolate where the data transfer breaks down and correct the configuration so that the two fields agree.
Business requirement: The TMCS application must transfer the value of the Compensation Amount field from the parent Complaint Resolution Case into the Refund amount field of the Refund Processing child Case, so that the two values match when the child Case is created.
Note: This challenge has been configured with Single sign-on (SSO) using your Pega Academy credentials. If you are not automatically signed-in to the challenge environment after initializing the instance, you may use the credentials provided.
The following table provides the credentials you may need to complete the challenge:
| Role | User name | Password |
|---|---|---|
| Solution Builder | [email protected] | pega123! |
After completing this challenge, you should be able to:
- Identify data transfer discrepancies between parent and child Cases in a Pega Platform application.
- Use the Tracer tool to evaluate run-time rule execution, including filtering to a specific ruleset and analyzing the Run Data Transform automation step.
- Inspect the parent and child page values that the Tracer tool captures for a Run Data Transform step.
- Modify Case Type configuration so that the parent Compensation Amount transfers correctly to the child Refund amount.
Detailed Tasks
1 Troubleshoot a Pega Platform application
Use the technical documentation linked in the Doc Journey above to complete the assigned tasks. The technical documentation might have more information than you need to complete the tasks.
Acceptance criteria
- The Tracer tool runs against a new Complaint Resolution Case and is filtered to evaluate only the application Ruleset: TMCS that contains the Complaint Resolution and Refund Processing Case Types.
- The Tracer tool captures the behavior of the Data Transform: PropagateDatatoRefund that is invoked during the Refund Processing child Case creation on the Fulfillment Stage of Complaint Resolution.
- The Tracer event for the Data Transform: PropagateDatatoRefund is examined to compare the parent Complaint Resolution Compensation Amount with the child Refund Processing Refund amount captured at run time.
- The configuration is corrected so that the Refund amount value on the Refund Processing Case equals the Compensation Amount value on the parent Complaint Resolution Case after the child Case is created.
- The corrected configuration runs without modifying any of the following:
- The Stages or Steps of either Case Type.
- The
pyDefaultdata transform onUPlus-TMCS-Work. - The Generate Refund ID data transform on Refund Processing.
Directions
- Open the Complaint Resolution Case Type and create a new Case. Capture a non-zero value in the Compensation Amount field as the Case progresses through the Propose Resolution Stage.
- Allow the Case to reach the Fulfillment Stage so that the Refund Processing child Case is created.
- Open the Refund Processing child Case and confirm that the Refund amount value does not match the parent Compensation Amount value.
- In the Infinity Studio footer Developer toolbar, open the Tracer window. Update the Tracer settings to filter to the application Ruleset: TMCS that contains the Complaint Resolution and Refund Processing Case Types.
- Create a new Complaint Resolution Case. Run the Tracer tool to capture the Data Transform: PropagateDatatoRefund that runs during the Refund Processing child Case creation on the Fulfillment Stage.
- In the Tracer output, open the event for the Data Transform: PropagateDatatoRefund and review the parent Complaint Resolution and child Refund Processing page values captured at run time.
- Analyze the data transform that maps the parent Compensation Amount to the child Refund amount. Identify the missing or incorrect mapping.
- Modify the PropagateDatatoRefund data transform so that the parent Compensation Amount is mapped to the child Refund amount and Save your changes.
- Create a fresh Complaint Resolution Case and confirm that the Refund Processing child Case now reflects the correct Refund amount.
Available in the following mission:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?