- Open the Mask Data form and search for the default mask created during model definition. This will be used as template for the new mask.
Depending on the content to be displayed in the mask you must select the following default mask as a template to be copied:
- Display master data -> default master list/form
- Display type data -> default type list/form
- Display child elements for a 1:n relation -> default Refine list for relations or master list of table 2 for links
- Display child elements for n:1 relation -> default Aggregate list relations or master list of table 1 for links
- Make sure that the index card with the Field Assignment sub-list is in the foreground. Only thus guarantees that the mask-field relation will also be copied when the mask is copied in the next step.
- Copy the default mask record, assign a new mask name and modify the following mask master attributes:
- Change into the Field Assignment sub-list and modify the mask-field relation attributes for each field contained in the mask.
DataView has automatically copied all field assignments of the mask template into the list. You can edit the existing mask-field relation there.
If you want to import additional table fields from other tables into the mask (or calculation fields already created in the field master), you will have to save first, then insert a new record in the sub-list and select the name of the desired field in the modal window. Please note that you only import table fields of connected tables.
If you do not want to display certain table fields in the mask, you will have to save first, then select the desired field assignment in the sub-list and delete.
Field
|
Comment
|
Confer
|
Field Name
|
For field assignments already copied you do not change the field name. A new field is imported by selecting it in the modal window. Table fields can be identified by their syntax TABLENAME.COLUMNNAME. If a mask component is to be inserted, a modified name is required.
|
-> Mask components
|
Sequence
|
Here you specify the position number of the field. It determines the real field sequence in lists and the logical field sequence in forms.
|
-> Field sequence and field position
|
Order
|
Here you use a number to specify the value of the field for sort procedures after database queries. If possible, assign the sort identifier for one field only in order not to reduce performance unnecessarily. This value can be changed by the user at run-time.
|
-> Sorted query results from the database
|
Row, Column
|
Here you specify the position of the field in forms. For fields in lists the entries will be ignored.
|
-> Field sequence and field position
-> Display of logical fields (check boxes)
|
Length, Width Virtual Width
|
Here you specify the field dimensions. The row length of fields in lists is always 1. You only explicitly define a virtual width if the defined (visible) width of the field is smaller than required by the field content (lack of space), else you enter 0.
|
Access Flags A, U, I, Q
|
Here you specify field access in Mask-Edit state, in A mode-independent, in U, I, Q mode-dependent. With Z = empty entry you can make the field invisible.
|
-> Field access
-> Visibility of fields
|
Video
|
Here you select the color of the field content (1.digit) and the field background (2.digit).
|
-> Color settings for fields and field titles
|
Menu Menu type
|
Here you link the field to a selection tool. For mask components you enter the mask name here.
|
-> Selection tool at fields
-> Modal windows at fields
-> Mask components
|
Pre_Field Userexit Post_Field Userexit Hyper-field Userexit
|
Here you can install userexits at field triggers. If a userexit requires parameters, you enter them separated by a space after the userexit.
|
-> Field trigger
-> List of standard field userexits
|
After saving both the copied mask in the header form as well as all field assignments will have been logically defined in the sub-list.
- Change into the Field Default sub-list, overwrite mask-independent field master attributes with mask-specific values and edit the field title attribute for each field contained in the mask.
You will see some field master attributes twice in the mask. The columns without the identifier ...-M show the mask-independent field master attributes. They cannot be edited and are for information only. In the masks with the identifier ...M you can overwrite them mask-specifically. If you do not enter anything, the entry in the mask-independent field master attributes will remain valid for the mask.
After saving the field default assignments the mask will have been logically defined.
- Change into the Additional Attributes sub-form and install the trigger functionality of the mask (additional mask master attributes).
After saving the trigger functions at the mask will have been installed.
- Change into the Mask Data header form and create the mask in main memory via Reconfigure.
DataView creates the mask and copies it into main memory. It is available as interaction object on the user interface and can be called via menu items, buttons or events.