I’m going to give this a shot with my perspective because I would look at it this way:
A document (or the information in a document) is a complex datatype and forms one part of your transaction attribute. Therefore document understanding by itself may not necessarily contain everything that will help you handle transaction based processing . You may have to supplement the DU + Action center capabilities by adding a mechanism to track the transaction.
For example: Processing an invoice record can be considered a transaction which contains the following steps:
- Get the Invoice Header record containing the Invoice Number
- Get the Invoice Item records with that Invoice Number
- Each Invoice may have one or more Invoice items
When you process a single invoice record, these 3 steps become part of a transactional Unit of Work. They must complete successfully if started and if there are failures, it must be completely rolled back. Otherwise the Invoice items can be orphaned without their invoice header information.
Therefore, you track all the 3 steps above with some kind of a Unit of Work (UOW) number . Each UOW record that you are tracking in the system either ends with a Success or Failure (rollback)
Now, you can extend this analogy to your DU Process and that may translate to roughly the following steps:
- Assign the incoming document with a unique UOW Value - this can be a number, a GUID or a datetime stamp that is unique
- Split the document and each page in turn is associated with that UOW ID
- Determine if each page needs to go to the action center based on your risk factors
- If yes, post page to action center, and when it is processed by the human supervisor and returns to the flow, you will have to UOW as part of that page
- Therefore even if the document is split or single, or even if it goes through action center or the DU Flow straight, the UOW flows with it.
- In the end, you would have extracted the information from the page either with or without human intervention and that information for that page+the parent document+the UOW ID can be recorded as part of the unique transaction ID.
- That is because UOW ID is at the document level and therefore all pages in that document will get the same UOW ID after you split it. But combining it with the page number will make that record unique.
What is the challenge factor?
You have to find a way to integrate the UOW ID in your RPA flow and make sure it is flows in and out of the Action center correctly.
I hope this concept helps flesh out the solution.