Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

 
SYNTAX:
 
xpxValidateModelWithParameters (modelId                 : GENERIC;
diagnosticFile          : STRING; options                 : INTEGER; ruleSchemaId            : GENERIC; userOutputFile          : STRING;VAR validationResultId  : GENERIC;VAR returnValue         : GENERIC; numberOfParameters      : INTEGER; argument1               : GENERIC;...                  ... argumentN               : GENERIC)status                  : INTEGER;
 
This function invokes the EDMmodelChecker to validate all instances in the specified data model against the rules and constraints specified in the <options> argument.
The result of the validation can be a text report, a population of the Express schema EDM_Validation_Result_Schema or both. A population of the EDM_Validation_Result_Schema enables the caller to make his own diagnostic report in his own format.
There exist two options that will influence the amount of information in the validation report produced by this function: XPXNO_PRINT_OUTPUT and XPXFULL_OUTPUT
A standard validation report will be produced when none of these options are set in the <options> argument. A validation report with all available detailed information is produced when the XPXFULL_OUTPUT option is set. No validation report will be produced when the XPXNO_PRINT_OUTPUT option is enabled. The validation result would then normally be in a population of the EDM_Validation_Result_Schema.
When validating data model against rules specified in an EDMruleSchema, only he following validation options are effective: XPXFULL_VALIDATION, XPXGLOBAL_RULES, XPXLOCAL_RULES, XPXUNIQUENESS_RULES. XPXFULL_VALIDATION means in this context: XPXGLOBAL_RULES ~| XPXLOCAL_RULES ~| XPXUNIQUENESS_RULES .
A number of arguments can be supplied to the ?model validation process? in the arguments argument1, ?, argumentN. Hence the validation process can be made parameterized. The validation process can return a value to the caller through the returnValue argument. The value to return must be set in the validation process by invoking the xpxReturnValueToCaller operation.
See related functions: xpxGetNumberOfUserParameters, xpxGetUserParameter
This function is only applicable to data models.
The data model that holds the instance to validate must be open before this operation can be successfully performed.
The argument <options> specifies the options that should be used during the validation. The <options> argument should be specified as a bitwise OR of one or more of the following integer constants:
 

  • XPXFULL_VALIDATION
  • XPXGLOBAL_RULES
  • XPXLOCAL_RULES
  • XPXINVERSE_RULES
  • XPXUNIQUENESS_RULES
  • XPXREQUIRED_ATTRIBUTES
  • XPXATTRIBUTE_DATA_TYPE
  • XPXAGGREGATE_DATA_TYPE
  • XPXAGGREGATE_SIZE
  • XPXARRAY_REQUIRED_ELEMENTS
  • XPXAGGREGATE_UNIQUENESS
  • XPXOUTPUT_STEPID
  • XPXFULL_OUTPUT
  • XPXSTOP_ON_FIRST_ERROR

This function is equivalent to the EDMinterface function edmiValidateModelWithParameters.

  • No labels