The properties of the context node are as below:

 

Node Name: The node name specifies the Name of the context node.

 

Interface Node: Interface node property of the context node determines whether the node can be used for cross component communication (One component to another Component) or not.

Say for example we have two components Component A and Component B. When the component A to which contains a context node “STATUS” is used in another component B then the component B can access the node STATUS if it is interface node. Interface nodes are mainly used for the purpose of transferring data from one component to another component. The context node in a component that is created in the view level does not provide interface option and cannot be accessed in other components.

 

Input Element (Ext.): Usually when we want a context node to be used in the number of views we define it in the component controller context and map it to the view required by dragging and dropping the context node in the different view. We call it data mapping ref to document data mapping.

 

Dictionary Structure: Here we specify a dictionary object reference as a structure to the context node. It can be either table or structure. When the dictionary structure is referenced to the context node then the attribute of the context node can only bear attributes belonging to the structure or table specified. Also it is not necessary that all the fields of the dictionary structure is to be used as the structure of the context node, we can choose only the required fields from the structure. Apart from the fields in the dictionary structure any attribute other then the fields in the dictionary structure specified cannot be added unless and until the dictionary structure reference is removed.

Cardinality: Here we specify the cardinality of the context node. i.e. the no of the records that the context node is subjected to have at run time.

 

0..1 – It can contain up to one record or nothing.

1..1 –  It can contain only one record. A record by default is instantiated.

0..n – It can Contain N no of records or nothing.

1..n – It Contains one record instantiated by default or any No of records.

 

 

Selection: This selection specifies no of (Elements or rows or leads) can be selected by the user for processing. The input is similar to that of the cardinality.

 

 

Initialize lead selection: If the initial lead selection is checked then one (Element or row or lead) will be selected by default. It will be the first element of the context node.  For example, when you display the data in the context node using the table UI element one row of the table will be selected by default.

 

Singleton: Singleton property is set to reduce the load of the context node. Say for example when we have a parent-child relationship between two nodes, Node A (5 Elements) and Node B (10 elements). When the Node A is accessed it loaded with all the elements of the Node A as well as all the elements of the Node B when the singleton property is not set for node A. The same when the singleton property is set for the Node A, then only the 5 elements of the Node A along with the records corresponding record of 1^st record in the node A with Node B will be loaded.