A couple of days ago I came across a new feature that has been available since Release 19C. I noticed it earlier but I am getting around to it only now. Well, the overall conclusion is very positive. It definitely simplifies all sandbox activities among different implementation streams that might work concurrently. The main advantages are the following:
- Ability to select a configuration tool to be used for the Sandbox activity
- Refresh and merge – update a sandbox with a latest mainline updates produced by publishing other sandboxes, possibility to resolve conflicts wherever it’s possible
- Merge option is not supported for Application Composer, instead, there is provided a locking feature for objects maintained by application composer in the Unified Sandbox preventing concurrent updates to the same object
- Now CSM provides the ability to set up a target instance for direct migration of customizations to PROD/QA instances.
- CSM supports incremental loads now.
Let’s enable a Unified Sandbox in my test instance.
- Delete or publish old classic sandboxes
- Opt-in a new feature in FSM
- Start a new session and go to Navigator>Configuration>Sandboxes
- Create a sandbox, pick a configuration tool (you can pick more than one) and enter a sandbox. Please note: you can select a customization layer only for the page composer tool. Make changes inside a sandbox, preview and publish
- Migrate. Please note that changes are migrated into a special sandbox in the target instance to be able to make a final test before publishing to the production instance.
Please note that the system allows having 20 open sandboxes by default. It’s controlled by ORACLE.ADF.SHARE.SANDBOX.MAXIMUMSANDBOXCOUNT profile option. You are free to increase this value but make sure this is the optimal maximum value recommended by Oracle. Increasing this value might affect system performance.
I hope this is helpful.