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

Best Practices for migrating new developments between POD's

Summary:

Hi

We are trying to setup a migration release path for our developments and we want to do it as more automated as possible.

We are currently working with 3 environments.

1- In DEV1, we do our developments and tests - this environments never gets refreshed.

2- In UAT(test) we just move our final approved developments - every 3 months a P2T refresh takes place.

3-After testing in UAT, we then move succcesfull developments to PROD.

However, we are doing all of this manually each time we implement a new development (e.g. change of setup/ adding flexfields/ others) except of course for VBS changes which we can deploy from one place to different environments.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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