Timer Boundary Event

Introduction

Process execution is delayed until a certain point in time is reached or a particular duration is over.

Properties

General

Attribute	Type	Description	Category
Model Id	Text	Model Id identifies the element within the process model.	The model id, name and documentation properties can be found on any element. They are used respectively to uniquely identity the boundary event, to give it a user-friendly name and to add a free-form description.
Name	Text	The name of the element. This is the name displayed in the diagram.
Documentation	Multiline Text	A free-form text that can be used to explain details about the particular element.
Timer configuration	ComplexTrigger	Configuration of the timer event. * Date: An absolute date and time. * Duration: A duration relative to the start date of the event. * Cycle: A cycle which allows you to configure recurring timers. * Technical: An expression which must resolve to either a date, a duration or a cycle in the ISO 8601 format. Time cycles can also be specified as a cron expression.	Configuration of when the timer will fire. Use 'Cycle' when the timer should be repeating, which only applies when the boundary event does not cancel the activity it is attached to. Use 'Duration' if the timer needs to fire after a certain time after the creation of the boundary event. Use 'Date' to set a fixed time for the timer to fire. By default, triggering the boundary event will cancel the activity it is attached to. To change this, uncheck the 'Cancel Activity' checkbox. A new flow of execution starting from the boundary event will be started concurrently.
Cancel activity	Boolean	Denotes whether the activity should be canceled or not, i.e., whether the boundary catch event will complete the activity it is attached to.
Job Category	Text	When set, the underlying generated job will have a Job Category, which will be executed only by Application Servers, where the Process Engine has enabledJobCategories set to this category.

Advanced

Attribute	Type	Description	Category
Execution listeners	List	Allows invoking custom after certain lifecycle events. Start: Executes after the activity has been started. End: Executes after the activity was completed. Transition: When defined on a sequence flow, executes once the flow is transition is taken.	Execution listeners are used to add logic on certain lifecycle events. Typically it is used to add extra technical logic which shouldn't be visible in the BPMN process model.

Visual

Attribute	Type	Description	Category
Font size	Selection: 8 9 10 11 12 14 18 20 24 36 48 72	Font size.	Visual properties that determine how the boundary event is shown in the diagram. This has no impact on the runtime execution.
Font weight	Selection: Normal Bold	Select the style between bold and normal.
Border color	Color	The border color of the element in the diagram.
Font style	Selection: Normal Italic	Select the style between italic and normal.
Font color	Color	Select a font color.
Background color	Color	The background color of the element in the diagram.

List Attribute Details

Execution listeners

Attribute	Type	Description
Event	Selection: Start End Take	The lifecycle event. The 'Take' event is only available for sequence flow.
Class	Text	Fully qualified classname of a class to be invoked when executing the task. The class must implement either JavaDelegate or ActivityBehavior.
Expression	Text	JUEL Expression to be executed when the task is started. Expressions allow you to interact with the backend by calling services, making calculations etc. You can find more information about expressions in the documentation.
Delegate expression	Text	Delegate Expression to be executed when the task is started. A delegate expression must resolve to a Java object, for instance a Spring bean. The object's class must implement either JavaDelegate or ActivityBehavior.
Fields	List

Fields

Attribute	Type	Description
Name	Text	The name of the element. This is the name displayed in the diagram.
String value	Text
Expression	Text	JUEL Expression to be executed when the task is started. Expressions allow you to interact with the backend by calling services, making calculations etc. You can find more information about expressions in the documentation.
String	Text