Field status
When you verify documents, each field has a symbol that shows its status.
|
The field has been interpreted correctly. |
|
The field needs to be verified manually. |
|
The field contains an error. |
Point to the symbol to read a tool tip that tells you the exact status of the field:
| Symbol | Status in tooltip | Description |
|
|
Complete | Fields with this status have been interpreted
and validated without error, based on the
document definition. A field with this status
has been:
|
|
|
Retype | Fields with this status contain no errors
detected by
Kofax ReadSoft Entrance.
However, the field is associated with a field profile that has
Retype
selected as an option.
Kofax ReadSoft Entrance
compares the data you type with the data it interpreted and tells
you if there is any discrepancy.
Retype can also indicate that Kofax ReadSoft Entrance has calculated the field value using the values of other fields, instead of interpreting the actual field on the document |
|
|
Field proposal | Kofax ReadSoft Entrance found more than one field that might be correct. You need to choose the correct field in the Field proposal column. |
|
|
Validation error | One or more of the validation conditions you defined for the field are not met, so you must check and possibly correct the data. |
|
|
Manual entry | A field with this status must be typed manually in Verify, because the No interpretation option was selected for the field profile. |
|
|
Interpretation error | Kofax ReadSoft Entrance
found the field but could not interpret one or more of the
characters in the field.
Fields with the Interpretation error status can be manually entered in Verify. If you experience consistent interpretation errors of a particular field, you can apply a filter or change the text type of the field definition in Optimize to solve the problem. |
|
|
Field error | INVOICES could not find the field. The field is not considered to be "found" if the required title is not interpreted completely and correctly. If the title is not found, then technically the field value is not found, either. |