/
Rollback Procedures: TAPSS-845/TAP-902

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

Rollback Procedures: TAPSS-845/TAP-902

Description

Execution Steps

Status

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.

 

 

Mock Deployment in TAP902SB

package.xml

<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <Package xmlns="http://soap.sforce.com/2006/04/metadata"> <types> <members>AQC_Donor_Contact_Type_Auto_Updater</members> <members>Automate_task_for_GA_for_Pledge</members> <members>Create_a_link_to_a_Third_Party_Pledge</members> <members>Description_HOLD_RECEIPT</members> <members>GIN_Stage_based_Update_Before_Save</members> <members>Gift_Pledge_On_Create_After_Save</members> <members>USYD_Gift_Pledge_Update</members> <members>USYD_Populate_Chart_of_Accounts_in_Transaction</members> <members>USYD_Transaction_Update</members> <members>USYD_Update_Pledge_Status</members> <members>USyd_GRC_Rollup</members> <members>Usyd_Campaign_member_status_update_when_new_transaction_created</members> <members>Usyd_Campaign_member_status_update_when_transaction_campaign_appeal_changed</members> <members>Usyd_Gift_Driver_Derivation</members> <members>Usyd_Transaction_surface_up_Pledge_WO_Notation_to_Gift</members> <members>Usyd_Update_Gift_Implementation_Status</members> <members>pledge_is_due_to_paid_out</members> <name>Flow</name> </types> <version>55.0</version> </Package>

 

 

TAP902SB

PROD

 

TAP902SB

PROD

AQC_Donor_Contact_Type_Auto_Updater

2

 

Automate_task_for_GA_for_Pledge

2

 

Create_a_link_to_a_Third_Party_Pledge

inactive

 

Description_HOLD_RECEIPT

4

 

GIN_Stage_based_Update_Before_Save

24

 

Gift_Pledge_On_Create_After_Save

2

 

USYD_Gift_Pledge_Update

3

 

USYD_Populate_Chart_of_Accounts_in_Transaction

2

 

USYD_Transaction_Update

4

 

USYD_Update_Pledge_Status

3

 

USyd_GRC_Rollup

1

 

Usyd_Campaign_member_status_update_when_new_transaction_created

6

 

Usyd_Campaign_member_status_update_when_transaction_campaign_appeal_changed

1

 

Usyd_Gift_Driver_Derivation

4

 

Usyd_Transaction_surface_up_Pledge_WO_Notation_to_Gift

3

 

Usyd_Update_Gift_Implementation_Status

1

 

pledge_is_due_to_paid_out

7

 

Related content

TAPSS-845/TAP-902: MS Team - To check the logic and any bad code practice for the list of flows mentioned and merge if required
TAPSS-845/TAP-902: MS Team - To check the logic and any bad code practice for the list of flows mentioned and merge if required
Read with this
May R2 Fortnightly TAP Release
May R2 Fortnightly TAP Release
More like this
TAP-1303: Update Batch Logic
TAP-1303: Update Batch Logic
More like this