Hi Red,
Good to hear from you!
Ok, I totally hear you and this is certainly an area we're working on, but let me take you through a bit of the detail.
I appreciate in most circumstances you're uploading a "document", but that's not how Decipher sees it. Instead it's considered a file as it may contain multiple documents or multiple document types and in order for the classification engine to work, this has to be broken down. So the first part of the image processing is to split a file into pages.
If classification is disabled, then sure, these will be put back together as a single document. But if it's enabled, Decipher will refer to the classification model to decide how to proceed. At this time, the initial document processing doesn't differ between whether classification is enabled or not.
The next stages of OCR and capture both process pages 1 at a time, this is in line with how the training data is constructed and helps it work quicker than if it were processing entire documents. Following these stages, the document ID is created and allocated to the respective pages. So the ID's linking them can be traced as you mentioned via SQL, but as the document ID isn't created during the upload period it's not immediately available for tracking.
And to return to the multiple documents in a single file concept, you would then have the same file name across 2 or more documents. So you not only need to know what the file name was, but now you need how many of them there are.
This is one of the things which makes Decipher super flexible in its file management, but as a result you get the challenge outlined above.
We've got a lot of great things coming in this space, including a new accuracy report and we appreciate your interest.
Thanks for your feedback, I'll make sure it gets to the right people.
Regards
------------------------------
Ben Lyons
Product Consultant - Decipher Specialist
Blue Prism
UK
------------------------------
Ben Lyons
Principal Product Specialist - Decipher
SS&C Blue Prism
UK based