A Timer Start Event initiates a process instance based on a specified time or schedule.
Please note that a process definition version can accommodate only one Timer Start Event.
If a process definition contains versions with Start Timer Event nodes, only for the published version will generate a scheduler.
Depending on the node type, the following timer types can be configured:
Node Type | Date | Duration | Cycle |
---|---|---|---|
Timer Start Event | Yes | No | Yes |
Starting a process via registered timers requires sending a process start message to Kafka, necessitating a service account and authentication. For detailed guidance, refer to:
Specifies an exact date and time for triggering the event. You can use ISO 8601 date format for accurate date-time representation.
In this scenario, the Timer Start Event is used to trigger an employee onboarding process at a specific date and time.
Specifies a repeating interval for triggering the event. The cycle can be defined using ISO 8601 repeating intervals or cron expressions.
For each timer type, the following values can be configured:
Field | Validations | Accepted Values |
---|---|---|
Definition | Mandatory | - Process param |
- ISO 8601 formats (date/duration) | ||
- Cron expressions (cycle) | ||
Start Time | Only for Cycle | - ISO 8601 format (date-time) |
- Process param | ||
End Time | Only for Cycle | - ISO 8601 format (date-time) |
- Process param | ||
Active/ Suspended | Default: Suspended | - Active |
- Suspended |
The Start Timer Event supports either ISO 8601 formats or spring cron expressions for defining timer values.