Transitions and Logic
Transitions are the links (arrows) that connect activities together. They carry the process logic: Conditions, Notifications and Quick Actions.
1. Transition Conditions
By default, a transition is taken if it is the only exit. If multiple paths are possible (Gateways), you must define conditions.
Condition Editor
By double-clicking on a transition, you open the condition editor.

You can compare:
- The decision from the previous step (e.g: If Validation = "Approved").
- The value of a field (e.g: If Amount > 1000).

The available comparators allow you to handle all common cases (Equals, Contains, Is empty, etc.).

2. Notifications (Emails)
You can send automatic emails when passing through a transition (e.g: Notify the requester that their request is approved). Access: Right-click on the transition > Notification.

Configuration
-
Recipients: Choose from Roles, Actors (e.g: Initiator), or enter a fixed address.

-
Template: You can use a predefined template or write the email directly.

-
Content: Use variables to personalize the message.
$Titre$: Document title.$Link$: Link to open the document.
3. Automatic Actions (No-Code)
It is not necessary to create a script for simple operations. Transition "Actions" allow you to modify fields automatically. Access: Right-click on the transition > Actions.

Usage examples:
- Set the document status to "Closed".
- Fill the "End Date" with today's date.
- Store the validator's name in an "Auditor" field.
Adding an action
Select the field to modify and the value to assign to it.

[!TIP] Always favor these transition actions over complex scripts when possible. It's more readable and easier to maintain.
4. Gateways
To organize complex flows:
- XOR (Exclusive): Only one route will be taken (the first one whose condition is true). Represented by a diamond with a cross.