...

• Suspend/softly: The operation allows an order to complete the current instruction, for example, executing a job, and after completion of the instruction the order will be put to the SUSPENDED state. The JS7 - Retry Instruction and JS7 - Cycle Instruction when resumed will use the retry/cycle counter in which they were with which orders have been suspended.
• Suspend/terminate task: The operation will forcibly terminate a current job instruction , for example, a running task, and will put the order to the SUSPENDED state.
• Suspend/reset: The operation will suspend the order and will reset the current instruction. The JS7 - Retry Instruction and JS7 - Cycle Instruction when resumed will use the initial retry/cycle counter. Without reset option an order can be resumed from the retry/cycle counter with which it has been suspended.
• Suspend/reset/terminate task: The operation combines resetting an order and forcibly terminating a running task.
  
  

...

• Deep Suspend/softly: The operation allows child orders to complete current instructions, for example, executing jobs, and after . After completion of the instruction child orders will be put to the SUSPENDED state. The JS7 - Retry Instruction and JS7 - Cycle Instruction when resumed will use the retry/cycle counter in with which they were have been suspended.
• Deep Suspend/terminate tasks: The operation will forcibly terminate current job instructions for running tasks of any child orders and will put child orders to the SUSPENDED state.
• Deep Suspend/reset: The operation will suspend child orders and will reset current instructions. The JS7 - Retry Instruction and JS7 - Cycle Instruction when resumed will use the initial retry/cycle counter. Without reset option child orders can be resumed from the retry/cycle counter with which they have been suspended.
• Deep Suspend/reset/terminate tasks: The operation combines resetting child orders and forcibly terminating running tasks.
  
  

Explanation:

• Deep Suspending child orders is performed as an asynchronous operation which includes the JOC Cockpit, Controller and Agent.
  • In a first step child orders are displayed with a green/red bullet icon indicating that child orders still are running and that the suspend operation is in progress.
  • In a second step child orders will be displayed with an orange bullet icon indicating that child orders have been suspended.

...

Dragging & dropping an order with the mouse to a different position in the workflow looks like this:

...

• The order remains assigned its original Daily Plan date though it is executed at an earlier date/time. This means that the order will not consider Notices from JS7 - Notice Boards of an earlier Daily Plan date but Notices of its original Daily Plan date if the “let run” operation causes the order to start before begin of the assigned Daily Plan.
• Users who wish to modify an order's assignment to the Daily Plan and to Notices matching the order's effective start date can use the operation "Modify start time" with option "Now" from the Daily Plan view.
• The "let run" operation is available for non-cyclic orders in the submitted state. For bulk operations users have to apply the One-time orderOrders filter.

...

The operation is available with the Workflows view and can be applied in a situation when users find more than one version of the same workflow:

• When modifying and deploying workflows then a new version of the workflow is created.
• Orders that did not yet start and that hold the PENDING or SCHEDULED state can make use of the new workflow version.
• Orders that have started and that hold any other state will remain with the previous workflow version. The reason being that changes to the workflow can disrupt orders that have been added to a previous version of the workflow. For example, if certain jobs or instructions have been added before the order's current position in the workflow, then this will break execution of an exiting existing order.

The operation to transfer orders is available for previous workflow versions and includes to transfer all orders to the latest version of the workflow.

...

• If orders are in the PENDING, SCHEDULED, FAILED, SUSPENDED, PROMPTING state then this will worktransfer is possible without limits.
• If orders are in the IN PROGRESS, RUNNING or BLOCKED state then this cannot worktransfer is not possible.  , 
• If orders are in the WAITING state then it depends on what orders are waiting for:
  • Orders waiting for Notices from JS7 - Notice Boards can be transferred.
Orders waiting for 
• • If the definition of Notice Boards changes between workflow versions then users can apply the "suspend/reset" operation, can transfer orders and can resume orders from the latest workflow version.
  • Orders waiting for JS7 - Admission Times for Jobs
or for a 
• • can be suspended, transferred and resumed from the latest workflow version.
  • Orders waiting for a JS7 - Cycle Instruction
cannot be transferred.
• • require to apply the "suspend/reset" operation to transfer orders and to resume orders from the latest workflow version.

  • Generally, users

Users

• • can suspend WAITING orders. When orders are in the SUSPENDED state then they can be transferred to the latest workflow version and can be resumed.

    • Use of the "suspend/reset" operation will suspend orders and will reset the current instruction. The JS7 - Retry Instruction and JS7 - Cycle Instruction when resumed will use the initial retry/cycle counter. 
    • Use of the "suspend/softly" operation allows to resume orders from the retry/cycle counter with which they have been suspended.

Bulk Operations

The Workflows view displays a maximum of three orders for each workflow. The overall number of orders available for the workflow is displayed by the grey order indicator:

...