# In the KTM Statistics Viewer module; how are the results "Correct"; "Incorrect" and "Rejected" defined?

19888
Article # 304842 - Page views: 138

19888

QAID # 19888 NOT Published

 QAID # 19888 NOT Published   Please do NOT provide the article number (QAID) and/or URL of this Knowledgebase article or its contents to external customers, as it is NOT Published and/or * INTERNAL ONLY *.

## Question / Problem:

In the KTM Statistics Viewer module, how are the results "Correct", "Incorrect" and "Rejected" defined?

“Correct” means KTM believes the field is "correct", the field is extracted with at least the minimum confidence levels and the associated Validation Rules return valid results.

"Incorrect" means the field is initially considered "correct", the field is confidently extracted and the Validation Rules return valid results, but the field is still corrected by a user (validation operator). This indicates that the initial value, even though confidently extracted and the Validation Rules satisfied, is “incorrect”.

"Rejected" means KTM rejected the results either due to the Locator not satisfying the minimum confidence levels and/or the Validation Rules returning invalid results. KTM rejects the results, not a user.

“Correct” and “Incorrect” correspond to a user's actions on the fields.

“Rejected” corresponds to KTM rejecting the results on the fields.

For example, from the user's perspective:

If the field is green (valid) and the user does not change the value, the field is considered "Correct".

If the field is green (valid), but the user determines the result is not correct and changes the value, the field is considered "Incorrect".

If the field is red (rejected) due a failed Validation Rule, the field is "Rejected".

If the field is red (rejected) and the user changes the value before confirming the field, the field is considered both "Rejected" and "Incorrect".

The number of "Correct" and "Incorrect" fields usually add up to the total number of fields, but not "Rejected" fields as it represents the fields "rejected" by KTM and not the users.

 Note that if a field is set to "Require manual field confirmation", it is considered "Rejected" as the user must manually confirm the value of the field.