Triggering Custom Code
Triggers and actions allow you to interact with changes that occur in the system. You can trigger code to run in-between processes, to prepare the environment, for example, or react on a process change or status with triggers and process definition actions. The main difference between the two is the scope. Actions are limited to the object, and triggers are partition-based and apply to all process definitions ( Before Job triggers) or all objects ( Before Definition Change trigger) in the partition of the trigger.
note
A process has the same partition as the queue it ran in.
When you want to trigger code for processes, you should decide which solution to implement based on the amount of affected process definitions and the total amount of process definitions that you use regularly. Triggers are a little more expensive in terms of performance, because they fire for every process. Actions require you to specify them on every affected process definition.
- Using Triggers.
- Trigger Examples.
- Using Actions.
- Customizing Processes with Actions.
- Executing Your Own Classes.