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

Buttons on the screenflow harness are not hidden



A local flow action with a custom button is configured with the “Hide the default Action Section buttons” checked. When this local action is launched from screen flow harness, it shows both the custom and the harness buttons. The expectation was that the harness buttons would be hidden because of the "Hide the default Action Section buttons" check on the flow action. Hiding the buttons is also not acheived by including the "pyCaseActionAreaButtons" section on the screenflow harness, as this only works on the Perform harness.

Error Messages

Not Applicable

Steps to Reproduce

1. Configure a screenflow
2. Configure a local flow action on this screenflow and check the
“Hide the default Action Section buttons” option on the flow action rule.
3. At runtime, when you arrive at this local flow action, verify if the out-of-the-box buttons on the screenflow harness are hidden because of the check in Step 2.

Root Cause

In a screenflow, the "Hide default action buttons" check does not hide the buttons because currently those buttons are at the harness level.

It is also not correct to conclude that by simply including pyCaseActionAreaButtons section on any harness, that should hide the flow action buttons.

The way this is working is the expected behavior of the product at this time.


An enhancement request, FDBK-20105, has been created for consideration by Pega Product Management.

Suggest Edit

Published August 26, 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