Page History
Table of Contents |
---|
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.
Orders can be cancelled and can be suspended to prevent execution of jobs and they can be resumed:
Status Operations on Orders
Status Operations are available individually per workflow and are available as bulk operations when users select a number of workflows in the Workflows view.
The following sample workflow is available that allow to
Download (upload .json):
Cancel Order
Orders in a PENDING, SCHEDULED, RUNNING, IN PROGRESS, SUSPENDED, PROMPTING, WAITING, BLOCKED and FAILED state offer a number of operations to fail order execution from the order's action menu, for details see JS7 - Order State Transitions:
- Cancel: The operation allows the order to complete the current instruction, for example executing a job, and after completion of the instruction the order is set to the FAILED state.
- Cancel/Kill Task: The operation kills processing of the current instruction, for example a running task, and makes the order enter the FAILED state.
Explanation:
- Cancel: The operation causes the order to complete the current instruction, for example executing a job, and then to be set in the FAILED state.
- Cancel/Kill Task: The operation kills a running task and makes the order enter the FAILED state.
Suspend Order
Running orders offer a number of operations from their action menu:
- Suspend
- Suspend/Kill Task
Resume Order
FAILED orders offer a number of operations from their action menu:
- Suspend
- Suspend/Kill Task