app/cockpit/scripts/config.js. The following configuration options are
available:
Logo and Header Color
You can change the visual aspects of Cockpit. The user stylesheet file is located inapp/cockpit/styles/user-styles.css. This file contains CSS which is loaded into Cockpit
and can override the standard styles.
app/cockpit/scripts/config.js configuration file as follow:
Localization
Cockpit can be localized. ASEE Flow maintains English and German translation files. You can find and download community maintained translation files at the ASEE Flow webapp translations repository. The localization of Cockpit is contained in theapp/cockpit/locales/ directory. This
directory contains a separate localization file for every available language. The file name
consists of the language code and the suffix .json (e.g., en.json).
Cockpit uses a locale file corresponding to the language settings of the browser. You can
set the availableLocales property in the configuration file to provide a list of available
locales. Every locale which is contained in this list must have a locale file in the locales
directory with the corresponding language code.
If the browser uses a language which is not available, Cockpit uses the locale which is
defined via the fallbackLocale property in the configuration file:
Custom Scripts
Cockpit allows you to include arbitrary JavaScript files. This allows you to extend Cockpit with custom code. The script file might contain a custom frontend module as described in Cockpit Plugins - Structure of a Frontend Module. Add your files to thecustomScripts property of the app/cockpit/scripts/config.js file:
custom-module/module.js file. The path is relative to the app/cockpit folder in the ASEE Flow webapp .war file.
You can find a complete example about how to use customScripts to develop a Cockpit Plugin in the ASEE Flow examples repository.
Legacy Custom Scripts
Custom Scripts created for ASEE Flow 7.13 or earlier can be included using therequireJsConfig property to the app/cockpit/scripts/config.js. You can include these custom scripts using the custom requireJS configuration.
BPMN Diagram Viewer (bpmn.js)
The diagram viewer (bpmn.js) can be either customized by moddle extensions or additional modules. To extend the BPMN diagram viewer of Cockpit, abpmnJs property must be added to the app/cockpit/scripts/config.js file.
Additional Modules
To add modules, theadditionalModules property needs to be specified, where each module is registered with its path. The path is relative to the app/cockpit folder in the .war file of the ASEE Flow Webapp.
Moddle Extensions
The BPMN moddle can be extended by adding amoddleExtensions property. Each moddle extension has a unique name (key)
and a path (value) to the JSON file of the moddle extension. The path is relative to the app/cockpit folder in the
.war file of the ASEE Flow Webapp. The suffix .json of the file is added automatically and must not be specified.
skipCustomListeners and skipIoMappings Flags
You can configure the skipCustomListeners and the skipIoMappings flag globally for cockpit by adding askipCustomListeners or skipIoMappings property in app/cockpit/scripts/config.js:
true. However, you can set the default value of the flag (true | false)
in the default property in the configuration.
Moreover, the checkbox to enable/disable the option is by default not hidden in Cockpit. You can set this behaviour by configuring the property
hidden (true | false) in the configuration. If the hidden value is configured to be false, then the checkbox
will be hidden everywhere in Cockpit.
The cascade flag
You can also configure the default value for the cascade flag by adding a cascade property in app/cockpit/scripts/config.js:
true, the flag’s checkbox in cockpit will be selected by default. When the property is not present, the default value is ƒalse. This flag is used when deleting process definitions and deployments.
Runtime Activity Instance Metrics (Process Definition)
display flag is true. If the statistics shouldn’t be displayed initially process definition runtime view is opened, the display option needs to be set to false.
In any case does the toggle button allow to display/remove the statistics on demand.
Historic Activity Instance Metrics
adjustablePeriod flag value is true. Setting it to false disables the ability in the process definition history view to manually select the time period for which the activity instances are displayed.
the unit property of period allows to specify the default timer period for which the activity instance badges are supposed to be shown.
Here it is possible to select form the range of values: today, week,month,complete;
Default Filter for the Historic Process Instances Search
- The property
lastDaysspecifies the numeric amount of days in the past based on the current time - The property
eventcan be either set to ‘started’ or ‘ended’
Change CSRF Cookie Name
The default name of the CSRF Cookie isXSRF-TOKEN. When using other applications within the
same-origin, the CSRF mechanisms could interfere with each other. To avoid the name conflict, you
can change the name of the CSRF cookie in the config.js file as follows:
Disable Welcome Message for new Users
First-time visitors are shown a message directing them to the camunda welcome page. If you do not want this message to be shown, you can disable it by adjusting theconfig.js as follows:
User Operation Log Annotation Length
The default maximum length of a User Operation Log annotation is 4000 characters. Some databases have smaller limits. You can change the maximum allowed input length in theconfig.js file as follows:
Preview Deployed Embedded Forms
You can view a preview of embedded forms and other HTML files in the Cockpit deployment view. If the HTML has embedded<script> tags, they will be executed, which may have unintended side-effects. You can disable this feature if you don’t trust your deployed HTML files in the config.js file as follows: