{"id":31898,"date":"2015-03-10T11:41:21","date_gmt":"2015-03-10T19:41:21","guid":{"rendered":"https:\/\/ephesoft.com\/docs\/2019-1-2\/batch-class-management\/index-fields-4050\/validation-rules\/"},"modified":"2021-01-06T14:16:43","modified_gmt":"2021-01-06T21:16:43","slug":"validation-rules","status":"publish","type":"docs","link":"https:\/\/ephesoft.com\/docs\/products\/transact\/features-and-functions\/administrator\/batch-class-management\/index-fields-4050\/validation-rules\/","title":{"rendered":"Validation Rules"},"content":{"rendered":"
This page provides an overview of validation rules in Ephesoft Transact. This information is intended for Transact administrators.<\/p>\n
To create and configure validation rules, the following prerequisites must be in place:<\/p>\n
Validation rules use regular expressions to determine if an extracted value is correct.<\/p>\n
When an index field value is extracted from a document, Transact will run the extracted value against the validation rules for that index field. If the format of the extracted value matches the regular expressions (regex) set in the Validation Rules <\/strong>page, the field will be automatically validated.<\/p>\n These rules are set at the index field level.<\/p>\n This section describes how to create and configure validation rules for an index field.<\/p>\n <\/p>\n Figure 1. Validation Rules<\/em><\/p>\n <\/p>\n Figure 2. New Pattern<\/em><\/p>\n <\/p>\n Figure 3. Select Option<\/em><\/p>\n <\/p>\n Figure 4. Phone Number Validation Rule<\/em><\/p>\n Note: <\/strong>In the example above, we’ve used the following expression for a phone number:<\/p>\n \\(?([0-9]{3})\\)?[-\\. ]?([0-9]{3})[-\\. ]?([0-9]{4})$<\/p>\n This will validate U.S. phone numbers entered in the following formats:<\/p>\n For more information on regular expressions, refer to Regular Expressions<\/a>.<\/p>\n When creating multiple validation rules for a single index field, you can specify whether all rules must be satisfied for a field to be validated, or only one rule. To do so, change the Validation Operator <\/strong>on the Index Fields <\/strong>page.<\/p>\n <\/p>\n Figure 5. Validation Operator<\/em><\/p>\n Validation rules are applied automatically by Transact during the Automated Validation <\/strong>module.<\/p>\n If a validation rule cannot be satisfied, it will appear highlighted red during Validation for operator intervention. When hovered over, the following message appears:<\/p>\n “<index field name><\/em><\/strong> could not satisfy the validation pattern.”<\/p>\n <\/p>\n Figure 6. Field Not Matching Validation Rule<\/em><\/p>\n If an index field is consistently being marked as not satisfying the validation pattern, you may need to edit your existing rule or add another validation rule to cover the variation.<\/p>\n This completes an overview of how to create validation rules in Ephesoft Transact.<\/p>\n","protected":false},"featured_media":0,"parent":31894,"menu_order":5,"comment_status":"closed","ping_status":"open","template":"","doc_tag":[],"yoast_head":"\n<\/a>Configuring Validation Rules<\/h2>\n
\n
\n
\n
\n
\n
\n
\n
<\/a>Configuring the Validation Operator<\/h2>\n
\n
\n
\n
<\/a>Using Validation Rules<\/h2>\n
<\/a>Conclusion<\/h2>\n