Timer Event

Timer events are triggered by a defined timer. They can be used to start a process, as intermediate events or as boundary events. The timer itself can be a defined Date, a Duration or a Cycle.

In our first process, we will take a deep dive into the extensive jobs of your profs. Let's consider the high-level process of planning and giving lectures: process_timer

Durations#

Your first task is to enter the process variables into the model and check the successful execution in the Camunda web interface. Let's start with configuring the timer event. Select the event and Choose "Duration" as a Timer Definition Type. After that you need to provide a timer definition. The specification of seconds, minutes, days, months etc. is defined according to ISO 8601. For our case, it should be sufficient to use a timer from a few seconds to a few minutes. Enter PT1M in the field for a duration of 1 minute. Also test the process for a duration of PT30Sseconds by entering T30S.

Bind to form field values#

Let the professor select the time in seconds in the "Plan Lecture" task. Bind the value to the timer definition.

Hint: You can use an expression in the timer definition e.g. = "PT" + selection + "M" If the value "selection" contains "30", this would result in PT30M.

Cycles#

The third option Cycle makes no sense in our use case and will not be executed successfully. This definition type is often used for periodically starting processes for maintenance or other QA systems. The formatting of the intervals also follows ISO 8601, for further information see the Camunda docs.