Introduction

JS7 - Workflows implement jobs and dependencies for workload automation. Orders are triggers that cause the execution of workflows.

The Configuration View provides a graphical design view from the JS7 - Workflow Editor.
The Workflows View provides a tactical view which can be used to monitor the processing of orders with workflows in near real-time and perform interventions if required.

JS7 allows any JS7 - Workflow Instructions to be skipped and stopped on-the-fly.

FEATURE AVAILABILITY STARTING FROM RELEASE 2.7.0

Status Operations on Instructions

The following status operations are available for instructions in a workflow:

Skip: The instruction will not be executed, instead an order continues execution with the next instruction after the skipped instruction.
Stop: The order will be put to the suspended state if it meets a stopped instruction. Users can resume suspended orders.
- An order can be resumed from the same position, from a previous or later position in the workflow, depending on the workflow design. For a stopped instruction, resuming the order will force execution of the instruction. When resuming orders, users are free to chose the same or a different instruction from which the order will be resumed.
- Orders are not automatically resumed when an instruction is unstopped. Users can find the category of suspended orders in the Dashboard view. This displays a list of related orders and workflows. Bulk operations can be carried out, allowing a larger number of orders to be resumed at the same time.
The Workflows view provides the Search option to look up workflows that include skipped or stopped instructions.

An instruction's action menu includes the Skip operation:

A skipped instruction is not considered. This includes any nested instruction in a block instruction.
The operation to skip an instruction applies to any available version of the workflow that holds the skipped instruction.

The status of skipped instructions is displayed like this:

The skipping of instructions can be reverted by using the Unskip operation, which is available from the instruction's action menu:

The Stop operation is available from the instruction's action menu:

A stopped instruction suspends any incoming order to create a breakpoint in the workflow.
- Users can resume a suspended order from the same position or other position in the workflow.
- Resuming from the same position forces the instruction to be processed.
The operation to stop an instruction applies to the version of the workflow for which the stop operation is performed.

The status of stopped instructions is displayed like this:

The stop operation can be reverted by using the Unstop operation, which is available from the instruction's action menu:

Instructions in a workflow can be stopped and skipped at the same time. In addition the workflow can be suspended.

The above explanations suggest the following precedence of operations in descending order:

An instruction being stopped is assigned the highest precedence.
- Should a workflow be suspended then this includes that orders can complete the current instruction in the workflow.
- If the current instruction in a workflow is stopped then the order will be suspended before the workflow is suspended.
If a workflow is suspended then orders will be frozen once they have completed processing of the current instruction.
If the order specifying end position has been added then the order will leave the workflow once the end position is reached.
A skipped instruction has the lowest precedence compared to stopped instructions and suspended workflows.