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

Value entered in Currency control is not retained on focus out



Value in the Currency control is not retained on, when the user tabs out of the control. On entering a value, the property is blank. The Declare Expressions are triggered; however, they are restored to the original value. This occurs sporadically. 

Error Messages

Not Applicable

Steps to Reproduce

  1. Configure a section with Currency control property with the below action, 

    OnChange >  Post Value, Refresh Section (invoke the activity to validate the property).

  2. Search a case and open it.
  3. Enter a value in the Currency control and tab out.
  4. Move the focus out of the Currency control.

Root Cause

The custom section has the design configured twice for the same property based on the Visibility condition. Here, the ‘Run visibility condition on client’ is enabled in  the property and the dynamic layout contains this property.

Below is the explanation on setting the 'Run visibility on Client'.

Run visibility on client: When the same section or property is included in multiple sections and configured with 'Run visibility condition on client', duplicate elements are generated on the Document Object Model (DOM) with the same name or ID.
Hence, while submitting a form or a Post Value action, the hidden values of the name or ID are submitted. The 'Run visibility on client' must be selected, only when the client uses different properties in two or more sections and displays them through the Visible condition expression, such that evaluation occurs at the client side instead of the server side.

Referring to the same property in the same or multiple sections on the UI is not supported.
It is not recommended to configure the 'Run visibility client' option on the same property in the same or different sections. The design must be such that, the same property reference must not be rendered as editable in two or more places including non-visual inputs to the user, but in the DOM (that is, a property reference must not be bound to two or more input elements in the document).


Perform the following local-change:

Disable the ‘Run visibility condition on client’ on dynamic layouts which contain the properties.

Published July 11, 2020 - 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