Updating Subflows to a New Version

Updating built-in subflows to a new version

For built-in subflows:

• When a new minor version of a built-in subflow becomes available, any runbook that uses it will update automatically to include the new minor version.

• When a new major version of a built-in subflow becomes available, you will need to manually update any runbook that uses it to include the new major version. Riverbed IQ Ops will tag each affected runbook in the relevant page (Incident Runbooks, On-Demand Runbooks, and Lifecycle Runbooks) with a warning. You can update the subflow by editing the Subflow node and clicking the Update button in the Subflow node editor, or you can delete the Subflow node and replace it, which will use the latest version automatically.

Updating custom subflows to a new version

Duplicating a subflow will create a new subflow with version 1.0.0.

Renaming a subflow does not affect older versions of the same subflow, meaning that the same subflow can have different names in different versions.

Updating integrations to a new subflow version

When a subflow is used in an integration Shared Access Signature. A secure way to grant limited access to Azure storage resources without sharing storage account keys. A SAS token contains permissions and an expiration time., you will need to take action to update the subflow if its version changes:

• When a new minor version of a subflow is available and the integration is already installed, the integration will be marked with "Update available," and you will need to click the Update button to replace the subflow with the latest minor version. Any runbooks that use that subflow will update to use that latest minor version automatically.

• When a new major version of a subflow is available, the integration will be listed in the Integration Library's Available tab, even if an earlier major integration is installed already. You will need to re-enable the integration to use the updated major version of the subflow.