Some control types can load required data from the database themselves, assuming Database was selected as data source.
The control type Tree load data from a database table depending on hierarchy level. First of all, the root level is loaded; the second level is loaded by expanding a node and so on.
This reduces memory usage and the control can be displayed faster.
You can define actions to be executed if a specified operation is applied to the collection data. Events can be triggered by the following.
|Insert||A single row was added to the collection.|
|Delete||A single row was deleted from the collection.|
A single collection data value was updated.
|Bulk||A set of rows was added to the collection or deleted from it.|
To define an event
The view switches to Configuration (custom) and the new Insert subnode is selected. In the Node editor view, you can manage the following settings.
|Identifier (optional)||Enter the name for the event.|
|Operation*||Select one of the operations listed above.|
|Collection*||Select a collection in the option box. You can navigate to the selected collection using and apply further settings if necessary.|
|Control-ID*||A Control-ID is preset. You can overwrite this.|
To define an expression-based event
The view switches to Configuration (custom) and the new subnode is marked. In the Node editor tab, you can manage the following settings.
Before you can assign a collection to a component, you must prepare the custom component to make it suitable for the collection.
To do this, the component requires a "virtual collection", which you will find under the component’s Property node in the definition tree view. Collections are assigned in the "virtual collection".
"Virtual collections" defined on components are marked as compulsory or optional.
Compulsory "virtual collections" must be assigned to a location collection. This assignment is made where the component's usage is defined.
Before you assign a collection to a component, a node must be configured under Collection mapping under the component.
Collection mapping nodes are automatically assigned when a component reference is added. These nodes are added automatically but not configured. You configure them in the Node editor view. You can also add a Collection mapping node with the help of a wizard that you can call from the context menu. Another option for adding these nodes, is to add a single node that you can also access through the context menu of your component in the definition tree view.
NOTE: The following instruction steps are based on an example of a direct container reference.
To assign a collection to a component
NOTE: If you add a component reference, the subnodes for collection mapping are automatically added. If more nodes are required for collection mapping, you can either add a Collection mapping type node yourself or by using the wizard. Other nodes may be added when you add a node with the wizard. You can delete these afterward.
To define a virtual collection for a user defined component
This displays the object in the definition tree view.
A new virtual collection is added in the definition tree view.
Note: Use the Object type and Cursor required options to limit collection assignment further. Use the Object type option to ensure that the assigned collection must be a database collection of the given type. Use the Cursor required option to specify the point of the assigned collection which must be within an iteration above this.
To declare a configuration key for a module or a component
You can see that the new configuration section is selected with empty fields in Node editor.
The configuration section is displayed with its name in the definition tree view.
The new parameter is added under the configuration section.
Note: You may have to edit further settings depending on which parameter type you selected.