“Is there a way to train IDC to automatically delete the second page or merge it every time, so I don’t have to do it manually?”
This is asking if IDC can be trained to perform a specific task (deleting or merging the second page) automatically, saving you from having to do it manually every time.
None that I know of.
Depending on your version of IDC. In version 9.34 and above, there is a DocSeparator Misc Parameter that can detect if attached to a field and if it sees a different value in a field, split a document into multiple documents.
Also, if you have the Misc Parameter called AttachmentDetection and link to a field, this allows you to mark a page as an attachment page, and IDC will remember which pages are attachments.
This functionality has made the Classification model less likely to be used in implementations due to the ease of using Misc Parameters for splitting documents and detecting which pages are attachments.
In the case of the scenario listed above, I would explore if attachment detection would fix the issue. You could look at a monitoring tool that could take only the first page, but I would think attachment detection might be a good substitute.
“Can you explain how to configure the AttachmentDetection Misc Parameter in IDC to automatically detect and mark pages as attachment pages? How does it work, and how can it help in splitting documents or identifying attachment pages in a workflow?”
I typically add the AttachmentDetection to the VendorName for AP Automation.
When a page is marked as an attachment, the IDC system will look at the page and keep track of what was marked as an attachment. It won’t split the document, that is the DocSeparator Misc parameter.
AttachmentDetection This misc parameter makes it so that when a user marks a page as an attachment in Data Verify, the user will train the system to treat a similar page like that one as an attachment going forward. If there is no training data collected for a page, and no information is captured, with this option enabled, the page can be marked as an attachment in future. This should be applied to an assignable field in the DFD (a field with the Assignable flag applied). Exceptions: 1) The document should not start with an attachment page. 2) If all the pages in a document did not match training data, they should not be marked as attachments. 3) Any pages between two pages which match training data should not be marked as attachments.
Sorry to hijack, but have you found the DocSeparator to be, well, any good?
We have a customer who is having consistent issues with documents not splitting, or splitting erroneously, with it enabled.
It does take training the document to look at say an invoice number and when the document has the invoice number with the docseparator misc parameter this will cause doc to separate