Using Boundary Timer Events
You can add a boundary timer intermediate event to all activity types except for user and manual activities. Based on the activity type, boundary events are:
Interrupting - when the boundary event interrupts the step activity. When the timer expires, the step stops and the process follows only the transition(s) from the boundary event.
Non-interrupting - when the 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.
A boundary event can have one or more output transitions. The output transitions from a boundary event do not support transition conditions.
When Dynamic Business Orchestrator receives the first input for a step with a event, it creates a timer object in memory. If Dynamic Business Orchestrator receives all step inputs before the timer expires, Dynamic Business Orchestrator cancels the timer.
When a server starts running the service of a step, Dynamic Business Orchestrator creates a timer object in memory. If the server finishes running the service before the timer expires, Dynamic Business Orchestrator 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. Dynamic Business Orchestrator publishes the document and the triggers for the specific target step, model, and model version.