Assigning Primary Fields, Case tabs, and more in Constellation

6 Tasks

45 mins

Pega Platform '24.2

Pega Platform '23

Visible to: All users

Intermediate

Pega Platform '24.2

User Experience

Constellation

English

Scenario

Stakeholders at Sweet Life Inc are extremely interested in how a Pega application built on the Constellation UI can make Case processing easier for Case workers and Dispatchers. As a result, you have been tasked with incorporating Constellation functionality, including Primary Fields, Case Tabs, the Details View, and Promoted Actions into the Tell Us More application.

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 Primary Fields in the Case Type Data Model

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, and then click the Data Model tab to access the Data Model of the Incident Case Type.
3. Click Primary Fields, and then in the Configure Primary Fields window, delete the following fields:
   1. Label
   2. Description 
4. Add the following Primary fields and sort them in the following order:
   1. ID
   2. Work Status
   3. Incident Type
   4. Incident SubType
   5. Eligibility Type
   6. Resolution Method
   7. Preferred Resolution Method
   8. Fraud Indicator
      
5. Click Submit, and then click Save.

2 Modify the Details View

1. In the Incident Case Type, click the UX Tab, and then click the Other Views Tab.
2. In the Partial section, click Details to open the Details View.
3. Note that the list of Primary Fields is already displayed in the Details View.
   
4. In the Primary Fields row, click the Gear icon, and then confirm that the Show heading option is inactive.
5. In the Details View, click Add > Fields > Customer > Views > Primary Fields > Add to add the Primary Fields View that is defined on the Customer data object.
6. Click the Gear icon, and then in the Field label field, enter Customer. Click Save.
7. In the Details View, add the Primary Fields View that is defined on the Product data object.
8. Click the Gear icon, and then in the Heading field, enter Product. Click Save.
   

3 Configure Case Tabs

1. Click Back, and then click the Full Page View Tab.
2. In the Tabs section, add the following new Tabs:
   1. Customer
   2. Product
3. Configure the Customer and Product Tabs to show their respective Primary Fields Views.
   

4 Configure the Case Summary View

1. Still on the Full Page View tab, in Summary section, add the following fields and sort them in the following order:
   1. Eligibility Type
   2. Incident Type
   3. Incident SubType
      

5 Configure a Promoted Action

1. In the Incident Case Type, click the Workflow tab.
2. Click the Optional Actions tab.
3. In the Process Stage, click Action > Collect information to add a new Stage-only user Action called Contact customer.
   
4. Configure the Contact customer Action View with Customer Data View.
5. Add a new field Contact notes of the type Text (paragraph).
   
6. Click Submit.
7. Click Save.
8. In the Incident Case Life Cycle, click the UX tab, and then click the Full Page View tab.
9. In the Options section, select the Show promoted Action checkbox and click Save.
   Note:  If the Options section is not available, click Actions > Refresh.
   

6 Configure What is Next information on the Confirmation View

1. In the Incident Case Type, click UX tab, and then click the Other Views tab.
2. In the Partial section, click Confirmation to configure the View.
3. Configure the Confirmation View:
   1. Add a Primary Fields (Customer) View, and then in the Field Label field, enter Customer.
   2. Add a Primary Fields (Product) View, and then in the Heading field enter Product, and select Show heading.
4. Note the What's next section of the Confirmation View.
   
5. Click Save.
6. Switch to Dev Studio. 
7. In the App Explorer, in the SL-TellUSMore-Work-Incident class, expand Data Model, and then click the PostReview Data Transform.
8. Note the following information in the WhatsNext Page list:
   • Your incident report will be analyzed
   • You might be contacted for more information
   • We will let you know about resolution in an email notification
9. Add the following additional entry to the PostReview Data Transform: "You will receive a survey for your opinion on the incident resolution process."
   
10. Click Save as > Create and Open > Save to save the updated version of the PostReview Data Transform.
11. In the App Explorer, in the SL-TellUSMore-Work-Incident class, expand Process > Flow Action, and then click the Review Flow Action.
12. Click Save as > Create and Open.
13. In the Edit Flow Action: Review page, click the Action tab, scroll down to the Post-processing section, and in the Apply Data Transform field, enter PostReview.
    
14. Click Save. 

Confirm your work

1. Switch to App Studio, and then click Preview.
2. Create a new Incident Case, and then complete all the necessary fields until you click Submit.
3. Review the full Incident Case to confirm the following details:
   1. The Summary panel includes the Incident Type, Incident SubType, and Eligibility Type fields.
   2. The Tabs section includes the Customer and Product tabs.
      
   3. The Confirmation View includes the Case Type, Customer, and Product Primary Fields, which includes Case-related information and What's next information.
      
   4. Click the the Details Tab, scroll down and confirm that it includes the Case Type, Customer, and Product Primary Fields, which includes Case-related information.
      
   5. Continue through the Case, and select Eligible as the resolution method.
   6. Progress to the Handle Ticket Assignment of the Process Stage.
   7. In the Summary panel, note that the value of Eligible Type field is Eligible. 
   8. In the Summary panel, confirm that the Contact customer Promoted Action is available as a button as well as from the Actions menu.
      

---

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