Automator supports verification of report inputs on a project-by-project basis.
NOTE: Verification is not available for database inputs. If a project calls for database inputs, the verification options are simply ignored.
Verification settings allow you to specify the kind of verifications you want it to perform when processing the project's associated job. When project verification is enabled, Automator may verify field boundaries, data types and filter results.
NOTE: Automator performs verifications after running the PreExport script (if any), and before performing any exports.
Specify the desired verification settings by selecting the appropriate check boxes on the Model and Verifications tab. The following types of verification are available:
Following filter produces at least one row — Checks that when the specified filter is applied to the data, the resulting table contains at least one row.
Following filter produces no rows — Checks that when the specified filter is applied to the table, no rows are produced. For example, you may have created a filter that performs checks on your data to ensure that it is valid, and if any bad rows are returned by this filter, you wish to abort the procedure.
Field boundaries and data types for text inputs — Checks that all fields are in the correct location, are the correct length, and are of the correct data type. This is equivalent to using the verify feature in Monarch. Note that any verification settings recorded in the Monarch model will be honored. These can be found in the Field List of Monarch. (Note: This feature is not available for database and PDF inputs.)
Unfiltered table has at least one row — Checks that the unfiltered table contains at least one row of data.
Text field lengths — Checks that all text fields have valid field lengths.
Numeric field decimals — Checks that all numeric fields have valid decimals.
Numeric field lengths - Checks that all numeric fields have valid field lengths.
Database fields — Checks that all database fields have been defined correctly.
Calculated fields — Checks that all calculated fields have been defined correctly.
Date/time format precisions — Checks that all date/time fields have the correct format precision.
When you select a verification option, project verification is activated. Note that the default If verification fails setting is Continue. This means Automator will continue processing the associated job even if a verification failure of the specified kind is encountered. If you prefer to have Automator stop the job when a verification failure occurs, select the Stop option instead. If you want to stop the job without sending an email alert, select the Stop without error notifications option.
The If verification fails option applies to the entire set of verifications. If this option is Stop, then the first failed verification causes the job to immediately fail, thereby skipping any subsequent verifications. If this option is Continue, then all the verifications are performed regardless of their success or failure. In either case, the verification results are noted in the <verification> section of the job log.
If verification fails, a "SystemAlertVerifyFailed" alert is raised in the job log, then the job either continues or fails, according to the specified continue/stop option.
Whenever Automator performs verification, it writes a <verification> section to the job log, regardless of whether verification is successful or not. The verification section of the jog log looks similar to this when successful:
<verification>
<verify_project id="1">
<field_properties>
<success>
<model>
<location>C:\Test\Models\V7\Lesson11.xmod</location>
</model>
</success>
</field_properties>
</verify_project>
</verification>
If a verification failure occurs, the <verification> section of the job log will contain some details about the type of failure and its specific location within the input report(s).