...

• The functionality of the JobScheduler Job API has been migrated to the JS7 - REST Web Service API.
• However, a number of differences have to be considered:
  • The JS1 Job API allows to modify objects of the current job such as the current task or order.
  • The JS7 REST Web Service API allows modification of any objects, but requires to identify objects such as jobs.
  • A number of operations of the JS1 Job API are not available, for example to modify the job configuration on-the-fly, e.g. by adding/dropping a setback configuration.
• A REST Client has to be used by jobs that access the JS7 REST Web Service API.

Object Changes

Consider changes indicated with the JS7 - Terminology.

Jobs and Job Chains

Job Chains in JS1 correspond to JS7 - Workflows:

• The JS1 knows Jobs and Job Chains that implement a sequence of jobs.
  • A job is an object that can be modified individually and that can be re-used with a number of job chains.
  • A job is defined to be operated standalone or as a node in a job chain.
  • Any changes to jobs and job chains are immediately in effect.
• The JS7 is not limited to a sequence of JS7 - Jobs but introduces a number of JS7 - Workflow Patterns which is why the term workflow replaces job chain.
  • A job is available within a workflow only. A job is not an independent object and it cannot be re-used.
    • While users might consider this a limitation, in fact it guarantees a self-contained and consistent workflow configuration. Consider the fact that a JS1 job could be modified or removed at run-time leaving the job chain in a critical status. The JobScheduler Master had to check for updated versions of a job XML file and had to apply any modifications in good time. If modifications are not consistent, e.g. if the job parameterization changed, then this breaks a current order run as any changes to jobs are immediately applied.
    • Modifications of a JS7 job force a workflow to be deployed once again.
    • The JS7 - Inventory Bulk Operations for Jobs offer to modify a single job and to apply changes to a number of jobs across workflows.
  • There are no JS1 standalone jobs in JS7, instead such jobs are considered workflows with a single job.
  • Changes to workflows take effect for newly added JS7 - Orders only. The JS7 Controller keeps track of workflow versions as long as an order is assigned the workflow.
    • At the point of time of submission an order is associated with the current version of a workflow.
    • If the workflow changes later on then this has no impact on submitted orders, but affects new orders only that are submitted after this change.
    • This feature can be used to target changes of a workflow to a future date. Existing orders can be cancelled and re-submitted to be assigned the current version of a workflow from the Daily Plan view.

...