A workflow always runs in the context of a case file. Its lifecycle has four phases: start, execution, runtime data flow, and end.

1 Start manual or via a start rule 2 Execution Engine calls the ServiceTasks 3 Data flow Variables ↔ case file, live in both directions 4 End EndEvent reached or ended early

Start

A workflow is started within a case – either automatically via a start rule or manually by a user in the case’s Workflow tab. On start, DEPLAW passes all data of the case’s entities into the workflow as variables. By default, all variables are passed as strings (see Variable Concept).

Execution

The workflow engine works through the elements defined in the process model. As soon as it presents a ServiceTask, DEPLAW executes the associated function and returns the result to the engine, which then moves on to the next element.

Data flow during runtime

Data exchange is bidirectional – the case data and the workflow stay in sync in both directions:

Case file case placeholders Workflow running instance change → propagated new variable → saved
  • From the workflow into the case file: Every variable generated within a workflow lands in the case file’s placeholders immediately after the generating element executes.
  • From the case file into the workflow: If data in the case file is changed during runtime – for example a placeholder or a participant’s data – these changes are automatically propagated after saving into the running workflow.

End

A workflow ends as soon as its EndEvent is reached. Alternatively, it can be ended early – through a manual or an automated action.