Developing in Branches

1 Aufgabe

1 Std. 20 Min.

Pega Platform '26

Sichtbar für: All users Applies to: Pega Platform '26

Anfänger

Data Integration

Englisch

Szenario

In the Refund Processing Case Type of the Travel Management Customer Support (TMCS) application, stakeholders want to enhance how refund requests are categorized and analyzed.

Currently, the Root Cause Category field does not include sufficient options to classify refund-related issues effectively. To improve reporting and operational insights, stakeholders have requested additional values for this field.

Additionally, stakeholders want refund transactions to be executed only for approved requests. When a request is approved, the system updates the refund execution date and transaction status. Otherwise, no refund processing occurs.

At the same time, another team is working on a different part of the Refund Processing Case Type. To avoid conflicts, you must implement your changes in a development branch.

After you complete and validate your changes, you merge the branch into the main application ruleset.

Hinweis: 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:

Create and manage development branches.
Modify local lists in a property.
Merge branch changes into the main application.

Genaue Übungsschritte

1 Create a Branch

Solution Builder Intermediate Developing in Branches Doc Journey

Use the technical documentation linked in the Journey map above to complete the assigned tasks. The technical documentation might have more information than you need to complete the tasks.

Acceptance criteria

A development branch is created for the TMCS application:
- The branch is named UpdateRefund.
- The branch is associated with the TMCS application.
The RootCauseCategory field is updated in the Refund Processing Case Type class:
- A new version of the property is created and saved into the development branch.
- The local list for Root Cause Category includes the following new values: Customer Dissatisfaction, Chargeback, and Service Issue.
- Existing values remain unchanged.
The Initiate Refund Transaction data transform is updated in the Refund Processing Case Type:
- The data transform includes a condition to check .ApprovalStatus = "Approved".
- When .ApprovalStatus = "Approved", the data transform sets .RefundExecutionDate = @DateTime.CurrentDateTime() and .PaymentTransaction.TransactionStatus = "Refunded".
- If the condition is not met, the data transform exits without performing any mappings.
The development branch is successfully merged into the TMCS ruleset:
- After the merge, changes are available in the main application.
- The updated Root Cause Category values are visible in Refund Processing.

Directions

Create a development branch named UpdateRefund and associate it with the TMCS application.
Update the RootCauseCategory property and add the new values, as detailed in the Acceptance criteria.
Update the Initiate Refund Transaction data transform, as detailed in the Acceptance criteria.
Review and merge the UpdateRefund branch into the main application.
Save your changes.

In der folgenden Mission verfügbar:

Solution Builder Intermediate v1

Zur Mission zurückkehren

Hilfe erhalten

Wenn Probleme mit den Lerninhalten auftreten, lesen Sie bitte die Pega Academy Support FAQs.

Fanden Sie diesen Inhalt hilfreich?

Nein

Möchten Sie uns dabei helfen, diesen Inhalt zu verbessern?

Änderung vorschlagen