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 5 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.

The JS7 offers to skip jobs and to stop jobs on-the-fly.

FEATURE AVAILABILITY STARTING FROM RELEASE 2.4.0

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.

FEATURE AVAILABILITY STARTING FROM RELEASE 2.4.0

Skipping Jobs

A job's action menu offers the Skip operation:


For skipped jobs the status is displayed like this:


The operation to skip a job can be reverted by using the Unskip operation that is available from the job's action menu:

Stopping Jobs

A job's action menu offers the Stop operation:


For stopped jobs the status is displayed like this:


The operation to stop a job can be reverted by using the Unstop operation that is available from the job's action menu:

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.

Further Resources



  • No labels