A trigger is a configured action for an event to execute. In the case of start and end events, triggers are used to determine the action that must be performed when the event executes. With intermediate events, triggers can be placed directly on the designer canvas (that is, an intermediate event), or they can be added within a Service Node on the designer canvas. When they are added to a Service Node they are used to create an exception flow, which will be taken should the event execute instead of the Service Node.
Events are particularly useful for transmitting information across processes. For example, a Recruiting Process might use a Send Message trigger on an End event to send all employee information to an HR On-Boarding Process. The use of triggers within events allow you to distribute and collect data from various sources in a process. Also, the use of rule and time triggers allow you to change the flow of a process based on attributes from another process.
Each of the event types only support some of the triggers. The table below lists the different triggers that are supported by each event.
|Intermediate - Exception Flow|
On This Page