I would like to export the number of symbols corrected during verification. This value appears to be stored in dbo.DocumentEditingStatistic.CorrectedSymbols. (Or at least an indicator that 1 or more characters were changed during verification). I did not find a Service field Source that would give me this information and am unclear on how I would query the database directly if that is what is needed.
From a business perspective, I am using ABBYY for Invoices and I want to assess whether a particular vendor is being captured reliably (no changes in verification). If the capture quality is near 100%, then I can have a script bypass verification for high-confidence invoices for these vendors. The UncertainCharacters tells me ABBYY is uncertain about something, but it does not tell me that something was actually incorrect.
From a business perspective, I am using ABBYY for Invoices and I want to assess whether a particular vendor is being captured reliably (no changes in verification). If the capture quality is near 100%, then I can have a script bypass verification for high-confidence invoices for these vendors. The UncertainCharacters tells me ABBYY is uncertain about something, but it does not tell me that something was actually incorrect.
Comments
2 comments
1. I created a set of "ComparisonCopy" fields in the document definition. One Copy_field for each exported field.
2. I created a post-recognition/pre-verification stage where I set the values from the standard export fields into the Comparison Copy.
3. I created a post-verification/pre-export stage where I compared the values from the standard fields against the Comparison Copy. And I set a value into an export field indicating the number of fields changed.
Thank you for sharing your solution.
Document editing statics table is usually used for custom reports in monitoring console. Retrieving correct information from this table may require complex queries.
Your solution is simple and probably the best way to get information about changed fields.
Regards
Timur
Post is closed for comments.