Establish Extension-Level Settings
You configure settings for an extension in the Settings editor. To access the Settings editor, click the Menu in the upper-right corner of the Designer, then click Settings:
Description of the illustration extensionsettingoption.png
Here are the extension-level settings and how to use them:
| Version | Your extension's version number. Although VB Studio assigns a version number when you create an extension, you can change the value at any time. |
| Workspace Name | Name of the current workspace (which you can also see in the header). |
| Project Name | Name of the current project. This is handy, as otherwise you'd have to exit the Designer completely if you wanted to know which project you're in. |
| Repository Name | Name of the current Git repository (which you can also see in the header, along with the current branch). |
| Extension ID | Internal name for the extension. Extensions created by Oracle are prefixed by oracle_, as in oracle_name.
|
| Extension Name | Name of the extension as it will appear in the Dependencies list. (Recall that Dependencies lists extension names, not App UI or any other resource names.)
If you change the extension name, the extension ID changes accordingly. |
| Extension Description | Optional description of the extension. Before you publish your extension, it's a good idea to make sure this description is as helpful as possible, so that people who are trying to add your extension as a dependency later can understand what's in it. |
Note:
If you used the Edit Page in Visual Builder Studio option to jump over to VB Studio from an Oracle Cloud Application, the names and IDs generated by default use the pillar of the page you're trying to extend (instead of its extension ID). For example, the extension name takes the formatPILLAR Extension, like HCM Extension. If that name already exists, a number is added to the name and incremented as needed, for example, HCM Extension 1, HCM Extension 2, and so on.