Whenever a sandbox is refreshed, you will need to perform the following steps:
- Get the new org id of the refreshed sandbox. Go to Setup -> Company Information -> Organization Id field.
- If the org id is only 15 characters, convert it to 18 characters. You can do so using this tool.
- Open the Environment record.
- Add the new org id.
- Notify the owners of these org credentials so that they set OAuth authentication in each of them, since the previous OAuth token is no longer valid.
Branch Management - Steps for Refreshed Sandboxes
- Go to your Git repository service.
- Create a new branch out of the branch that is linked to the sandbox. This branch will be a backup to review any commit history in the future. It is recommended to add the current date in the name of the backup branch.
- Delete the branch linked to the sandbox.
- Create a new branch out of master and name it with the same name as the branch deleted in the previous step.
- Go to your deployment flow. Click on Manage Releases (Manage Branches if you are in v11 or under) and then click on Recalculate.
- If the other branches linked to the branch of the refreshed sandbox have new changes, the Copado Branch Management application will show you the differences and will perform a validation deployment so that you can sync the new changes into the refreshed sandbox
If one of the middle sandboxes (integration, testing, etc.) is refreshed and there are pending user stories in this sandbox:
- Open the latest Promotion record in the user story.
- Redeploy the promotion into the refreshed sandbox.
- Copado Branch Management application will detect the new changes in the integration branch. You will be able to sync the changes to the lower environments if the branches of the lower environments do not have these changes yet.