next up previous contents
Next: MICsubmit Up: MICverify Previous: Syntax   Contents

Description

MICverify is used to provide special verification procedures which are not handled by the datatype verification procedures. It provides for arbitrary tests and reports.

MICverify's are contained within a MICfieldspace tag. The name parameter assigns a name to this MICverify. Later, in the MICsubmit tag, one can specify MICverify names which must pass in order for the form to pass the verification process.

The test parameter may be either a block of code or a function name to call. A simple conditional statement is not sufficient because of the accounting necessary for MIC's error tracking and reporting functions. More about the necessary accounting in 5.1. For now, it will simply be noted that the code or subroutine must return a boolean where a true value indicates that no errors where found and a false indicates that an error was found, and thus, the associated error text contained between the tags should be processed and displayed when requested (with a MICerrorreport).

One may use a MICverify for the purpose of conditional verification. That is, there may be a situation where the user may want to verify fields A and B and run the verification X if parameter P is set, and perform no verification otherwise. This may be accomplished by using the verify_fields() and verify_verifies() functions defined as necessary for a MIC compliant fieldspace implementation. See 5.1.2 and C.1.1.

It is assumed (and highly recommended) that one will redisplay any fields involved in a failed test. This will give the end user the chance to change faulty data without having to return to an old form. See 5.3 for more about this.

Note that the MIC-HTML contained between the tags is deprecated because it may not include certain MIC tags. Specifically, other MICverifies are excluded (as well as MICfieldspace and MICdefine, obviously).


next up previous contents
Next: MICsubmit Up: MICverify Previous: Syntax   Contents