Skip to main content

Viewtemplates and Layouts Overview

This section explains which ViewTemplates and layouts are available in ADITO and how they structure the content of a View. Use it to choose the right presentation pattern for records, lists, actions, and multi-area View compositions.

It is intended as both a decision aid for selecting suitable standard components and a reference for understanding how Views are assembled in practice.

ViewTemplates​

A ViewTemplate defines which data is displayed in a View and how that data is presented. Depending on the selected type, it can render individual fields, multiple records in a table, charts, cards, action-oriented content, or other predefined UI patterns that are part of the standard installation.

To ensure a consistent and ergonomic design, ViewTemplates cannot be created or customized by users. If none of the predefined ViewTemplate types fits a required use case and no suitable workaround is available, a customized ViewTemplate can be ordered from ADITO.

Adding a ViewTemplate​

To add a ViewTemplate to a View, open the View in the Navigator window and choose Add ViewTemplate from the context menu. In the dialog, select the required ViewTemplate type from the list on the left and enter a name for the new ViewTemplate.

The field Assign to is only required when configuring a MasterDetailLayout or a HeaderFooterLayout. In all other cases, this field can be ignored. After the ViewTemplate has been created, it appears in the Navigator window as a subnode of the corresponding View. When you select the ViewTemplate, its properties can be edited in the Properties window.

Common ViewTemplate Properties​

The following properties are available for multiple or all ViewTemplates:

  • title defines the text of the list entry shown in the View selection button when the ViewTemplate is used in a GroupLayout. If no value is specified, a predefined default name is used.
  • maxDBRow defines a limit for the number of datasets displayed in the ViewTemplate. Depending on the ADITO version, datasets that exceed this limit may be ignored without notification, for example when using the filter bar above a TreeTable ViewTemplate.
  • entityField defines which EntityField is available for loading. If this property is set to #ENTITY, all fields of the Entity can be loaded and are therefore available in EntityField-based properties such as columns or fields. If only one specific EntityField is required, for example in the WebContent ViewTemplate, it should be selected explicitly to reduce the loading scope and improve performance.

Layouts​

A layout is a property of a View. It defines how multiple ViewTemplates or referenced Views are arranged within that View, for example vertically, horizontally, or as selectable sections.

Detailed information about layouts and all available layout variants is provided in the Layouts section.