“Unified Sandbox” , available from Release 13 19C (optional feature), is now a delivered feature from Release 19D.
With Unified sandboxes, we can do parallel development because when the sandbox becomes out of sync with the mainline, it can be refreshed to bring the latest changes from the mainline metadata to respective sandboxes.
Using this feature, we can also create sandboxes for testing purposes only. While creating sandboxes, if the Publishable field is set to “No”, then such sandboxes can’t be published in any situation.
Once we get satisfied with the changes made in the test-only sandbox, these changes need to be replicated in a publishable sandbox.
Below is a working example of using a unified sandbox:
In this example we will create two sandboxes and would try to make changes to the Delivered Label “Person Type”.
In SB_Sandbox1A, the delivered value of the label is changed to “Employee Type”.
In SB_Sandbox1B, the same label name is changed to “Worker Type”.
Once we publish the sandbox “SB_Sandbox1A” we can see it in the published sandbox section.
Now for publishing the second sandbox i.e. “SB_Sandbox1B” we would need to refresh the sandbox to make it synchronized with the mainline environment.
Previously in classic sandbox this feature is not available and the object gets automatically locked when you create it or modify it in a sandbox. So in such cases, an object can only be edited in any one sandbox at a time.
In this sandbox we have changed the value from “Person Type” to “Worker Type” but as we have already published the first sandbox where the name is changed to “Employee Type”. So in mainline metadata there is no value as “Person Type” hence an unresolvable conflict occurs and we would not able to publish the sandbox.
For publishing the changes, we would need to reenter the sandbox and make the changes again.
To know more about Sandboxes and how they can help your organization, feel free to contact SOAIS .