Suspension of job when transaction put to action centre

I am creating a process for taking invoice which are added as attachment to emails, pushed through document understanding and then added to our financial system.

  1. I intend to have a dispatcher process which solely strips the attachments from the emails and queue a job for each individual attachment to a queue to be processed through document understanding.
  2. I intend to have a performer which processes the queue items from stage 1 (the attached document) through document understanding then queue a job to a performer to add the attachment to the account system.
  3. I intend to have a second performer to add the invoice to the accounts system.

Very simply:

  1. Dispatcher to separate attachments from emails.
  2. Performer to process attachments through document understanding.
  3. Performer to add invoice to accounts system.

My question is regarding the first performer used for document understanding. How does the queue deal with transactions when the action centre is invoked for an invoice with low confidence. Does the queue suspend the current transaction and start a new job for the next transaction in queue or simply suspend the queue until the action centre query is resolved?

@duncan.macdonald

If you use wait in transactions then it will wait till the action is completed

Instead you can collect all the outputs of create form tasks and create action center tasks in the end process process state usign the collated task outputs…the task outputs can be added as array and can loop and run for each parallel activity with only wait for resume activity

cheers

Hi @duncan.macdonald

The DU Template deal with one document by time. When a job entering in Suspended state, the process is able to process other job (new queue item).

If you want process more than one queue item by time without waiting the job entering in Suspended State or Completed (having available licenses and resources) you can change the Queue Trigger to process simultaneously:

This process needs to be linear and process just one queue item, create the action and wait, then create a queue for the performer (3) when complete for each item. You do not want the DU performer to be a looping automation.