Events¶

An event marks something that happens outside the normal task flow: the process starts, the case waits, a message leaves the process, or the case ends. What an event does depends on where it sits and on its type.

Right-click an event and open its type menu — Start Event Type, Intermediate Event Type, End Event Type or Boundary Event Type — to change it.

Start events¶

A process begins with exactly one start event. Start Event Type offers:

Type	Meaning
Empty	The case starts when a user starts the process
Receive Message	The case starts when another process sends the matching message
Timer	The case starts on a date, or on a daily, weekly or monthly schedule
Conditional	The case starts when a condition over the process data becomes true
Signal	The case starts when the matching signal is broadcast

A start event can also carry a web entry, which gives the process a public form and a link that starts cases without a session.

Timer and conditional starts are not evaluated by the browser: they need the scheduler. Without it the diagram saves and the option does nothing, and the product tells you so — Please configure cron to wait for time event and Please configure cron to create cases in base to a condition.

Start timer¶

Open the properties of a start timer with no previous data. The fields are empty, not pre-filled with the last configuration.
Choose A date and time and pick a date and a time. Hours, minutes, and seconds have their own labels; the bin icon clears the date instead of keeping the old value.
Choose Daily, Weekly, or Monthly. Days run from Monday to Sunday, and month names are translated (including May in Spanish).
Invalid values such as day 00 and hour 25 are refused with a readable message — never with technical column names like tmrevn_day.
With a narrow window, the "required field" message appears at the end of the form without breaking the layout.

Intermediate events¶

An intermediate event sits in the middle of a flow and either waits for something or sends something.

Catching events — Receive Message, Timer, Conditional, Signal — hold the case until the event happens.

Throwing events — Email Message, Send Message, Signal — send something and let the case continue. The email and message bodies are edited in the event's Properties; a message carries the fields you defined in its message type.

Intermediate timer¶

An intermediate timer offers Wait for and Wait until specified date/time. Wait for pauses the case for a period; the second option pauses it until a date and time.

End events¶

End Event Type offers:

Type	Meaning
Empty	Ends this path
Email Message	Sends an email when the path ends
Message	Sends a message to another process
Error	Ends the path as an error
Signal	Broadcasts a signal
Terminate	Ends the case immediately

Use Terminate when a case must stop even if other branches are still open. An empty end event only closes the branch that reached it.

Boundary events¶

A boundary event is attached to the edge of a task and fires while that task is running: Receive Message, Timer, Conditional, Signal, Error. It is how a task gets a timeout or an alternative exit without changing the main flow.

Messages and email¶

Receive message: the case title and the variable table are saved and reloaded correctly. A form opened on an event without incoming or outgoing connections shows a notice but stays usable. Long variable-table headers are not cut.
Email events: pasting HTML into the body and opening the preview renders the HTML as formatting, not as source code.
With a narrow window the form scrolls internally and fields do not overlap.

What the canvas refuses to save¶

A start event needs an outgoing connection.
An intermediate event needs an incoming and an outgoing connection.
An end event needs an incoming connection.
A start event must not have outgoing message flows.

Gateways — how the paths between events are chosen.
Conditions — what a conditional event evaluates.
Web entry — the public form of a start event.
Case scheduler — scheduled actions on an existing case.