Client plugins

User interface for uploading custom plugins on the client plugin management page

If the plugin manifest contains the attribute Build-Time or Build-Timestamp, the value of that attribute is shown next to the plugin version, provided it is a SNAPSHOT version. This is helpful when you develop plugins as it helps yuo to distinguish between different SNAPSHOT versions.

You can add custom functionality to Xima® Formcycle by uploading custom plugins written in Java on the system plugin management page.

Uploading a plugin bundle

Click the browse button and select the JAR file to upload the plugin. The field bundle name will show the file name of the uploaded file.

Finally, click save or the plugin will not be registered.

While saving, the system will scan the JAR file for implementations of one of the above-mentioned interfaces that will then be available.

Should the JAR file not contain at least of Xima® Formcycle's plugin interfaces, the plugin will be discarded and will not be available.

Deactivating a plugin

Use the button   to deactivate the selected plugin and the button   to activate it again. A deactivated plugin behaves as if it had been deleted. However, all configured settings of the plugin remain saved and the plugin may be activated again at any time.

Contained plugin

This table lists all the Xima® Formcycle plugin interface implementation contained in this plugin bundle, as well as their type.


All global properties of the plugin bundle can be seen and modified here. New entries can be added, existing entries modified or removed.