Skip to Content

Wiki source code of Mandant-Plugins

Show last authors
1 {{content/}}
2
3 {{figure image="mandant_plugin_en.png" width="500"}}
4 User interface for uploading custom plugins on the client plugin management page
5 {{/figure}}
6
7 {{info}}
8 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.
9 {{/info}}
10
11 You can add custom functionality to {{formcycle/}} by uploading custom plugins written in Java on the system plugin management page.
12
13 == Uploading a plugin bundle ==
14
15 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.
16
17 Finally, click //save// or the plugin will not be registered.
18
19 While saving, the system will scan the JAR file for implementations of one of the above-mentioned interfaces that will then be available.
20
21 {{info}}
22 Should the JAR file not contain at least of {{formcycle/}}'s plugin interfaces, the plugin will be discarded and will not be available.
23 {{/info}}
24
25 == Deactivating a plugin ==
26
27 Use the button {{icon name="ban"/}} to deactivate the selected plugin and the button {{icon name="power-off"/}} 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.
28
29 == Contained plugin ==
30
31 This table lists all the {{formcycle/}} plugin interface implementation contained in this plugin bundle, as well as their type.
32
33 == Properties ==
34
35 All global properties of the plugin bundle can be seen and modified here. New entries can be added, existing entries modified or removed.