Composition tab of the Folder
In this tab, you indicate the hierarchical structure of the nodes that constitute the Folder. A Folder node corresponds to a Logical View managed by a Business Component.
The types of nodes
- The root nodes. There is only one root node in a Folder. It is the parent of all the dependent nodes and it does not depend on any other node. A root node is a hierarchical node that corresponds to a Logical View managed by a Business Component.
- Dependent nodes. They are linked to the root node or to another dependent node by a hierarchical relationship. A dependent node is a hierarchical node that corresponds to a Logical View managed by a Business Component.
- Reference nodes. They are linked to the root node or to another dependent node by a reference relationship. Reference nodes are not hierarchical nodes and they do not correspond to a Logical View managed by a Business Component. Then, they do not generate any processing and are inserted for control purposes only. The Data Elements that they contain are used as references to the Data Elements that are called in other nodes. Reference nodes cannot be updated.
Description of the tab
- An editable table. You can click some of the fields to display the list of the possible values.
When you move your cursor on a value in the list, the label that is associated with the value is
displayed in a tooltip.
From the Component, Logical View, Parent key, and Child key columns, you can directly call instances or change the called instances. Content assist is provided in these columns.
Note: For a guided input, you must use the definition sections that you open by clicking Add. These sections display only the relevant fields for the inserted elements, with all the possible values for each field. - Buttons that you can click to add nodes or node keys to the Folder, remove existing calls, or
move them in the tree.Note: The possible actions with the buttons are also available in the contextual menu of the table.
If you remove a root or dependent node, all its dependent nodes are automatically removed. However, if you remove a reference node, the node that it references is not automatically removed.
- Sections that open depending on your selection in the table or on the line you want to create. These sections contain fields in which you select or enter the values. When you save, these values display in the table.
Node insertion in the table
The first composition line of a Folder is always the root node. You insert it by clicking Add a root node. The Folder contains an error if the root node is not declared.
The nested composition lines correspond to child nodes. They depend on the root node or on a dependent node. They fit under the line that is selected in the table when you click Add a child node. Child nodes are dependent or reference nodes.
For all the nodes, you must indicate the Node code. This code must be unique in the Folder composition.
For the root node and the dependent nodes, you must also select the Business Component and Logical View. Both are required. The association of a Business Component and a Logical View must be unique in the hierarchy (working context and higher projects in the design build path). Therefore, a root or dependent node belongs to only one Folder in the hierarchy.
All the Business Components and Logical Views that are called in a Folder must be defined in the hierarchy. The Logical View must be called in the -CS Lines of the selected Business Component.
To indicate a Business Component and a Logical View or change them if they are already called, you can click Change in the Component and Logical View lines of the node description section. A selection wizard opens with the instances that can be selected. Select or create an instance and click OK. It is then displayed in the table.
You can also specify a Business Component and a Logical View directly from the Component and Logical View columns of the table.
- Place the cursor in the column and enter the name directly. To make the input easier, you can open a content assist wizard by clicking Ctrl and the space bar simultaneously. If you start entering a name, the content assist displays the instances that start with this input. If you enter the name of an instance that does not exist and if you validate, the input is discarded.
- Click the button that appears when you set your cursor in the column. In the selection wizard that opens, select an instance.
Additional specifications for child nodes
- Node type. You must indicate whether it is a dependent or reference node.
- Cardinality. A root node or dependent node can have one or more dependent nodes. The possible cardinalities on a dependent node are then (0,1), (0,n), (1,1), and (1,n). However, a reference node references only one node. The only possible cardinalities on a reference node are then (0,1) and (1,1). When you save, a warning is displayed on the node call link if the cardinality is invalid.
- Subschema. This field is specific to a reference node. Its input is optional. It can be used to narrow the selection to the Data Elements that belong to a subschema in the Logical View.
- Select a child node and click Add a key.
A selection wizard opens. It displays all the Data Elements that are called in the Segments of the -CS Lines in the Business Component declared in the child node.
- Select a Data Element.
It is then displayed on the Parent node Data Element and Child node Data Element lines of the key definition section and in the Parent key and Child key columns of the table.
- Select the corresponding Data Element in the parent node. To do so, you can click
Change on the Parent node Data Element line of the key
definition section.
You can also indicate the key Data Element directly from the Parent key column of the table.
Two methods are possible:- Place the cursor in the column and enter the name directly. To make the input easier, you can open a content assist wizard by clicking Ctrl and the space bar simultaneously. If you start entering a name, the content assist displays the instances that start with this input. If you enter the name of an instance that does not exist and if you validate, the input is discarded.
- Click the button that appears when you set your cursor in the column. In the selection wizard that opens, select an instance.
This direct input method from the table also applies to Child key column.