Page History

...

Besides import of objects the suggested rollout procedure considers a number of use cases:

• DeployDeploying/release releasing scheduling objects.
• Transfer Transferring existing orders to the latest version version of a workflow.
• Remove Removing inventory objects that are not included with the import archive.

...

This step works from a call to the Import-JS7InventoryItem cmdlet.

Existing objects such was as workflows, schedules etc. that are available from the archive file will be overwritten.

Step 2: Deploy/Release Scheduling Objects

This step is carried carries out in the following sub-steps:

• Release Releasing baseline scheduling objects
  • Objects such as JS7 - Script Includes and JS7 - Job Templates are released to make them available for further deployment, see Publish-JS7ReleasableItem.
• Deploy Deploying scheduling objects
  • Deploy objects Objects that should be available with a Controller and Agents such as as JS7 - Workflows are deployed, see Publish-JS7DeployableItem.
• Release Releasing scheduling objects
  • Release objects Objects that are required for automation such as as JS7 - Calendars and Schedules are released.

Step 3: Transfer Orders to latest Workflow Version

If a new workflow version is deployed then JS7 keeps the previous version of a workflow if a new workflow version is deployedfor which orders exist. The reason being that orders assigned the previous workflow version that have been started should be able to continue in the previous workflow version. If no orders exist for a previous workflow version, then this version will disappear. For details see see JS7 - Workflows - Status Operations on Orders.

For users who wish to transfer existing orders to the latest workflow version the script Rollout Script implements the desired behavior.

• A number of order states such as INPROGRESS and WAITING for specific events do not suggest orders to be transferred. Such orders are suspended to allow transfer to the latest workflow version and are later on resumed.
• BLOCKED orders cannot be transferred as they indicate missing connections from a Controller to the related Agent.
• RUNNING orders are ignored as they are assumed to complete the workflow.

This step This steps makes use of the the Get-JS7Workflow, Get-JS7Order, Suspend-JS7Order, Resume-JS7Order and Set-JS7Order cmdlets.

...