About Boundary Timer Event Timer Conditions
You can add a boundary timer intermediate event to all activity types except for user and manual activities. For more information, see
Adding a Boundary Intermediate
Event. The timer event can be interrupting or non-interrupting, depending on the activity type.
An interrupting boundary event interrupts the step activity, so when the timer expires, the step stops and the process follows only the transition(s) from the boundary event.
A non-interrupting boundary event does not interrupt the step activity. When the timer expires, the process follows the transition(s) from the boundary event as well as the transition(s) from the activity as it normally would if there were no timer present.
A boundary timer event can have one or more output transitions. The output transitions from a boundary timer event do not support transition conditions. For information about configuring timer events, see
About Boundary Intermediate Timer Events.
When the Process Engine receives the first input for a step with a timer event, it creates a timer object in memory. If the Process Engine receives all step inputs before the timer expires, the Process Engine cancels the timer.
When a server starts running a step's service, the Process Engine creates a timer object in memory. If the server finishes running the service before the timer expires, the Process Engine cancels the timer.
If the timer expires, the step has timed out and transitions to the timeout transition defined for the step. The step produces a process transition document that identifies the next step to run. The Process Engine publishes the document and the triggers for the specific target step, model and model version.
