Support Article

OOTB pyCaseHistory is not rendered

SA-38040

Summary



Application in UAT is upgraded from Pega 7.1.8 to 7.2.2 and noticed some different behavior of an Out-of-the-box (OOTB) Pega section named pyCaseHistory.

In a harness, user can search cases.

The section for doing the search displayed the found cases in a repeating grid, using master-detail operation to invoke another flow-action to populate the case data.

This flow-action section embedded the OOTB Pega section pyCaseHistory in it as a collapsed section which in turns uses pxLocalAction.

On Pega 7.1.8, pyCaseHistory is performing as expected and populate the case audit history, but on Pega 7.2.2 it does not get triggered and no audit history appear on screen.


Error Messages



Not Applicable


Steps to Reproduce



1. Configure a Repeat Grid.
2. Set the operation of Repeat Grid as Master-Detail invoking a LocalAction.
3. For the Local Action, configure a section including the OOTB pyCaseHistory rule.
4. At runtime, search the case, click on the row of Repeat to show detail information.

Actual Behavior: Case History information is not displayed in Pega 7.2.2.
Expected Behavior: Case history information is to be displayed.


Root Cause



The Pega Work-.pyCaseHistory uses the flow-action pyCaseHistoryContent to retrieve the audit history, but the page context for this flow-action is changed between Pega 7.1.8 and 7.2.2.

In Pega 7.1.8, the output is saved in a top level page called workPage, but in Pega 7.2.2 it is another name and hence the output on the screen is not observed because it is pointing to workPage.

Resolution



Perform the following local-change step:

Customize the pre-activity of pyCaseHistoryContent to point the output back to workPage and then it works.


Published May 16, 2017 - Updated June 2, 2017

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.