Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • The Repeat interval requires the Repeat Time to be specified, for example to execute every 10 minutes.
  • The Begin and End of the repeat period have to be specified, for example from 8am to 8pm.
  • The Schedule will create individual order instances for each start during the period:
    • The order instances are hidden from the JOC Cockpit GUI and appear as a single cyclic order with the  icon appended to the Order ID.
    • Any operation to cancel, suspend, resume or modify a cyclic order is applied to all order instances.


Users can specify the behavior if a scheduled date meets a non-working day.

Image Added


The following options are offered:

  • suppress execution (default): no order will be added to the non-working day.
  • ignore non-working day: add an order for the non-working day.
  • before non-working day: anticipate execution to the closest working day before the non-working day.
  • after non-working day: postpone execution to the next working day.

Add Restriction

Schedules allow the addition of Restrictions that further limit the days for which orders are created:

...

  • Execution
    • A Cycle Instruction spawning a complete workflow is equivalent to the use of cyclic orders from a Schedule.
    • In addition, a Cycle Instruction can be used to execute parts of a workflow in cycles.
  • Efficiency
    • Schedules create a number of order instances for each period in a cycle, Running a single workflow every 30s adds up to 2880 orders per day.
    • Cycle Instructions cause cyclic execution of a workflow from a single order.
    • Processing of cyclic workflows is by far more efficient than the processing of cyclic orders.
  • Error Handling
    • Failure
      • If a job in a workflow fails then this will occur for each order instance of a cyclic order individually.
      • If a job within a Cycle Instruction fails then, depending on the error handling in place, any cycles that would occur while an order is in a failed state are skipped..
    • Notification
      • For each failing order instance of a cyclic order a JS7 - NotificationNotifications is created.
      • For the single order of a cyclic workflow a single Notification is created.
    •  Intervention
      • Any operations on cyclic orders are applied to all order instances included, for example, resuming execution after failure. This results in parallel execution of orders previously scheduled for execution in intervals.
      • For cyclic workflows there is a single order that waits for user intervention.
  • Logging
    • For each order instance of a cyclic order: a separate entry is created in the JS7 - Order History and in the JS7 - Task History.
    • For a cyclic workflow: there is a single entry in the Order History that is appended the log output of each cycle. Individual entries per job execution are added to the Task History.

...