Using intermediate timer events
Use intermediate timer events to cause a delay between activities.
If a timer event is not attached to an activity, it causes a delay. The process waits for the timer to trigger before proceeding to the next activity. For example, if your BPD includes an activity that emails offers to customers and you want your internal sales team to follow up two days after the offers are mailed, you can place a timer between the two activities. The delay ensures that a specific amount of time passes between the completion of one activity and the start of another.
If the timer event is connected to an event gateway, the timer serves as a timeout. If the other events connected to the gateway do not trigger within the configured timeframe, the timer event triggers and the other events stop waiting.
- In an intermediate timer event, you can select only After Start of Parent Process or Subprocess, After Custom Date, and Before Custom Date. There is no option based on due date.
- There are no Boundary Event Details options.
To calculate the fire date of the event, the work schedule, holiday schedule, and time zone of the BPD are used. If the intermediate timer event is contained in a linked process, the work schedule, holiday schedule, and time zone for calculation of the fire date are taken from the top-level BPD.
The fire date of the timer is governed by the timer-use-activity-schedule property. See JR45433: ALLOW CONFIGURATION OF WORK SCHEDULE FOR ATTACHED TIMER for details on how to set this property.
If the timer-use-activity-schedule property is not set or is set to false, the default 24x7 work schedule and an empty holiday schedule are used for calculating the fire date.
If the timer-use-activity-schedule property is set to true, the Work Schedule, Holiday Schedule, and time zone settings of the root BPD are used, even if the timer is contained in a linked process.