When you specify model settings for a project, you select the model you want to assign to it, and specify any desired verification settings.
To specify model settings for a project
1. On the Navigation Tree, click Automator > Standard Processes and select Project Editor.
2. On the Model and Verifications tab, click the Browse button next to the Location field, to select the desired model.
3. In the displayed window, select the data source type from the following: Local, Named Paths, Web, or Definition Objects.
4. Depending on the data source type specify other parameters:
o Local: Specify project location and path to it.
o Named Paths: Select the appropriate named path and select the project file path from the list of displayed in the Named Path Content box.
o Web: Specify project location.
o Definition Objects: Select definition object type and select the definition object from the list of displayed in the Available Definition Objects box
5. If you want to specify verification settings for report inputs, select the desired options under the Model
Verifications heading.
Note: Verification is not available for database inputs. See Verifying Projects for additional information.
6. To save or download created project file, click the corresponding button or continue specifying other project settings if necessary.
Note: When saving a project file provide a comment in the displayed window and click Commit. The Definition Objects' Project page is displayed, where you can edit project file name, revision and access rights if necessary.
The next step in creating a project is to specify input settings for it.
Verifying Project Reports
Datawatch 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, Datawatch 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 Modeler. Note that any verification settings recorded in the Modeler model will be honored. These can be found in the Field List of Modeler.
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 Datawatch Automator will continue processing the associated job even if a verification failure of the specified kind is encountered. If you prefer to have Datawatch Automator stop the job when a verification failure occurs, simply select the Stop option instead.
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).
Viewing Model Information
Model Information section provides detailed information about the Modeler model assigned to the current project.
Here you can view, copy and print the information contained in the current model. It also provides access to the Audit Trail.
Note: The contents of the Model window vary, as they are determined by the contents of the current model.
The Model Information section displays information such as:
Author: Displays the author of the current model.
Description: Displays the description of the current model.
Input Settings: Displays information about the current input settings, such as whether to ignore leading control characters and form feeds, whether to interpret input as ASCII, when to force a page break (i.e., after n lines), etc.
Templates: Lists the templates within the model, provides information about them (e.g., their names, whether they are floating traps or multi-column traps, their trap characters, etc), and displays sample
lines of the data they trap.
Fields: Lists the fields within the model and provides information about them, e.g., their names, their type (character or numeric), their data and display lengths, their alignment, etc.
Filters: Lists filters defined for the model. Each entry on the list shows the name of the filter, the filter type, and the filter expression.
Sorts: Lists sorts defined for the model. Each entry on the list shows the sort name, sort fields used, and sort order (ascending or descending).
Summaries: Lists summaries defined for the model. Each entry on the list shows the summary name, filter used, custom page setup, number of keys, and number of measures.
Summaries: Key Fields and Measures: Enumerates key fields and measures for each summary in the Summaries list. For each Key Field, the field names, titles, display lengths, and sort directions are displayed. For each Measure, the measure title, display length, and expression are displayed.
Audit Trail: Displays the audit trail for the current model.