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

Pega Triggers are missing on the Upgraded schema



Post upgrade to Pega 7.3.1, unable to view triggers in the New schema. The application does not have custom triggers. The out-of-the-box triggers, which existed in the Rules schema, do not display in the Upgraded schema.

Error Messages

Not Applicable

Steps to Reproduce

Perform the below steps to upgrade from Pega 7.1.7 to Pega 7.3.1.
  1. Run the Migrate script to migrate data from the Rules schema to the newly created schema.
  2. Run the Upgrade script to upgrade the Rules schema.
  3. Run the Migrate script to generate the Rule schema objects.
  4. Run the Upgrade script to upgrade the data schema.

Root Cause

This behavior is as per Pega product design.


Here’s the explanation for the reported behavior:

Database triggers are removed in the higher versions of Pega to avoid performance lag.



Published August 28, 2018 - 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