HRSD Re-implementation and Upgrade Approach

ASHU_1
Tera Contributor

‎11-06-2023 02:35 PM

Hello, 

 

We have our HRSD Re-implementation go live in Utah coming up in Jan 2024. We have already started build - Configuration and Custom changes (Delivered and Custom objects are in balance - 50/50) Now, Vancouver upgrade is also planned for Feb 2024. What are the possible options and implications?

 

1. Stick to the plan, backup the new update sets for all the build efforts, Clone Prod to Dev, Upgrade to Vancouver, Roll back update sets, Review changes and apply, and then test and finally move to next instance.

2. Complete the upgrade, backup the new update sets for all the build efforts in Utah, Clone Prod to Dev, Upgrade to Vancouver, Roll back update sets, Review changes and apply, and then test and finally move to next instance.

3. Or any other options and implications?

 

Thanks!

 

 

0 Helpfuls
  • 268 Views
1 REPLY 1

Sandeep Rajput
Tera Patron
Tera Patron

‎11-06-2023 07:01 PM

I will stick with approach 1 as after redeploying the update sets post upgrade and testing the changes thoroughly, using this approach you will get to know if any feature/customisation doesn't work post upgrade.

 

Hope this helps.

0 Helpfuls