Controller: Context 

Every controller has a context in which the used data are stored hierarchically. This context is empty when a new component is created. To create and maintain the context of a controller, choose the Context tab page in the Controller Editor.

On the left side of this tab page you can see the structure of the context that you want to process. To create a structure beneath the empty root node of the selected context, open the context menu for this node.

Create: The Create function enables you to design your context by creating individual context nodes and context attributes. Note the following rules:

·        For each context you can create either attributes or nodes beneath the root node. Attributes that were created directly below the root node are called “free attributes”.

·        No mapping can be defined for the root node CONTEXT. If you want to define mapping for a context node later, first you have create a new subnode below the root node, since no mapping can be defined for this root node.

 However, it is possible to map to a root node. This means that you can define mapping for a non-root node to the root node of a different context.

 

·        No mapping can be defined for individual attributes. This is why you have to create a new node first for the attribute(s) that are intended for mapping.

·        All nodes must have a unique name within a context. Nodes with the same name are not permitted in different hierarchy levels. Attribute names can be used several times, however, as long as they were not created in the same node.

·        All child elements within a node must have a unique name. It is not permitted for a subnode to have the same name as an attribute of the same node.

·        Names of context elements may contain letters and numbers, but no special characters.

 

For more information, see:

Creating and Maintaining Context Nodes

Creating and Maintaining Context Attributes

Defining Mapping