Viewtemplates Overview
A ViewTemplate defines what and how data is presented, e.g., specific fields of one dataset ordered in single lines, or multiple datasets in table form, with or without Action buttons, etc. The ADITO standard installation includes a set of predefined ViewTemplates, which fit for most use cases.
In order to assure a consistent and ergonomic design, ViewTemplates cannot be created or customized by the user. In special cases, if none of the predefined ViewTemplate types fits, and a workaround is not possible, then a customized ViewTemplate can be ordered from ADITO.
To add a ViewTemplate to a View, open the View in the Navigator window and choose "Add ViewTemplate" from its context menu. Consequently, a dialog will open, in which you select one of the ViewTemplate types included in the list on the left. Furthermore, enter a name for the new ViewTemplate. The field "Assign to" is only required for configuring a MasterDetailLayout and a HeaderFooterLayout (see chapter on layouts); in other cases, it can be ignored.
After creating a new ViewTemplate, it appears in the Navigator window as sub-node of the View it refers to. If you click on the ViewTemplate, you can edit its properties in the "Properties" window. The following properties are common to multiple or all ViewTemplates:
title: The text of the list item shown via the View selection button, if the ViewTemplate is intergrated into a GroupLayout. (Unless you set the "title" property, a (non-configurable) default name is shown.)
maxDBRow: Allows you to set a limit for the number of datasets to be displayed in the ViewTemplate. CAUTION: Depending on your ADITO version, all datasets exceeding this number will be ignored without notification (e.g., when using the filter bar above a ViewTemplate of type TreeTable).
entityField: The name of the EntityField that should be available for loading. Setting this property to "#ENTITY" means that all fields of the Entity can be loaded and are therefore available in the EntityField-related properties, e.g., "columns" or "fields". If you actually need only one single EntityField (e.g., in ViewTemplate "WebContent"), you should select it in property "entityField" accordingly, because this will restrict the loading process and therefore result in a better performance.
In the following chapters, the function and configuration of all available ViewTemplate types are explained (in alphabetical order), with the prerequisite that property entityField is set to "#ENTITY".