HRSD Re-implementation go live (UTAH) and Vancouver upgrade approach
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 09:32 AM
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) Parallelly, we also have sustaibility development going on, scheduled for prod migration around end Jan 2024, Now, Vancouver upgrade is also planned for Feb 2024 go-live and it's work is already started. What are the possible options and implications for deployment? Should we deploy all 3 as per plan? or wait for upgrade and do the other two?
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2023 12:21 PM
@John Zhang1 @Chuck Tomasi - Can you please help?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2023 09:19 AM
I like option 1