Recommendation for Releasing Changes Using VBS into Different Environments — Cloud Customer Connect
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

Recommendation for Releasing Changes Using VBS into Different Environments

in Visual Builder Studio for HCM 8 comments

Summary:

  • Environment Setup to Control Releases to Production
    • What is the best way to configure environments to release changes for testing (e.g., DEV for UAT) without impacting Production?
      • Example: My organization customizes a page or process, then moves these to a DEV environment for UAT. How can I ensure these changes don’t deploy to Production?
  • Preventing Unintended Releases to Production
    • If team members push changes to the main branch, how can I ensure those changes are not deployed to Production before they’re ready?
    • What is the recommended process to keep incomplete changes out of Production?
  • Local Branch Renaming Behavior
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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