To display the content of the Group definition section, you must select or create a Data Element group in the Logical View call lines. A group is a set of elementary Data Elements. You must indicate some information such as the Logical View attributes directly in the call definition section. Other information such as the data transfer or the subschemas are to be specified in a wizard that you open from this section.
You can insert Data Element groups in the composition of a Logical View. A group can include other groups. All the elementary Data Elements are then counted to define the group. There can be nine nested levels maximum. It is strictly forbidden to use the same Data Element more than once in the Logical View composition.
The extraction method is sent to the Business Component through the technical part of the message. Parameters must be described in the application part of the message, that is in the Logical View.
In the Data type field, you specify the parameters by value for all the extraction methods that can be used by the Logical View. To do so, you call defined Data Elements. For each parameter, you enter the E type, which indicates that it is a parameter. Each identifier Data Element (U type) is an implicit parameter. The other Data Elements that describe the contents of the Logical View cannot be used as parameters. The E-type Data Element does not belong to the description of a Logical View. If necessary, you can define and call a child Data Element.Options | Description |
---|---|
None | Data Element that is not used as a parameter. For the Data Elements that describe the Logical View. |
U: identifier for paging | Data Elements that are to be used as selection criteria or start key for the reading of data occurrences in the database. Identifier for the paging of a list for the client. As output from the server, it contains the selection criteria values of the next page. |
R: repeated structure | There is only one repeated structure for a Logical View. A repeated structure is specified in the group Data Elements. This Data Element indicates the beginning of the repeated Data Elements. The end of the repeated Data Elements is deduced from the number of Data Elements in a group. The number of occurrences must be indicated in the Number of occurrences field in the Logical View definition. |
E: extraction parameter | The Data Element is used as a parameter for an extraction method. The E type Data Elements must be entered in the -CE lines before the Data Elements that describe the Logical View contents. Each identifier Data Element (U type) is an implicit extraction parameter. The other Data Elements that describe the Logical View cannot be used as parameters. If necessary, you can define and call a child Data Element. |
Options | Description |
---|---|
O: required | Required Data Element. The check for its presence
is generated in the client, and in the Business Component if CHECKSER=YES. Note: It
includes checks in relation to the Data Element description.
|
P: required | Required Data Element. The check for its presence
is generated only in the Business Component, if CHECKSER=YES. Note: It
includes checks in relation to the Data Element description.
|
Blank | The checks that are specified in the Data Element description are generated in the client, and in the Business Component, if CHECKSER=YES. |
F: optional | The checks that are specified in the Data Element description are only generated in the Business Components if CHECKSER=YES. |
Click More to open a definition wizard. In this wizard, you indicate to which subschemas the Data Element group called in the Logical View must belong.
Click -G Lines to define -GC lines (comments), -GE lines (error messages), and -GG lines (generation elements) for each Data Element group that is called in the Logical View.