Admin Plugins
Plugin Compatibility
Please note that the code of Admin plugins might need to be migrated when updating Camunda BPM to a higher version (e.g. CSS styles).
Admin uses the concept of plugins to add own functionality without having to extend or hack the Admin web application.
For further details about the concepts behind plugins, please read the Cockpit plugins section.
Difference between Cockpit and Admin plugins:
- To publish the plugin with Admin, its class name must be put into a file called
org.camunda.bpm.admin.plugin.spi.AdminPluginthat resides in the directoryMETA-INF/services. - The plugin mechanism of Admin does not allow to provide additional SQL queries by using MyBatis mappings.
Plugin Points
Here you can see the various points at which you are able to add your own plugins.
Dashboard
Name: admin.dashboard.section
With Camunda BPM 7.5, the Admin webapp gets a dashboard based on plugins similar to the Cockpit dashboard ones.
You can find examples of Admin dashboard plugins here.