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

Exception displays differently in different environments



When user enters a large integer value (For example, 999999999), validation message displays. However, the way the message displays is different in the lower environments and the Production environment. In lower environments, the Contact system administrator exception displays on the popup and an indefinite Busy indicator displays for the work object. However, in the Production environment, the exception (just exception as error message) occurs on clicking the Next or Submit button.

Error Messages


Steps to Reproduce

  1. Define a local property of activity or data transform
  2. Assign a large integer (For example, 999999999)
  3. Apply Math calculation on the property

Root Cause

A software use or operation error. The difference in the way exception displays in different environments is due to the difference in the flow of execution of rules based on the data.


Perform the following local-change:
Add a validate rule to handle abnormal behaviors (exceptions) when user inputs large integer values.


Published December 2, 2019 - Updated October 8, 2020

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