Allow DA clients the ability to submit multiple sources per batch

[dlruddick]

An enterprise customer (Chorus/ Bridge/ Document Automation) uses the capture process to ingest images that originate in emails. Because the sources are sent as a packet that should be worked as a single work-item in Chorus, they would like to send them as one transaction to Document Automation. 

Our request is to facilitate transitioning this customer to be able to submit multiple sources into a single DA batch.

[dt216183]

How does one get routine status of this rquest?

[dlruddick]

That's a really great question, let me see if I can find out. 

[dt216183]

Which development team is assigned to this?  The client this is for is asking for weekly updates.

[dt216183]

Is this part of a JIRA board I can track?

[dlruddick]

@dt216183 I was able to 'subscribe' to the content for labels with Document Automation. 

[Michael_S]

Hi all, if you go here:

https://community.blueprism.com/t5/c-hfgie69872/Chorus+BPM/pd-p/chorus-bpm

And click Options > Subscribe, you'll receive a weekly digest of all Chorus ideas and activity in the community. Alternatively as @dlruddick mentioned, you can subscribe to the Label to get just ideas.

As participants in this discussion, you should all automatically get email notifications whenever the idea status is updated or a new comment is added also - unless you've changed any settings in your profile 🫡

[dt216183]

Thanks Michael

[jabardwell]

This is critical to our immediate processing needs to consume inbound emails which often contain multiple document attachments.

[dlruddick]

We have another client use case that we need to ensure will be fixed with this updated code. 

Their work items are going down the ‘batchreject’ path because of a logo (jpg) within an email that is being created as an additional source attachment.  Even though there is a valid templated form within the batch that could follow the DA path, the whole batch routes to DA Review, which doesn't provide a benefit in using Chorus DA if these have to be manually reviewed each time. 

Under the Sorting tab in the DA Workspace, we see a digitized batch with multiple source attachment 'sub batches' below it. The batch status shows as digitized even though one 'sub batch' is rejected and one ‘sub batch’ is digitized.  We need the ability to return the status of the entire batch vs the rejected status of a 'sub batch', or the ability to cycle through each 'sub batch' to determine the appropriate routing path. 

If all 'sub batches' are rejected, the status of the batch shows as rejected, which is working as expected. But in this scenario where at least one 'sub batch' is rejected but we also have a digitized batch, we would want to manually review only the rejected batch. 

The below  screenshot is from testing Chorus DA that rejected the entire batch due to the email logo.