Overview of Using Visual Builder Studio

For certain applications, use Visual Builder Studio to make changes to various page components. Changes made using Visual Builder Studio are called application extensions. Here are the changes you can make using this tool.

• Display fields from your data source to the UI

• Add business logic to display certain layouts

• Edit variables, constants, and events as needed

• Change the default content

• Rearrange fields

• Hide fields

• Create your own App UIs and deploy them alongside other applications in your Oracle Fusion Cloud Applications instance. In other words, you can now build robust applications that are managed as part of the same Fusion Applications ecosystem as the application UIs produced by Oracle. For more information, see Extending Oracle Cloud Applications with Visual Builder Studio guide. You might want to start with The Basics, just to get oriented.

Your test environment is automatically populated with an instance of Visual Builder Studio. Depending on what tasks you want to do with Visual Builder Studio, here are a few recommendations:

• If you’re creating an application extension, you can deploy it to any of your environments (test or production), not just the test environment. For instructions, see Set Up VB Studio to Extend Oracle Cloud Applications.
• If you want to use this instance of Visual Builder Studio to create visual applications (new custom applications) rather than application extensions, you must deploy visual applications to a standalone instance of Visual Builder. This is an entirely separate product that may require a separate license. For more details, contact your sales account representative.

Note: After you install an instance of Visual Builder, you need to set up Visual Builder Studio using the instructions in Create and Set Up a Project for Development (Different Identity Domain). Only after setting it up, you can start developing visual applications.

How to Verify Whether a Page Can Be Extended Using Visual Builder Studio

If you see the Edit Page in Visual Builder Studio option in Settings and Actions menu of a page, that means you must use Visual Builder Studio to make changes to that page. If you don't see the option, that means the page can't be modified using Visual Builder Studio.

Note: Click your user image or name in the global header to open the Settings and Actions menu.

Here are a few things to know about using Visual Builder Studio:

• If you need to make changes to the data model, you must first use other configuration tools, such as Application Composer, and then use Visual Builder Studio to make the changes in the UI.

• You can make additional changes to the data model later using a sandbox and associate that sandbox with the workspace (your private work area) in Visual Builder Studio.

• When you're ready to merge your application extension changes with the mainline repository, you should publish the sandbox. Publishing the sandbox before merging your application extension changes can help avoid potential problems resulting from using two different data models. The application extension changes are then automatically deployed to a test environment.