Oracle Fusion Cloud Apps come with a built-in Visual Builder Studio instance that allows you to customize and extend Oracle Cloud Apps. By default the VB Studio instance is associated with the TEST instance of your cloud apps. This means that the creation of extension is going to be done on that TEST instance. You might however want to replicate the extensions you created on other DEV and PROD environment. To do this you are going to leverage the Environments and Build Jobs features of Visual Builder Studio.
Deploying Extensions
Below is a video showing the process of taking an extension created in one environment and publishing it on another environment step by step.
To summarize the steps in the video:
- Commit your changes to the Git repository in Oracle Visual Builder Studio (by pressing the publish button in the designer)
- Define a new Environment and map it to an instance of Oracle SaaS providing the URL to the FA instance and the user credentials for a user that is allowed to deploy extensions there.
- Duplicate the built-in deployment job created for your extension to create a new job. In the configuration for the new job, switch the environment used for the deploy step (and update the user credentials as needed).
- Optionally – include the new build job in relevant pipelines.
Once the job runs successfully you'll be able to see your extension deployed on the relevant instance. You can track the existing deployments through the deployment tab for your environment in Visual Builder Studio.
Deleting an Extension
If you need to remove an extension you deployed – copy the extension id and version from the deployment tab. Then create a new build job that uses the Delete step for Application Extension. Specify the environment, user credentials, the base app (hcm for example) and the extension id and version. Running the job will then remove the extension.