|
|
Validation Kick Back The QVALS feature is further enhanced by the new "Validation Kick-Back" facility. Now, in Validation specification at the function level, you can select option "R" (Repository) and select to attach the validation to either the Record Layout, the Data Dictionary OR the Classification Dictionary field (if applicable). Indeed, with validations other than type 'M', you will be automatically prompted to place the entry in the dictionary. Previously you had to hit F10 to go to the DataBase creator menu and key the validation against the appropriate area and then return to the Function Spec and hit F19 to include the Repository validation into the Function Spec. When Validations are copied from the Data Dictionary to the function spec (or indeed from the Data Dictionary to the Record Layout for file specific enhancements to a field validation) a cross reference table is kept so that whilst looking at validations at the Classification Dictionary, the Data Dictionary or the Record Layout, you can select the 'W'here Used option to see where the validation has been copied. When in the Classification Dictionary the Validation Where-Used option shows 3 sections. Section 1 shows any field in the Data Dictionary where the validation has been copied from the Class Dict. to be made more specific for the DD field. Section 2 shows if the Class Dict. validation has been copied directly to the Record Layout to be made more specific for the field in the record layout. Section 3 shows where the Class Dict. validation has been copied directly to a function spec. You can choose to update these lower level validations from this display. In the Data Dictionary validation where-used there are only 2 sections. The Record Layout and the Function Spec. which are based on the Data Dictionary validation. The Record Layout validation where used has only 1 section which are the functions that contain a validation based on the validation against a field inthe record layout. The current File Where Used function only shows files that are declared in section 3 of spec overview. We have tried to encourage specifiers to enter 'Reference Only' specifications in section 3 of the overview for files which are not read for the display but are quoted in validation and/or secondary update specifications, to give a better overview of files read in the program and also so the file where used (from the file list) gives a full list of the programs where the file is used. We have decided to remove the discretion of the specifier and Genesis V will now automatically create entries in section 3 of the overview for any X/N/A type validation or any secondary update. In order that these 'planted' entries do not interfere with the sequence of the files which are entered normally to signify files that are to be read to load the display, they will be given a sequence number 98, 97, 96 etc. descending and to indicate whether the file is a validation file or a secondary update file, the 'How used' box (normally blank, X or R) will be set to 'V' for a validation file or '2' for a secondary update file. |