How Do I Use My Sandbox in Visual Builder Studio?
VB Studio can access sandboxes in Oracle Cloud Applications that have changes to the application’s data model that haven’t been published yet.
If the changes in a sandbox are relevant to your extension, you can associate the sandbox with your workspace so you can access it while you’re working. Here are some tips:
- You’ll want to do all your work in a branch that is associated with the sandbox with those changes, and continue to use the same branch with that sandbox until you are finished.
- If you need to edit the extension using a different sandbox as well—for example, a sandbox defining an alternative data model that is being considered—it’s better to associate it with a new branch than to use an existing branch. This will help isolate the changes you make for each sandbox.
- For each branch-sandbox pair, you can create a separate workspace instead of switching a workspace’s branch and sandbox. VB Studio helps keep your changes in sync by automatically recommending a sandbox for your workspace if you choose a branch that is already using it.
If you’re using a sandbox with your workspace, VB Studio will notify you if there are changes to the sandbox (for example, it was published or deleted) or to the Oracle Cloud Application environment that could affect your extension. The notification will contain a description of the change and a link you can use to help address it. For example, here’s a notification you might see when the sandbox associated with a workspace needs to be refreshed because of changes in the application’s environment:
Description of the illustration sandboxrefresh1.png
Clicking the Refresh link will start the process to bring your sandbox up-to-date. For more about working with sandboxes in Oracle Cloud Applications, see Overview of Sandboxes in Configuring and Extending Applications.
When you’re ready to publish your extension to your Oracle Cloud Applications environment, you should publish the associated sandbox at the same time or shortly before to minimize the risk that the data model and extension will be out of sync. In addition, once you’ve published your extension, your users might have to sign out, then sign back in to the Oracle Cloud Applications environment to see the latest changes.