Workflow Component

Flows as state machines

In order to implement NS applications, traditional business processes have to be translated into state machines. This means that each flow is conceived as a sequence of tasks (i.e., a flow) operating on a single data element. A task embedded in a flow is executed whenever an instance of the data element (on which the flow is operating) is in a particular state (i.e., the “begin state”). During the time period in which the task is being executed, that state is altered into another state (i.e., the “interim state”). When the task has been completed, the state is altered again into an “end state” (in case the task was successfully executed) or a “failed state” (in all other cases). As a consequence, adding processing functionality to an NS application having data elements, should start with the creation of flow elements.

Workflow example


Run time

How it works


Release Expander version Change
201712 3.2.0 implemented parallel processing, sequencing and multiple nodes