The Leaf Fields (LEAF) page allows you to set up and maintain leafing information for all of the application pages.
The following information can be set up on this page:
UI Package – The name of the application.
Page – The name of the page that you are leafing to/from.
Record Source – The name of the attributes record source.
Leaf Name – The logical name of the leaf column.
Attribute Name – The name of the attribute/column/field to be used for leafing to a different page.
Export Only – If selected, then only leafing out is possible from this page.
Leaf Destination Usage – Indicates whether the attribute’s value is required, optional, or not used to leaf.
Not Used - if the Not Used selection is made, the Leaf Attribute is not used in the leaf action, but leafing will still occur. The default value is Not Used.
Required - if the Required selection is made, the Leaf Attribute must be provided by the source page, otherwise leafing will not occur.
Optional - if the Optional selection is made and the Leaf Attribute is provided by the source page, then the value provided is used to filter appropriate data on the destination page. Otherwise, if no value is provided, the Leaf Attribute is not used in the leaf action, but leafing will still occur.
Full Key vs Partial Key Leafing – Both full key and partial key leafing is supported. For full key leafing, the full set of primary key(s) for the destination page must be provided by the source page in order for relevant data to be displayed. If a destination page requires two keys and the source page only provides one of the keys, then this leafing will not occur. For example, the primary key for the Title (TITL) page is the Title code (TITL_CD), and the primary key for the Sub Title (STTL) page is the Title code (TITL_CD) as well as the Sub-Title code (SUB_TITL_CD). Full key leafing provides leafing functionality from STTL to TITL, since STTL can provide the full key required by TITL. However, if you wish to leaf from TITL to STTL using only the Title code, full key leafing does not allow this to happen as STTL requires two keys to display matching records.
For partial key leafing, the source page may provide only partial key information of the destination page. For example, the LEAF setup for the STTL table would be as follows. The key fields are Title and Sub-Title. Title is set up as Required, whereas Sub-Title is set up as Optional. This means that if the Sub-Title code is provided by the source page, then it is used, together with the Title code, to filter appropriate data on the STTL page to bring up only those records that match both the Title and Sub-Title code selected. If only the Title code is available and no Sub-Title code is available (such as when leafing from TITL to STTL), then only the Title code is used to perform the leafing. STTL displays all records containing the selected Title code.
Leaf Attribute Prefix – Accommodates query objects on the target page. If a column exists on more than one table in a query object, specify the Leaf Attribute Prefix with the table name to avoid an ambiguous column error.
For example: If a query object is made of the EMPL and the EMPL_ASGNMT table and has an attribute (INTERNAL_EMPL_ID) that is present in both of the tables, Architecture needs to know form which table the column should be referenced. In this case, the Leaf Attribute Prefix can be given as either EMPL or EMPL_ASGNMT.
Filter Method – Valid options for this field are Default or Equals.
Filter Method – Valid options for this field are Default or Equals.
Leaf Group/Entry Set – This is a required field that defaults to 0. This field is used to group Leaf entries together for the purposes of building a primary key to use for lookup to the target page for Show Description and Show Details. The Leaf Name and Group/Entry set combination must be unique within the UI Page, Package, and Record Source.
You can transition to the Context Sensitive Search page by clicking the Context Sensitive Setup Related Page link.