In the Workflow Editor, processes are defined as BPMN models. BPMN (Business Process Model and Notation) is the description standard for process automation and defines how tasks, events, and branches are modeled graphically. You open the editor via the Workflow tab in the settings by clicking a workflow.
Base configuration of a process
You set a process’s central properties in the right-hand sidebar under Custom Properties:
| Property | Effect |
|---|---|
| Startable | Marks the process as executable, so it can be started within a case. |
| Hideable | Allows technical workflows to be started within a case without appearing in the case view – for purely technical processes that aren’t relevant to the user. |
| Mark as Stale | Disables outdated workflows and hides them from the overview. |
The button bar
The following functions are available along the top edge of the editor:
- Save – saves the workflow definition.
- Compare – compares two workflows to spot differences.
- Import – uploads an existing process definition in XML format.
- Create element – opens the catalog of all ServiceTasks and catch events available in DEPLAW. A wizard lets you set an element’s input parameters; brief documentation is shown for each task. Finish inserts the configured element at the desired position.
- Element documentation – opens a modal with the complete documentation of all ServiceTasks and catch events.
How to add an element
Every building block enters the process through a guided wizard via Create element:
-
Open the catalog
Click Create element. The catalog of all ServiceTasks and catch events available in DEPLAW opens.
-
Select the function
Choose the appropriate task. Brief documentation is shown for each entry, so you can see what the function does and which inputs and outputs it expects.
-
Set parameters in the wizard
Fill in the input parameters. In the headers, the full FEEL function set is available – so you can pass calculated values instead of fixed inputs.
-
Finish & place
Use Finish to insert the configured element at the desired position in the editor.
-
Connect & name
Drag a sequence flow from the predecessor to the new element and give it a meaningful name in the side panel. The ID must be unique within the workflow.
-
Save
Save the definition with Save. A new version is created – older ones remain comparable via the version information.
Toggles below the button bar
Two switches display additional runtime and version information:
- Show element information – when this toggle is active, you can click an element to see how many times it has already executed (green) and how many instances are currently waiting at this element (blue).
- Show version information – opens a version overview at the bottom edge. There you compare the workflow’s versions and see in which cases each version was started.
The side panel for element configuration
On the right-hand side of the editor is the side panel, used to configure individual elements. Its content switches automatically as soon as a different element is clicked. When configuring a ServiceTask, the following fields matter:
| Field | Meaning |
|---|---|
| Name | Should be set so the step is clearly labeled. |
| ID | Must be unique within the workflow. |
| Documentation | Optional description of the task. |
| Job type | The decisive value: it identifies which function DEPLAW executes for this task. |
| Retry | Number of retry attempts on error. Recommended 1–3, depending on the task (example: an LLM request can be rejected – a retry makes sense here). |
| Inputs | Resolved at the start of the task. Especially useful for passing specific variables into a subworkflow. |
| Outputs | Resolved at the end of the task. With FEEL, you can remap or adjust results once more. |
| Headers | Pass a specific input to the ServiceTask. The full FEEL function set is available here, plus the DEPLAW-specific FEEL functions. |
Empty ServiceTask
If you just need to calculate a variable using DEPLAW-specific functions or evaluate a condition – for example for checks or RVG/GKG calculations – without actually executing a real function, use the ServiceTask named “Empty ServiceTask.” Its sole purpose is resolving expressions and conditions.