...

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

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

Workflows can be suspended to prevent the execution of jobs and they can be resumed:

...

• 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 which reach their start time while the workflow is suspended will transition to the in progress state and 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.

...

• The orange status button indicates suspension.
• Orders running in the workflow switch to the in Progress state to indicate that they are frozen.
  
  

The operation of suspending to suspend a workflow can include a number of Agents:

• If different Agents are used in a workflow and if one of them is not available then the workflow remains will remain in the suspending status until all Agents confirm suspension.
• If orders are added to a suspending workflow with an unavailable Agent then they will switch to the blocked state.
• Orders in the in Progress or blocked state will be continued when the workflow is resumed.
  
  

...

Orders waiting in the workflow in the in Progress or blocked states will continue when the workflow is resumed.

Stopping Instructions

The Stop operation is available from the action menu of any instruction in a workflow:

• 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 executed.
• The operation to stop an instruction applies to the version of the workflow for which the stop operation is performed.
  
  

Image Added

The status of stopped jobs is displayed like this:

Image Added

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

Image Added

Precedence of Status Operations on Workflows and Jobs

Jobs in a workflow can be stopped and skipped at the same time. Other instructions can only be skipped. In addition, the workflow can be subject to suspension.

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

• A An instruction such as a job being stopped is assigned the highest precedence.
  • Should If a workflow be is suspended then this includes means 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 having completed after processing of the current instruction has been completed.
• If the order has been added with an a specified end position being specified is added then the order will leave the workflow reaching the when it reaches that end position.
• A job being which is skipped experiences the lowest precedence compared to stopped jobs or other instructions and suspended workflows.

Further Resources

...