View Your Deployments

After you've published your extension, you can check your project's Environments tab to see if it's been deployed to your development environment.

To view the deployed extensions:

1. Click Environments in the main menu to open your project's Environments page.
2. If necessary, select the Development environment for your extension.
3. Open the Deployments tab for your environment and click Application Extensions:
   
   Description of the illustration deploymentsv2.png
   

This screen shows the Deployments tab only for the current project, SampleProject (as opposed to all the projects in the Development environment). There are two published extensions in this project, HCM_ProofOfConcept and sampleProject Extension. Let's look at these extensions more closely:

Name	Description
Extension ID	The extension ID used in the New Application Extension dialog when the extension was created (either site_extensionName by default or user-specified), or assigned automatically if you used the Edit Page in Visual Builder Studio option to jump over to Visual Builder Studio from an Oracle Cloud Application. In this example, HCM_ProofOfConcept was explicitly specified by the user. Extension IDs that use the format site_pillar_extension (for example, site_hcm_extension) typically indicate that they were automatically assigned by Visual Builder Studio.
Dependencies	When you expand an extension you can see its dependencies, listed by their extension IDs. (The Unified Application, which is a dependency for all App UIs, is not listed.) In this example, HCM_ProofOfConcept does not have any dependencies, while sampleProject Extension has one, with the extension ID oracle_hcm_timeUI. The version number of the dependency appears after the extension ID.
App UIs	If you added a new App UI to your extension, you can open it using the Open icon. All App UIs open in their own browser tab, with a dedicated URL. By default, this URL is in the form https://{Universal Application Name}/redwood/yourAppuiName. However, if you specified an App UI ID when you created your App UI, that ID will be substituted for yourAppuiName instead. An Open icon is not provided for an App UI that you configured, nor are configured App UIs listed here explicitly. In other words, there is no way to tell whether oracle_hcm_timeUI has been configured by this extension, only that it has been added as a dependency.
Published By	The name of the deploy job for this extension (by default, gitRepoName-Deploy.job, along with the time and date that the job completed. In this example, HCM_ProofOfConcept's creator supplied a Git repo name (hcm-poc), so it was appended to the job name. The sampleproject Extension, however, was created by using the Edit Page in Visual Builder Studio link, so its deploy job has the default prefix, Application-Extension-Deploy.

If you think your extension should have been deployed but you can't find it in the list, check the build jobs for your project to see if the job has finished. Click Builds in the project's far left navigator to see the list.

Note:

The list will only include extensions deployed to the environment using the project's deploy job. Extensions deployed from a local system using curl will not be listed. Instead, you can use the curl request described above in Deploy an Extension From Your Local System to see the full list of deployed extensions.

There are two jobs that must complete before the extension is deployed, gitRepoName-Package and gitRepoName-Deploy. These jobs are usually kicked off automatically by the Publish action, but you may have had to run them manually for some reason. Contact your project administrator if you think there might be a problem with deploying the extension.