You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started: AI Resources for Oracle Cloud HCM – Go Here

Progress with Redwood: Redwood Resources for Oracle Cloud HCM -  Go Here

looking for best practices to deploy VBS changes across different versions

edited Feb 6, 2025 11:45AM in Visual Builder Studio for HCM 1 comment

Summary:

Is it required to have one DEV pod to be on Prod cadence always so that no there will not be impact on VBS deployments during upgrade window?  


Content (please ensure you mask any confidential information):

We have multiple DEV pods , 1 TEST and 1 PROD pods. Upgrade follows 6 week schedule. TEST and PROD pods are on same patch cadence.
e.g. 25A will be applied to DEV pods on 2/7/25 and after 6 weeks, TEST and Production pods would be upgraded on 03/21/25.

Especially during upgrades, since DEV will be on 25A, Prod and TEST are on 24D, System does not allow VBS deployments from DEV to PROD / DEV to TEST for 6 weeks. 

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!