...

• 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 repeat period:
  • The order instances are hidden from the JOC Cockpit GUI and appear as a single cyclic order with the Image Added icon appended to the Order ID.
  • Any operation to cancel, to suspend, to resume or to modify a cyclic order is applied to all order instances included.
    
    

Add Restriction

Schedules allow to add Restrictions that further limit the days for which orders are created:

...

• A draft status is visible from  icon and from the  orange bullet.
  • The draft status is in place when a Schedule is added or modified and is not yet released.
    • A draft Schedule can further be invalid which is indicated by the  icon. This happens due to missing input or invalid data added to the Schedule by the user.
    • Invalid Schedules are automatically stored in the same ways as valid Schedules. However, they cannot be released before they are valid.
    • Validation is performed with a JSON Schema, see JS7 - Inventory Storage Format.
  • Draft Schedules are ignored by the Daily Plan when creating orders for workflow execution.
• A released status is visible from the  icon and from the  blue bullet.
  
  • Valid Schedules only can be released.
  • Released Schedules are applied by the Daily Plan to create orders for workflow execution.
  • In addition they are considered when manually creating the Daily Plan from the respective view.

Use with the Daily Plan

A Schedule can apply the following settings to specify use with the Daily Plan:

• Plan Order automatically: this setting activates the Schedule for use with the JS7 - Daily Plan Service. As a result orders are automatically added with a PLANNED state.
• Submit Order to Controller when planned: this setting offers to automatically submit planned orders to Controllers
  • when the daily plan is created from the JS7 - Daily Plan view and
  • when used by the Daily Plan Service.
  • As a result such orders are assigned the submitted state in the Daily Plan view and in the JS7 - Daily Plan History.

Use with the Daily Plan View

• The view allows to manually create the daily plan for a given date. 
• The functionality includes to select specific Schedules, Schedules by folder or all Schedules to generate orders.
• Released Schedules only are applied to the Daily Plan.

Use with the Daily Plan Service

• The Daily Plan Service makes use of any released Schedules that hold the settings
  • to plan orders automatically or
  • to submit orders to a Controller when planned.
• The Daily Plan Service plans and submits orders for the number of days ahead that is specified with the Daily Plan Service configuration.

Cyclic Orders vs. Cyclic Workflows

...

• Execution
  • A Cycle Instruction spawning a complete workflow is an equivalent to 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 counts 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 use 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 - Notification 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 to resume 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.

Use with the Daily Plan

When configuring a Schedule then two settings can be checked that determine use with the Daily Plan:

• Plan Order automatically: this setting activates the Schedule for use with the JS7 - Daily Plan Service. As a result Orders are automatically added with a PLANNED state.
• Submit Order to Controller when planned: this setting offers to automatically submit PLANNED Orders to a Controller either when used by the Daily Plan view or by the Daily Plan Service. As a result such orders are assigned a PENDING state.

Use with the Daily Plan View

• The view allows manual creation of a daily plan for a given date. 
• This functionality includes the application of individual Schedules or all Schedules to generate Orders.
• Only valid Schedules that have been released can be used by the Daily Plan.

Use with the Daily Plan Service

• The Daily Plan Service makes use of any released Schedules that hold the configuration items:
  • to plan Orders automatically or
  • to submit Orders to a Controller when planned.
• The Daily Plan Service will plan and submit Orders for the number of days ahead that is specified with the service configuration
  • .