Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

About Declare Trigger rules

Updated on April 5, 2022

Create Declare Trigger rules to cause an activity to run when instances of a specific class are created, updated, or deleted in the database. This implements a form of forward chaining.

The following tabs are available on this form:

For each Declare Trigger rule, the Pega Platform monitors database operations for objects of the Applies To class (and concrete classes derived from that class). During database commit processing, forward chaining processing may trigger — start execution of — the activity identified in this rule.

For example, a Declare Trigger rule can execute an activity each time an instance of Data-Party-Person class is saved with a modified ZIP code (property Data-Party.pyPostalCode ). The activity might send an email message to the sales representative whose territory includes the new address. Similarly, a Declare Trigger rule can implement a form of logging or audit history for a class, recording the date, time, and other facts.

Where referenced

No other rules explicitly reference Declare Trigger rules. After you save a Declare Trigger rule, it is run immediately and as needed.

Access

Use the Application Explorer to access Declare Trigger rules that apply to work types in your application. Use the Records Explorer to list all Declare Trigger rules available to you.

Category

Declare Trigger rules are instances of the Rule-Declare-Trigger class. They are part of the Decision category.

Have a question? Get answers now.

Visit the Support 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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us