Skip to main content

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

Develop applications faster with nested Declare Trigger rules (8.5)

Updated on May 3, 2021

For faster application development, you can now define complex correlations between events in your case types by nesting Declare Trigger rules. Declare Trigger rules invoke activities when a specified action takes place in a case. By nesting Declare Trigger rules, you avoid implementing unclear logic in your application. You can nest as many levels of rules as your business use case requires. For example, in an application for reviewing job candidates, you can create a Declare Trigger rule that starts a child case every time a candidate requires a background check. When the background check is finished, the second Declare Trigger rule prompts your application to create a document with the results and attach it to the case. Then another Declare Trigger rule invokes an activity that sends an email with the background check results to the job candidate.

The following figure shows the defining of a Declare Trigger rule:

Configurations on the Trigger tab of the Declare Trigger rule form
Configurations on the Trigger tab of the Declare Trigger rule form

You can nest only the Save and Save and types of Declare Trigger rules that run immediately.

For more information, see Declare Trigger rules.

  • Previous topic Navigate easier across business logic-based routing cards (8.5)
  • Next topic Plan successful microjourneys in App Studio (8.4)

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

Close Deprecation Notice
Contact us