Areas of the Applications module


The Applications module is subdivided into five areas. The size of each area can be adjusted by dragging with the mouse. To do that, position the mouse at the edge of an area until the mouse pointer changes to a double-headed arrow. If there is insufficient space for elements to be displayed in an area, vertical and/or horizontal scroll bars will be shown automatically.

Every tab, with the exception of the workspace, in the module can be closed via the symbol next to the title. If you show a tab via the View menu, and it is shown in its own window, you can also anchor it in one of the areas to the left or the right of the workspace, by dragging its title with the mouse to the desired position.

While the window is being moved, the area will be shaded in gray in its future position as a preview, and then anchored at the moment you release the mouse button. Areas can also be made into their own window.

From the View menu, areas can be hidden and then shown again. Furthermore, the default view can be restored.

Application structure

In the upper left area of the Applications module, the hierarchy of the individual pages and data groups of an application will be displayed.

Clicking on the arrow symbols left of an element's name allows subordinate levels of the application structure to be opened or closed.

Application node

The application node can always be found at the top of the application structure. It represents the application itself. Settings such as title, version, application menu, portlets and permissions can be edited in the properties dialog. New data groups, external data groups, system data groups and view pages can be created via the New menu when the application node is selected.

Data groups

Click here for more information about data groups.

System data groups

Click here for more information about system data groups.

External data groups

Click here for more information about external data groups.

Data fields

The data fields of a data group can be shown or hidden in the application structure via the Edit menu / Show/Hide data fields.

Every data group also find the following system data fields:

  • (PK) (S) ID

    ID of the data record

  • (S) UserID

    ID of the user who last edited the data record

  • (S) ChangeDate

    Date of last change

  • (S) CreatorID

    ID of the user who created the data record

  • (S) CreationDate

    Date of last change

  • (S) ChangeDate

    Date of last change

These data fields can, if desired, be additionally connected to view elements. When creating a data set in the browser, system fields will automatically be filled with relevant data by Intrexx.

Data types

The Elements used in the application development can be linked to data fields. Data entered in the edit elements can be saved in the connected data fields. View elements can display the values saved in the data fields. Intrexx uses the following data types for data fields:

  • String

    Short text

  • Text

    Long text

  • Integer


  • Double

    Decimal numbers

  • Datetime

    Date and time

  • Boolean

    Boolean values such as true and false.

  • File

    Referral to files

How the Intrexx data fields are actually mapped to the physical data fields of the portal database depends on the type of database used.

View pages

This symbol designates view pages, on which data entered to an application will be shown.

Edit pages

Edit pages are always found within a data group. Data can be recorded using corresponding elements here.

Pages in the application menu

This symbol designates view or edit pages that are connected to the application menu. These pages can be directly accessed in the browser from the application menu. The application menu can be changed in the properties dialog of the application node.

Start page

This symbol designates a main or edit page that has been defined as the start page of the application via the Edit menu / Start page. The start page will be loaded first when the application link is clicked on in the browser, regardless of its position in the application menu or whether it is there at all. Edit pages can therefore only be defined as the start page if they are located in data groups directly beneath the application node.

Portlet pages

This symbol designates a view page that is being used as a portlet.

Office integration

Edit pages with Office Integration are represented by this symbol.


Click here for more information about this topic.


Frequently used items can be included in this area for quick and easy access.

Configure favorites

Opens a dialog w here elements can be added to the favorites list.

Export favorites

Exports the favorite list as an XML file.

Import favorites

Imports an exported favorite list.

ReadContainer and WriteContainer

These areas can be shown or hidden via the View menu. Every ReadContainer or WriteContainer that has been defined on the current page will be shown here. More information about this topic can be found here.

Add ReadContainer

Opens a dialog where a new ReadContainer can be created.


The contents and appearance of the workspace will change, depending on whether a page, data group, or the application node is selected in the application structure. If, for example, the application node has been highlighted, the workspace will provides information about the application description, start page, additional pages and the application history with ID and date.

If a data group has been highlighted, the name of the corresponding database table will be shown. All data fields and references of the data group will be listed.

If an application page in the application structure has been selected, elements can be assigned via drag & drop to the workspace.

If an element on the workspace is moved with the mouse to a position that is not allowed, such as when elements overlap one another or when the borders of the workspace have been exceeded, the border of the element will be shown in red. It will not be moved. When you let go of the left mouse button, it will return to its original position.

The most important properties of the elements will be displayed in a quicktip when the mouse is positioned over an element.


Elements with script calls or comments will be automatically designated with a blue symbol. Mandatory fields will be designated on the workspace with a red symbol.

Help lines

On the workspace, vertical and horizontal help lines can be inserted via the Edit menu / Horizontal/Vertical help line. They are added at the last position of the mouse. Existing help lines can be deleted via Edit menu / Delete help line. The workspace will then be given a grid on which view and edit elements can be aligned. Additionally, a ruler will help you to position the elements. The current coordinates of the mouse pointer will be shown highlighted on the ruler. In the application options, the properties of the workspace can be modified, e.g. to deactivate the ruler or grid. You can select elements on the workspace by clicking on them. You can select multiple elements by clicking with the mouse and dragging a border around the elements, or by clicking on the elements, one after another, while holding down the Ctrl key.


With the Edit menu / Group, selected elements can be grouped together.

  • Group

    The group uses a background shading.

  • Group label top

    The grouping is created with the HTML element div and the page, where the grouping is made, is transformed to a layout without tables. Titles in the controls are hidden and title fields are shown above the controls.

  • Group inline

    All elements are transformed as inline elements. Depending on the element type, display:inline; or display:inline-block will be written in the CSS.

  • Group H1

    The text of the grouped elements are automatically assigned the style class H1.

  • Group transparent

    Groups the elements without background shading.

  • Group hidden

    Groups the elements and hides them.

  • Ungroup

    Removes the grouping.

The key combination Ctrl + a highlights every element on the workspace. When this is done, elements that are found in a group will not be individually selected. If you have selected an element in a group or have selected the group itself, the key combination Ctrl + a will highlight all additional elements in this group.


You will find the Zoom tab underneath the workspace. If the Grid element is located on a page without a table layout, the individual columns of the rows can be edited in the Zoom area.

Hidden area

In addition to the workspace, there is also a hidden area, which – like the workspace – can have elements added to it. The elements defined here are not displayed on the screen. Using the keyboard shortcut Alt + h, the hidden elements can be displayed if necessary, for example, for testing purposes. Elements can also be moved to the hidden area via drag & drop or via the Edit menu / Move to hidden area and then configured just like visible elements.

Elements can be moved back to the workspace in the same manner. If elements should be used in the JavaScript and their functions should be available in the browser, you need to activate the checkbox in the Web column. If the setting is not activated for a particular element, then that element can only be used server-side, (e.g. in Velocity).

Hidden group

Groups the elements and hides them. You can open the properties dialog of the hidden group by double-clicking on the Hidden elements entry. Other groups can be created within the highest level grouping in the hidden area, e.g. to group the hidden elements into smaller units for clarity.

Search, Notifications, Problems, Description, Script

At the bottom, you will find more tabs which can be shown/hidden via the View menu.


Search field

Enter a search term here.

Drop-down list

The following functions are available here:

  • Attribute value

    Searches for the value of an attribute.

  • Data fields without edit control

    You can search through the application for Data fields without edit element in order to list all data fields that are not connected to an edit element.

  • Elements with comments

    Lists all elements that are commented if you do not enter text in the search field. If text has been entered to the search field, the search engine will look for elements that contain this text in their comments.

  • Elements using JavaScript

    When searching for Elements using JavaScript, all elements will be listed that have a script call entered in their events.

  • Elements using style class

    Elements using style class will find elements that have been assigned a specific style, which you can enter to the search field.

  • Elements linking to other applications

    The search for Elements linking to other applications returns all elements that are connected to other applications, such as buttons whose target page is found in another application, or tables that show data from other applications.

  • Elements without title

    Searching for Elements without title will find all elements that have no title entered for any of the portal languages.

  • Groovy

    The search for Groovy returns all elements that are using Groovy script.

  • GUID: Definition

    This function will find the element with the GUID you entered in the search field.

  • Buttons / Buttons sending an email

    The search can be run for buttons and buttons that execute a send email action.

  • Velocity

    Searching for Velocity finds all VTL include view elements integrated into the application.


Triggers the search. Hits will be shown beneath the search field. If you click on a hit, the corresponding element will be highlighted on the workspace.

Search history

Opens a window with a list of the most recent searches. Click on a search action to repeat it.


On this tab messages will be printed, for example if an element cannot be deleted because it is linked with other elements.


Intrexx supports you in many ways when developing applications. Most of the checks for avoiding incorrect configurations are already performed directly when editing elements. In addition, there is the "Problems" pane, which scans the currently opened application for errors and warnings. The underlying algorithm is constantly being expanded and will help you to ensure that your applications will continue to function properly and be maintainable in the future. Even in seemingly problem-free applications, new problems can be listed after an Online Update. This is not due to a faulty Online Update but to the continuous development of the algorithm for detecting errors.

The "Problems" pane contains the following types of messages:

  • FIXME or TODO marker in JavaScript

    This gives you an overview of all fixme or todo comments in the application's JavaScript. The application can be published despite the messages, if desired. Click here to learn how to set the appropriate markers in the script.

  • Errors

    Prevent the application from being published and must be fixed unless the "Allow application to be published despite error entries in the 'Problems' area" setting is enabled in the options.

  • Warnings

    The application can be published despite reported warnings.

By default, the FIXME and TODO markers from the JavaScript are listed at the top, followed by the errors and then the warnings. The sorting of the individual columns can be changed by clicking on the column header.


Here you also have the ability to enter a description of the currently selected element. This applies to all elements of an application, i.e. also pages, data groups, data fields, etc. The texts you enter here will be adopted in one language when the application is saved. Elements with a description will also be designated with a symbol on the workspace.

If entering a description is not possible, such as when multiple elements are currently selected, this symbol will appear in the comments field.


On the "Script" tab, an overview of all script calls used on the page is provided. By double-clicking on an entry in the "Element" column, the element, which the script call is assigned to, will be highlighted on the workspace. Double-clicking on an entry in the "Call" column opens the corresponding script at the correct place in the editor.


Click here for more information about this topic.