Oracle Cloud Infrastructure Documentation

Create a Simple Extension

The easiest way to set up VB Studio so that others can configure Oracle Cloud Applications pages is to create a simple extension yourself. This lets you ensure everything is working properly.

The best practice is to create one project for all the Oracle Cloud Applications your users will want to configure in an environment family. Within that project, you should have one Git repository for each pillar that your users will extend—that is, one for HCM, one for SCM, and so on—so that the code for all extensions within that pillar is stored in the same Git repository. For more recommendations, see Extension Best Practices in Extending Oracle Cloud Applications with Visual Builder Studio.

  1. Navigate to a page in your Oracle Cloud Application.
  2. Click your user name at the top-right corner to open the Settings and Actions menu, then select Edit Page in Visual Builder Studio:
    Description of fa-edit-page-link.png follows

  3. In the New App Extension Project dialog, enter a unique name for the project, as well as some team members or groups you think might use this project to extend this Oracle Cloud Application:
    Description of newappextproj.png follows

    Note

    After you've completed this procedure, make sure that the team members you've added have the proper roles, by following the steps in Set Up VB Studio Users.

    VB Studio shows you a status dialog so you can follow along as each asset is created:
    Description of projprogress.png follows

    If you're curious about these assets, you can find out more about them in What Project Artifacts Are Created?.

    By default, VB Studio creates a private project that’s discoverable, which means that users you haven’t added explicitly to the project will be allowed to choose the project when they click Edit Page in Visual Builder Studio from the associated Oracle Cloud Application. Remember, it’s best to keep all work for a given Oracle Cloud Application within the same project, so VB Studio will place a “Recommended” badge next to the project’s name to encourage users to select it.

    Note

    The default workspace name generated when you jump over to VB Studio typically uses the pillar of the page you're trying to extend, in the format Workspace PILLAR, for example, Workspace HCM. If that name already exists, a number is added to the name and incremented as needed, for example, Workspace HCM 1, Workspace HCM 2, and so on.
  4. VB Studio opens the page you were just viewing, in the Designer. When you hover over an extendable component on the canvas, it is outlined in blue, like this:
    Description of extendableareasingreen.png follows

  5. Make a small change to the page, just for testing purposes. You can drag a Heading component onto the page, for example, or add or remove a field on a dynamic form. VB Studio implicitly saves your changes as you work.
  6. In the Designer's header, click Publish:
    Description of designer-publish-changes-action.png follows

    By default, your extension's sources are merged to the default branch (main) of the workspace's Git repository, then built and deployed immediately to the Oracle Cloud Applications instance within your DEV environment.
    Note

    If you prefer, you can change the default and instead deploy your changes via a continuous integration and delivery (CI/CD) pipeline. CI/CD pipelines give you the option of deploying an extension to multiple environments as well as automating some lifecycle operations. For more information, see Enable or Disable the CI/CD Pipeline for Publishing in Extending Oracle Cloud Applications with Visual Builder Studio.
  7. Now click the link in the Publish dialog to see your published changes:
    Description of publish-pipelinedisabled.png follows

    Note

    Make sure you copy and paste the deployment URL to your clipboard before you click Close. You won't have access to the URL after the Publish dialog is closed.

    Also, users of your Oracle Cloud Application will have to sign out of the app, then sign back in again to be sure they're seeing the latest.

If this were a real extension, after testing your changes in your DEV environment, you might want to deploy it to other Oracle Cloud Applications instances. You can use the Manage Extension Lifecycle page to do this. See Manage Your Published Extensions in Extending Oracle Cloud Applications with Visual Builder Studio.

As this was just a simple test and not a real extension, you may want to remove it. To do so, see Delete an Extension.