Arguments
LIMITED—use the default functionality in versions prior to V7.2. This means that declarative checks are performed when the user modifies an occurrence.COMPLETE—ensure the validation of all modified data in the component, regardless of how it was modified. Default if setting is omitted.
Defaults
| Assignment file: | Any application assignment file |
| Section: | [SETTINGS] |
| Default value: | COMPLETE
|
Description
$VALIDATION determines the extent of validation that is performed when the active path is left, for example with a ^NEXT_OCC structure editor function or when the store statement is executed:
Note: The $VALIDATION setting is not supported for static server pages.
Note: This setting is provided for compatibility only. For this reason, it is recommended that components are updated to consider complete validation.
Validation Compatibility
In versions of Uniface prior to V7.2, only data on the active path was subject to declarative syntax checks. When the active path changed through user or ProcScript action, or when a store statement was executed, declarative checks were made only if the user had changed the occurrence or if $fieldcheck or $occcheck had been set. If data was generated in batch mode or via ProcScript in interactive mode, no checks were made. If the database accepted the unchecked data, this allowed data to be stored which did not conform to the declarative checks.
Beginning with V7.2, this situation no longer occurs, since the implicit validation of
all modified data ensures that data within a component conforms to the declarative, as well as
procedural, checks. However, the setting $VALIDATION can be used to reinstate the
older functionality in part or in total.
