Page History
...
Status Operations are available individually per workflow and are available as bulk operations when users select a number of workflows in the Workflows view.
Suspending Workflows
The suspend operation for a workflow means that:
- orders running in the workflow will be frozen after they complete their current processing step.
- This implies that orders are not cancelled and running tasks for jobs are not killed.
- orders scheduled for execution of the workflow that reach their start time while the workflow is suspended will wait until the workflow is resumed.
- orders that are added to the workflow for execution at a point in time while the workflow is suspended will wait until the workflow is resumed.
- This applies to orders available from the JS7 - Daily Plan.
- This applies to orders added from the Workflows view.
- This applies to file orders added from JS7 - File Watching.
...
As a result of this operation the workflow will switch to the suspended status:
...
The operation of suspending a workflow can include a number of Agents:
...
For details see JS7 - Workflows - Status Operations on Workflows.
...
Resuming Workflows
The Resume operation is available for a suspended workflow from its action menu.
...
Status Operations on Jobs
For jobs in a workflow the following status operations are available:
- Skip job: The job will not be executed, instead an order continues execution with the next instruction following the skipped job.
- Stop job: The order will be put to the suspended state if it meets a stopped job. 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 job a resumed order again will be suspended.
- Orders are not automatically resumed when a job is unstopped. Users find the category of suspended orders in the Dashboard view which offers to display the list of related orders and workflows. Bulk operations allow to resume a larger number of orders at the same time.
Status operations on jobs can affect a number of Agents that are assigned the related jobs. If one or more Agents assigned to jobs in a workflow are not accessible to the Controller then the status operation is considered being outstanding.
- The Controller will forward the status operation to the respective Agents when they become accessible.
- The workflow remains in an outstanding status indicating that not all Agents confirmed the status operation.
| Display feature availability | ||
|---|---|---|
|
Skipping Jobs
...
...
...
, for example to skip and to stop jobs.
For details see JS7 - Workflows - Status Operations on Jobs.
Stopping Jobs
...
...
...
Precedence of Status Operations on Workflows and Jobs
...
When adding orders from JS7 - Schedules and from the Workflows view and when modifying orders in the JS7 - Daily Plan then they can be assigned
- a start position in the workflow:
- users can select a later instruction, for example a job in a workflow, from which the order will start,
- any top-level instructions can be selected.
- any number of end positions in the workflow:
- more than one position can be selected,
- any top-level instructions can be selected.
Note: The start position and end positions specify the instructions in a workflow before which an order will start or complete.
| Display feature availability | ||
|---|---|---|
|
Adding Order Positions from the Instruction List
The popup window for adding orders allows to select the start position and end positions.
...
Adding Order Positions from the Graphical View
The popup window for adding orders offers the
icon to display the graphical workflow view for selecting a start position and end positions:
...
For details see JS7 - Workflows - Start Positions and End Positions of Orders.
Further Resources
| Display children header |
|---|
...
Overview
Content Tools