Linking Cases and Case Types in Constellation applications

4 Tasks

35 mins

Pega Platform '24.2

Pega Platform '23

Visible to: All users

Intermediate

Pega Platform '24.2

User Experience

Constellation

English

Scenario

During the application design phase, the business stakeholders for Sweet Life determined the need to establish relationships between Cases. For example, Sweet Life must recognize similar Incident Cases easily so that the management can evaluate its Caseload more efficiently.

Another business requirement of the Tell Us More application specifies that data related to the shipping process must transfer between the Incident and Ship Parcel Cases.

To facilitate this functionality, you are tasked with configuring the Link Similar and Shipping Service Views in the Incident Case Type. 

The following table provides the credentials you need to complete the challenge:

Role	User name	Password
System Architect	Author@SL	pega123!

You must initiate your own Pega instance to complete this Challenge.

Initialization may take up to 5 minutes so please be patient.

• Log In

Challenge Walkthrough

Detailed Tasks

1 Configure the Link Similar View

1. In the Pega instance for the challenge, enter the following credentials:
   1. In the User name field, enter Author@SL.
   2. In the Password field, enter pega123!
2. In the navigation pane of App Studio, click Case Types > Incident to open the Incident Case Type.
3. Click the Data Model tab, and then create a new field:
   1. In the Name field, enter Similar Incidents.
   2. In the Type field, select Query.
   3. In the Options field, select List of records.
   4. In the Data Page field, select Incident > Similar Incidents.
   5. Complete the Parameters section:
      1. In the IncidentType field, select Field, and then select Incident Type.
      2. In the IncidentSubType field, select Field, and then select Incident SubType.
      3. In the CaseID field, select Field and then select ID.
         
   6. Click Submit
4. Click Save.
5. Click the Workflow tab. 
6. Click the Link Similar Incidents Step, and then click Configure View.
7. Add the Similar Incidents field to the Link Similar View.
8. Click Similar Incidents to edit the field configurations:
   1. Select the Override parameters checkbox.
   2. In the IncidentType field, select Field, and then select Incident Type.
   3. In the IncidentSubType field, select Field, and then select Incident SubType.
   4. In the CaseID field, select Field and then select ID.
   5. In the Display as field, select Table.
   6. In the Columns section, delete Primary Fields.
   7. Add the following fields as shown:
      • ID
      • Incident Type
      • Incident SubType
        
9. Click Back to return to the Link Similar View.
10. In the Instructions list, select Override Case Step instructions.
11. In the Instructions text field, enter Link this Incident Case to similar Incident Cases in past for better root cause analysis.
    
12. Click Submit, and then click Save.

2 Add the Shipping Service Data Type to the Incident Case Type

1. Switch to Dev Studio, and then in the navigation pane, click Data types.
2. Click the Options arrow to the right of Data types, and then select Show or hide existing data types.
   
3. In the Data Types window, click Application, select the Shipment checkbox, and then click Apply.
   
4. Select the Shipping Service checkbox, and then click OK.
   

Note: Log out of the Sweet Life application, and then log back in for the changes to take effect.

3 Configure the Shipping Service View

1. In the navigation pane of App Studio, click Case Types > Incident to access the Incident Case Type.
2. Click the Data Model tab, and then create a field with the following details:
   1. In the Name field, enter Shipping Service.
   2. In the Type list, select Picklist.
   3. In the Display As list, select Drop-down list.
   4. In Picklist options list, select Data Page, and then select Shipping Service > List Shipping Service.
   5. In the Display field list, select Service Name.
   6. Click Submit.
      
3. Click Save.
4. Click the Workflow tab. 
5. Click the Dispatch shipment Step, and then Configure View.
6. Add the following fields to the Dispatch Shipment View:
   • Gift SKU
   • Shipment notes
   • Shipping Service
7. Drag the Gift SKU field to the second position.
8. In the row for each field, click the Gear icon to configure all three fields as always required.
9. In the Instructions list, select Override Case Step instructions.
10. In the Instructions text field, enter Confirm shipment details.
11. Click Submit.
    
12. Click Save.

4 Configure the Ship Parcel Case

1. Switch to Dev Studio.
2. In the App Explorer, expand SL-TellUsMore-Work-ShipParcel > Data model > Data Transform, and then click the CreateShipmentCase Data Transform.
3. Click Save As, and then click Create and open to open an editable version of the CreateShipmentCase Data Transform.
4. Pass the Shipping Service property from the Incident Case to the Ship Parcel Case by adding the following row to the CreateShipmentCase Data Transform:
   1. Create a set action with a .ShippingService.ServiceName target equal to a ParentPageParamName.ShippingService source.
   2. Move the set action to line 1 of the Data Transform.
   3. Click Save.
      
      Note: The ShippingService property in the Incident Case Type is a scalar property and in the Shipment Case Type it is defined as page.
5. Switch to App Studio, open the Ship Parcel Case Type, and then click the UX tab.
6. Click the Other Views tab, and then open the Schedule deliver View.
7. In the Schedule deliver View, delete the Shipping Service and Courier fields.
   Note: These fields are now included in the Shipment details Field Group.
   
   Note: If you receive an error message and see a Save Failed status for the View, click Back, and then reopen the Schedule deliver View. The Shipping Service and Courier fields are no longer displayed, and the View saves as originally intended.
8. Click Save.

Confirm your work

1. In the header of App Studio, click Preview.
2. Create two new Incident Cases with the following configurations:
   1. In the Incident Type field, select Product faulty or unsafe.
   2. In the Incident SubType field, select Product not as described.
3. Complete all the fields and move past Create Incident Assignment. 
4. Create a third Incident Case with the same configurations for the Incident Type and Incident SubType fields in step 2.
5. Complete the required fields, and then proceed to the Eligibility check Assignment.
6. On the Eligibility check Assignment, select Eligibility decision as Eligible.
7. Proceed to the Handle Ticket Assignment, and then select Replacement as the resolution method.
8. Proceed to the Link Similar Incidents Assignment, and then confirm that the first two Cases are displayed.
   
9. Progress to the Dispatch shipment Assignment, and then complete the required fields while taking note of the Shipping Service that you select.
   
10. Click Submit.
11. Confirm that the application routes you to a newly-created Ship Parcel Case and that the shipping service information has been transferred correctly.
    

---

This Challenge is to practice what you learned in the following Module:

• UI authoring in Constellation v2

---

Available in the following mission:

• Constellation Adoption v2