Skip to main content

Challenge

Debugging von Anwendungsfehlern

This content has been updated. Hier klicken für das Fortsetzen Ihres Fortschritts in der neuesten Version.

Szenario

Als Teil der Bearbeitung eines Unterstützungsanfrage-Cases kopiert die Pannenhilfe-Anwendung die ausgeführten Services aus dem untergeordneten Services-Case in den Case „Assistance Request“. Beim Testen der Konfiguration dieses Features stellen Sie fest, dass Unterstützungsanfrage-Cases nicht im untergeordneten Case angegebene Service-Elemente enthalten, wie im folgenden Screenshot dargestellt. Verwenden Sie das Tracer-Tool für das Debugging des Problems und beheben Sie dieses.

Side-by-side of Assistance Request case and Service case showing different selected services

In der folgenden Tabelle finden Sie die Anmeldedaten, die Sie zur Durchführung der Challenge benötigen.

Rolle Benutzername Kennwort
Application Developer author@gogoroad pega123!

Challenge-Schritte

Sie müssen zum Abschließen dieser Challenge Ihre eigene Pega-Instanz starten.

Die Initialisierung kann bis zu 5 Minuten dauern, bitte haben Sie Geduld.

Genaue Übungsschritte

1 Configure Tracer settings

  1. In the footer of Dev Studio, in the Developer Toolbar, click the Tracer icon to display the Tracer window.
    Tracer icon in the developer toolbar
  2. In the Tracer window, in the toolbar, click Settings to check the Tracer tool settings. The Tracer Settings window is displayed.
    Settings button in the Tracer toolbar
  3. In the Tracer Settings window, verify that the following events to trace and break conditions are selected.
    Tracer Events to Trace and Break Conditions section
  4. In the Rulesets to Trace section, click Deselect All.
  5. Select the GoGoRoad check box to trace rules in the GoGoRoad ruleset.
    Tracer Rulesets to Trace section
  6. Click OK to dismiss the Tracer Settings window.

2 Start the Tracer tool and identify candidate events

  1. In the Tracer window, in the toolbar, click Clear to clear any previous logs.
    Clear button on the Tracer toolbar
  2. Click Pause to pause the Tracer tool. To reduce the number of irrelevant events the Tracer records, play the Tracer before you encounter the error.
  3. Minimize the Tracer window.
  4. Create a new Assistance Request case.
  5. Advance the case to the Select services view.
  6. Open the Tracer window, and then click Play to start the Tracer tool.
  7. Minimize the Tracer window.
  8. In the Unlock and Replacement key rows, in the Quantity fields, enter a value of 1.
    Selected services view
  9. Click Submit. The Review service summary view is displayed.
  10. Open the Tracer window, and then click Pause to pause the Tracer tool. In the Tracer results, the following events set the values of SelectedServices(1) and SelectedServices(2)
    Tracer results
    Hinweis: Your line numbers may differ.
     
  11. In the Tracer results, click a line of interest in the STEP METHOD column to view more details. The Properties on Page TraceEvent window is displayed. The Event Key row shows the class and rule name, which is TESTVALUESFORINVOICING
    Properties on Page TraceEvent window for event 36
  12. Close the Properties on Page TraceEvent window.
  13. Close the Tracer window.

3 Locate and correct the source of the error

  1. In the header of Dev Studio, in the search bar, enter TestValuesforInvoicing, and then press the Enter key. The search results are displayed.
    Search results for testvaluesforinvoicing
    Hinweis: If the system fails to return a search result, use either the App Explorer to locate the rule in the AssistanceRequest class, or the Records Explorer to locate the rule in the Data Transform rule category.
  2. Click the TestValuesForInvoicing data transform. The Test values for Invoicing data transform has hard-coded values for the first two Selected Services line items. The data transform was included for testing purposes and should be removed. 
    Test values for invoicing data transform
  3. Click Actions > View references to see where the rule is referenced. In the pane on the right, in the Referencing rules tab, the InvoiceCustomer flow is displayed.
    Data transform testvaluesforinvoicing referencing rules
  4. Hover over GoGo-GoGoRoad-Work-AssistanceRequest-InvoiceCustomer, and then click the Edit icon to open the flow rule
  5. Between the start shape and the Review service summary assignment, right-click the connector, and then click View properties.
    View properties in the first connector of the Invoice Customer flow rule
  6. In the Connector properties window, in the Set properties section, verify that the TestValueForInvoicing data transform is executed from this connector.
    Connector properties with test values for invoicing data transform applied
  7. Clear the Data transform field, and then click Submit to dismiss the window.
  8. Click Save to save the flow rule.

4 Confirm your work

  1. Create a new Assistance Request case.
  2. Advance the case to the Select services view.
  3. In the Unlock and Replacement key rows, in the Quantity fields, enter a value of 1.
  4. Click Submit. The Review service summary view is displayed.
  5. Verify that the correct services are displayed.
    Review service summary displays the correct values


In den folgenden Missions verfügbar:

Wenn bei Ihrer Schulung Probleme auftreten, lesen Sie bitte die Pega Academy Support FAQs.

Fanden Sie diesen Inhalt hilfreich?

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

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice