Debugging Constellation applications

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

Task 1: Access View JSON data

• The pxEnableC11nDev When rule is set to true.
• The pyConfirm View Rule for the SL-TellUsMore-Work-Incident class is opened and after enabling Mark as custom the JSON is visible.
• In the JSON, the property displayed by .pyWhatsNext is identified.

Task 2: Examine View Rules using the Tracer

• In the Research Case Type, an Address field of type Address is added to the Data Model.
• The Tracer is opened with View Rules enabled under Event Types to Trace.
• After submitting the Debug Assignment, the Resource: /application/v2/assignments entry is expanded in the Tracer.
• The DATA-ADDRESS-POSTAL!PYADDRESSFORM link is located by searching for View Start entries tied to pyAddressForm, and the JSON metadata is reviewed.

Task 3: Explore View metadata with the UI Inspector

• In the Research Case Type, the Details Partial View is updated: the Primary fields View is removed and the Address field is added.
• The UI Inspector is launched using the following console command: PCore.getDebugger().toggleInspector();
• The following components are examined in the UI Inspector:

  Component	Detail
  View	pyHome
  Component	AppAnnouncement (data source: D_pyAnnouncements)

• In the pyInitAnnouncements Data Transform, the following steps are added:

  Step	Action	Target	Value
  Step 2	Append and Map	.pxResults	New page
  Step 2.1	Set	.pyLabel	"New authoring experience with Constellation"

• After relaunching the Customer Portal, the new announcement bullet is visible.

Task 4: Debug DX API calls

• The DebugPegaAPI Dynamic System Setting is set to true.
• In the Tracer, the Resource: /application/v2/data_views/D_pyC11nOperatorsList entry is expanded.
• The pxGetData Automation is located, and the Data Transform End event Pega-API-DataExploration pzTranslateViewPageToJSON is found and the JSON list is reviewed.

Task 5: Review the Data Page cache

• In the Customer Portal, a new Incident Case is created and navigated to the Contact Info Step.
• The following console command is used to explore cached Data Pages: PCore.getDataPageUtils();

Task 6: Examine React changes with Redux DevTools

• The Redux DevTools browser extension is installed.
• A new Incident Case is created and navigated to the Determine Incident Type Step.
• Action information updates in Redux are observed as the form is filled out, and changes are noted as the Case progresses.

Directions

1. Locate and enable the pxEnableC11nDev Dynamic System Setting, open the pyConfirm View Rule for the SL-TellUsMore-Work-Incident class, and identify the .pyWhatsNext property in the JSON as detailed in the Acceptance criteria.
2. Open the Research Case Type, add the Address field to the Data Model, open the Tracer with View Rules enabled, create a Research Case, submit the Debug Assignment, and locate the DATA-ADDRESS-POSTAL!PYADDRESSFORM link as detailed in the Acceptance criteria.
3. Update the Details Partial View of the Research Case Type, use the UI Inspector to examine the pyHome View and AppAnnouncement component, update the pyInitAnnouncements Data Transform as detailed in the Acceptance criteria, and verify the announcement appears in the Customer Portal.
4. Enable the DebugPegaAPI Dynamic System Setting, trace the DX API call for D_pyC11nOperatorsList, and locate the pzTranslateViewPageToJSON Data Transform End event as detailed in the Acceptance criteria.
5. Create a new Incident Case in the Customer Portal, navigate to the Contact Info Step, and use the browser DevTools console command to review cached Data Pages as detailed in the Acceptance criteria.
6. Install the Redux DevTools browser extension, create a new Incident Case, navigate to the Determine Incident Type Step, and observe how Action information and changes are recorded in Redux DevTools as detailed in the Acceptance criteria.