...

• Controller: all objects in this area are deployed to a Controller, see JS7 - Deployment of Scheduling Objects.
  • Objects can exist:
    • as draft objects. Objects with this status are edited by the user and can be valid or invalid. Draft objects are intended for later deployment.
    • as deployed objects that are active with a Controller.
  • For Workflows and Notice Boards, versioning applies:
    • The Controller holds an active version of the object as long as a relevant Order or Notice ID is assigned.
    • Any number of active versions can co-exist. The Controller will drop earlier active versions if they are no longer assigned Orders or Notice IDs.
• Automation: objects in this area are not deployed to a Controller, instead they are released within JOC Cockpit. Such objects are used to automate Workflows, for example by scheduling Orders. 
  • Objects can exist
    • as draft objects. Objects with this status are edited by the user and can be valid or invalid. Draft objects are intended for later releasing.
    • as released objects that are e.g. actively used by the JS7 - Daily Plan to schedule Orders for workflow execution.
  • There is no versioning for such objects as they do not represent Controller objects but are used to automate processing of Workflows with a Controller.
• Note that Agents are not inventory items but are added when registering Controllers and Agents during JS7 - Initial Operation.

...

• More than one Controller can be connected to a JOC Cockpit instance, see JS7 - System Architecture.
  • Users choose the Controllers which objects are deployed to. For a Controller cluster the deployment process includes synchronization of objects with the journals of both Controller instances.
  • Objects can be deployed to a number of Controllers at the same time. For example, if the same workflow is deployed to more than one Controller, then any Orders scheduled for this workflow will be submitted to all Controllers that hold a copy of the deployed workflow.
• JOC Cockpit keeps track of the history of deployments, see JS7 - Deployment History.
  • Users can repeat deployments and can redeploy (recover to a previous state of deployed objects).
  • Users can select specific previously deployed versions of objects for (re)deployment.
• For details see JS7 - Deployment of Scheduling Objects

Inventory Operations

Folder Operations

...

The operations in this section are related to JS7 - Deployment of Scheduling Objects.

The operations work recursively for all sub-folders.

...

• A Schedule that has never been released will not be considered.
• A drafts is draft is created for a Schedule which has previously been released and which has been changed later on. Such drafts are not used by the Daily Plan unless they have been released. The Daily Plan will use the previously released version of such Schedules for the lifetime of the drafts.

...