Attention: Confluence is not suitable for the storage of highly confidential data. Please ensure that any data classified as Highly Protected is stored using a more secure platform.
If you have any questions, please refer to the University's data classification guide or contact ict.askcyber@sydney.edu.au
Skip to end of banner
Go to start of banner

Rollback Procedures: TAPSS-845/TAP-902

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Current »

Description

Execution Steps

Status

  1. Active Flow and Process versions in target org

From the target org, take note of the active versions of Flows and Processes that will be deactivated by TAP-902

  1. Create a rollback branch (e.g., release/TAP-902-rollback)

Create a new branch based from the release branch (release/TAP-902). In this branch:

1. new Flows introduced in TAP-902 will be deactivated, and
* Flow
<status>Obsolete</status>
* Flow Definition
<activeVersionNumber>0</activeVersionNumber>

2. old Flows will be reactivated
* Flow
<status>Active</status>
* Flow Definition
<activeVersionNumber>x</activeVersionNumber>

x - active version of the Flow in target org

  1. Merge release/TAP-902 to target branch

  1. Rolling back TAP-902 changes

Merge rollback branch (e.g., release/TAP-902-rollback) to target branch. This will deactivate the new Flows introduced by TAP-902 and reactivate the old Flows.

  1. Reversing changes from the rollback branch

Revert the merge commit done in Step 4. This will activate the new Flows introduced by TAP-902 and deactivate the old Flows.

  • No labels