JS7 JobScheduler

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Introduction

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

  • The Configuration View offers a graphical design view from the JS7 - Workflow Editor.
  • The Workflows View offers a tactical view that 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 execution of jobs and they can be resumed:
FEATURE AVAILABILITY STARTING FROM RELEASE 2.4.0

Status Operations on Workflows

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.

The Suspend operation is available from a workflow's action menu:


As a result of this operation the workflow will switch to the suspended status:

  • 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 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 in the suspending status until all Agents confirm suspension.
  • If orders are added to a suspending workflow with an unavailable Agent then they switch to the blocked state.
  • Orders in the in Progress or blocked state will be continued when the workflow is resumed.

Resuming Workflows

The Resume operation is available for a suspended workflow from its action menu.

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

Precedence of Status Operations on Workflows and Jobs

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

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

  • A job 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 having completed processing of the current instruction.
  • If the order has been added with an end position being specified then the order will leave the workflow reaching the end position.
  • A job being skipped experiences the lowest precedence compared to stopped jobs and suspended workflows.


  • No labels