Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

The Close button in HistoryAndAttachment behaves incorrectly



Using Pega 7.1.8 with Pega Customer Service (CS) 7.1.3, the out of the box (OOTB) Close button in HistoryAndAttachment is behaving incorrectly.

When a user clicks the Close button in Work- HistoryAndAttachment harness, the current case Stream name (pyStreamname) is modified to AutoClose which causes issues for any when rules monitoring the property mentioned.

Error Messages

Not Applicable

Steps to Reproduce

  1. Open a work object which opens the Review harness.
  2. Inside the harness have certain elements that are only visible if a when condition determines it is in Review mode (monitors pyStreamname).
  3. Click on Other Actions and click on Audit which uses the OOTB ViewHistory action. On click it opens a window.
  4. Click on close button in the window.
  5. Observe that when condition doesn't reflect the elements are in the review harness.

Root Cause

The issue here is that the close button that is in the HistoryAndAttachments harness (displayed in the Audit window), is a deprecated button which calls the AutoClose activity which in turns does a show-harness.

This harness has a non-auto generated section with javascript.

The show-harness, results in the recent updates to trigger which eventually overwrites the Declare_pyDisplay page that is why the modal dialog is empty the second time.


Perform the local change mentioned in the following support article:
Suggest Edit

Published August 1, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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

Pega Community 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
Contact us