The green button in the top-left corner opens drop-down Menu for running tools, allowed for the current user.

Each running tool has a button on toolbar, the active tool marked with blue background. Placing mouse pointer over a toolbar button shows full menu path to the related tool, Processes / Process Queues on the screen.

No needed tools can be closed by click to grey crosses on right toolbar buttons, or by right-click popup menu on active tool button.

Right to the toolbar can be displayed one or multiple user-configured process counters, showing quantity interesting processes, 70 for the screen. After is placed number of notifications, blinking in case of changing it. In the drop-down menu, opened after mouse click on notification counter, presented separated parts of the number, occurred in different tools. Click to the menu item opens the mentioned tool with unread news or messages.

In the top right corner has shown the name of the current user. Click on it opens drop-down menu with options for see own profile, processes or terminate the session.

Shows the title from the active object or tool, click on that refreshes the active content area.

In center of the topline, right from the title, placed so-named State area, there can be the related documentation link with ? char.

Or string representing the current state of active content.

There is also may be placed some controls of the active tool.

The Buffer contains list of inactive objects, previously being opened and not explicitly closed by switching activity to another object or tool. The size of the buffer is limited, last placed object placed on the top, others are shifted down, closing the oldest if the limit size has been reached.

Objects in buffer are used for quickly re-open them or object selection in some operations, like link creation.

No more needed objects in buffer may be closed by click on grey crosses at right area.

A Tool acts like an application inside the application and allows perform different data manipulation. Each tool can be opened only once inside a browser window, re-opening just makes it active. Beside of menu, switching active tool may be performed by click on an inactive toolbar button, or using Back and Forward browser navigation commands. The last option is possible, because any tool has an unique location URL, e.g.: /user/search, /user/news, /user/process/queue

An Object represents a set of related data: process, customer, user profile or some another from a plugin. Unlike tools, many objects of the same type can be opened in same time, their ID ends the object’s browser URL after # char.

In active content area can be placed only one tool, or an object, like on the screen above. Inactivated objects placed it buffer.

Button colors have the following meanings.

When hovering mouse pointer on some interface elements, additional information is shown. As example on toolbar buttons displayed a full menu path, for object buffer shown just a short hint.

For input fields there might be the logic’s details.

In many cases these tips contain entity IDs.

In configuration values can be stored multiline values, the way is actively used in JEXL expressions.

The value will be: Value Line 1Value Line 3, line brakes are excluded. Instead of END any other string can be used.

In configuration lines, it is possible to substitute previously specified values using macros {@<key>}.

The existence of used variables is being validated during configurations' save.

After parsing, a configuration is used by the system as a set of key-value pairs in which the order is not defined. If it is necessary to specify the order, additional numeric indexes are added to the keys.

When there are many such entries, maintaining the index can become difficult, especially when the entry numbers need to be changed. In this case, the index can be extracted into a separate variable and incremented using the inc macro. Below is an identical configuration where the indexes are extracted into a variable:

Repeated parts of large configurations they can be extracted to includes. For that can be used any Server Configuration with separated ID. The main and active server configuration is normally broken down with many includes of different subsystems and plugins.

Except that, a separated server configuration can be user like a library in any other configuration, using instruction include.<ID>=1

Note, how in the include was defined initial value of counter variable cnt. Using a unique ID of the included configuration multiplied by 100 ensures the uniqueness of key values in any location.

Except of simple assignment, a key value can be appended to the existing:

In this case the value for key will be 1,2,3. Together with includes the approach is used for appending to existing key values. If the keys' value is missing, it will be created on a first concatenation.

The both of configurations are included to the main ones and extend the same keys' value.