Field Type

as discussed in pattern creation and editing docid\ jjgd058ld kkhafjahuom , when creating a pattern, field type can be declared to create the expectation that data being received into the field fits a format expectation and can be presented accordingly via the api the available field types and their respective formats are field type description examples of accepted values text no type format is assumed; any text value is accepted as a value, so no validation will be performed "quarterly report" notes similar to text, but allows for longer inputs and is intended for manual entry the document view will display a character count for this field so users know how long the field can be no validation will be performed "kevin can you confirm the extracted values from this document and review accordingly?" numeric validation will be performed to ensure the entry is a value that contains numbers, optional commas, an optional decimal point, and optional parentheses to denote the accounting style of negative value 15 92 (90) 1,000 25 money validation will be performed to ensure the entry is a value that contains the same validation criteria as "numeric" as well as optional special characters for currency $2,950,000 00 (9,000 00￥) 75 99 percent validation will be performed to ensure the entry is a value that contains the same validation criteria as "numeric" in addition to a special character for percentage 99 98% (10)% 15 5% date validation will be performed to ensure the entry is a value that maps to a valid date the document view in the application will map this value to the iso 8601 format and will also provide a "date picker" that will show the date in a calendar view and will allow date selection directly from the calendar 01/01/2019 november 15, 2022 20 july 2018 19/09/2000 boolean validation will be performed to ensure the entry is a true or false value the boolean type is nearly exclusively used with the anchor tool's checkbox detection feature checked checkbox, unchecked checkbox picklist validation will be performed to ensure the entry is a value that matches against a user defined list the document view will show this field value as a dropdown listing out the possible values if an unlisted value is extracted via automation or smart capture, then a validation error will occur list \[buy, reduce, hold] accepted value buy if extracted or inputted data doesn’t meet the type definition as outlined above, a validation message will display this validation error can be resolved by removing the record or by editing the record with the correct value/ format, which will be evaluated once you click away from the entry box if this live evaluation determines that your entry matches the field type, then the validation error for that field will clear