Adding a Configuration UI for your Plugin
Purpose of the Configuration UI
A plugin can present configurable settings to Atlassian instance administrators. This is useful where your plugin requires configuration or user-specific settings to work.
Here are some examples of plugins which provide a configuration UI:
- The Google Maps plugin for Confluence requires a Google API Key from Google, which needs to be configured on each server before it will work properly.
- The WebDAV plugin for Confluence provides a configuration screen that is available both from the UPM and from a web item in the Administration menu.
In Configuring the Plugin Descriptor, we tell you how to create the XML descriptor file for your plugin. In Plugin Modules, we tell you how to define the modules within your plugin. Below is information on defining the links to the configuration UI for your plugin.
Adding a Configuration Link for the Entire Plugin
To add a configuration link for your plugin as a whole, place a single
param element with the name
configure.url within the
plugin-info element at the top of the plugin descriptor:
param element causes a button with the Configure label to appear in the details view for the plugin in the 'Manage Add-ons' page. The URL value identifies the page the contains the configuration form. For more information about implementing a configuration UI, see the Creating an Admin Configuration Form tutorial.
- Configuration links are relative to the application.
- The configuration URL is a link to a separate page, which you have defined using one of the following:
- A new XWork action that you have defined via an XWork plugin module.
- Or a servlet defined via a Servlet plugin module.
- Not all applications support configuration links, so you may need to create a web item link in the administration menu to link to your configuration page.