JavaScript is disabled on your browser.

Application Properties

The properties dialog of an application can be reached via the application node in the application structure. Open the properties dialog by double clicking on the application node, or via the Properties context menu item.

General properties

On this tab you will enter the name of the application under Title. An application description can also be entered here. The title will be used in the browser for the application link in the portal menu. The description will be shown if a menu item is found on the Intrexx default start page.

Application menu

On the Application Menu tab, you will select the pages that you want to be available in the menu of the application. You may select all main pages, portal pages, and edit pages that are located in data groups directly under the application node. In the Available Pages column, all available pages will be listed.

With the setting Hide Application Menü the application menu will not be displayed in the end device.

With the horizontal arrow buttons, pages can be moved from one column to the other. With the vertical arrow buttons, the order of the pages can be changed.

In this, the higher the position of a page in the Selected Pages column, the further left it will be shown in the application menu. If an edit page is directly called up from the application menu, it will be loaded with empty edit fields for entry of a new data record.


On this tab, view pages can be defined as portlets for display on a portal page.

New pages can be added by clicking Add Portlet or by double clicking in the empty area on the tab. Existing portlets can be removed from the list by clicking Delete Portlet. With Edit Portlet, as with adding a portlet, the dialog that allows a portlet to be selected will be opened.

Mobile devices

Here the pages that will be transformed for display on mobiles will be selected. For a selected page, the page property Transform for mobiles will automatically be set.

If a page is moved from one list to the other it will be checked if the page is in use in a plugin. In this case the page cannot be moved.

Access permissions

Access permissions to pages and data groups of an application are set here.


Plugins can be used to provide data from any Intrexx application, such as important sales data from various applications, or bundled appointments from various calendars.

Plugins are defined via the Properties dialog box of the application node or the Properties dialog box of a data group.

To define multiple plugins for different data groups, select the Plugins tab of the application’s Properties dialog box. There you will see an overview of all plugins defined in the application.

If you want to define a plugin for a single data group, go to the Plugins tab of the Properties dialog box for the corresponding data group. An overview of plugins defined for that data group is shown there.

Creating a plugin works the same in both dialog boxes. The only difference between the two is that when creating a plugin via the application in the first dialog box, the desired data group needs to be selected. When creating a plugin through the data group, the data group is already selected and cannot be changed.


Handlers can be defined in the property dialog boxes of Application nodes, Pages and Data groups. They can be used to run Groovy scripts. Within them, a distinction is made between an Action handler, which reacts to actions like saving or deleting data, and a Rendering handler, which is activated when the page is shown.

Action handlers can be used, for example, to write values from a data record when a new record is saved in a processing context, such as to create a history of a process.

An additional example of an application would be to generate IDs, such as NAME_YEAR_CUMULATIVE_NUMBER from various edit fields. If this problem is solved with a handler, neither a specific process nor JavaScript is required. For security reasons, the use of a handler is advantageous as well, since code is run on the server instead of client-side.

The scripts are run in the corresponding environment in which they are saved – scripts on a page are only run for that page, while scripts in data groups are run on all pages and actions contained in the data group, and scripts in the application node are run application-wide.