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

Fields in the use case display as editable in Review harness



All fields in the use case display as editable in the Review harness.

Error Messages

Not Applicable

Steps to Reproduce

  1. Set the rule as editable or read- only in the child layouts or sections of the Review harness.
  2. Launch the portal. The Review harness displays when the respective case is opened. The case is editable.

Root Cause

This behavior is as per Pega product design.

When the child layout or control has the editable or read-only condition set, the editable or read-only condition on this respective child layout or control is honed instead of the parent's read-only condition.


Here's the explanation for the reported behavior of the Review harness being editable:

The Review harness is by default ‘read only’. In case, if all the child layouts or sections are set to ‘auto’, the ‘read only’ mode is fetched from the parent (in this case, the Review harness).

The Perform harness is set to ‘Editable’ by default. If all the child layouts or sections are set to ‘auto’, the ‘Editable’ mode is fetched from the parent (in this case, the Perform harness).

This is the basic principle of Inheritance.

However, in both the harnesses, when both the child
layouts or sections are manually set to ‘Editable/Read only’, the child layout attribute takes precedence.

In the reported scenario, the parent attributes are manually overridden based on the read-only condition.

Perform either of the following local-changes:

  • Configure two versions of the section, each with an Edit option and display each version conditionally with the Visible When.

    Note: It may be an overhead to have two versions of sections. However, this is the expected behavior (where the Review Harness may not guarantee a complete read-only mode, thus, ignoring the child layout or section attributes).

  • Perform circumstancing.
  • Customize the When condition at the user end based on the requirement to have read-only or editable content in the Review or Perform Harness.

    For example, set the When condition as below:

    param.Readonly = -1

Published August 15, 2019 - Updated December 2, 2021

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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