Is there a way to get Exception batches back into Blue Prism.

[CharlesTrott1]

We have a scenario where files are being transferred from Email, to Blue Prism, to Decipher, to Blue Prism, to an API call, to Email confirmation at present. It's a bit complicated but effectively Decipher is capturing the data and helping Blue Prism transform it to the API call. While most of this works as expected, in some scenarios, bad *.pdf files (PDF's that include changeable fields, or non-flattened data) are Exceptioned by the system. 

What I'd like to know, is there a method in the Decipher.dll that allows Blue Prism to get these exception batches. The idea is to be able to complete the email loop and state the file was not accepted by Decipher X number of times in a period such as a Blue Prism Scheduler. 

For reference I'm wondering if it's just built into the Decipher.Dll already like this

try {
var nextBatch = Connection.GetNextCompletedBatch(QueueName, new RabbitMqConnectionFactory());

[BenLyons · Accepted solution]

Hi Charles,

The exception handling in Decipher's not quite the same as Blue Prism, where you send it on separate path to be handled in a different manner. For Decipher it means it's the end of the journey and as such it never reaches the Export client (this means it won't be sent to RabbitMQ).

That being said, there's certainly things we can do to facilitate an exception path. In Decipher 1.2 we added a new permission that enables selected users/user groups to access documents marked as exceptions (that have been moved into a separate batch). These are accessed in the Data Verification tab, check out the video here for an overview.

If you're in 1.1 or this doesn't quite meet your needs, the alternative is that you don't use the in product option to mark as an Exception. It's a bit trickier, but you could create a new field in your DFD with the options Yes/No as to whether the user would like to mark it as an exception. This could be used by a Blue Prism process to check the status before deciding on a path.

You'll need to select the Virtual flag and remove the Assignable flag for this to work correctly (you don't want it to store the value in the training data). And if you have any validations that may hold it up, you'll need to add the flag for Soft Validations.

Let me know if you have any questions on those options.

Thanks

Ben

[CharlesTrott1]

Hi Ben, 

Thank you for your prompt response, this is just to extend the conversation a little bit more. 

Your suggestion about the Virtual Flag and Soft Validation is something I'm already utilizing when documents do not meet full criteria. But this question is more born out of a document that is not compatible with Decipher and errors out before I can get to any sort of Validation. 

What I would like to see is a way for the "Exception" to be an output data, or status for the batch where it can be picked back up by an automation when collecting Exception batches out of RabbitMQ. 

What I will do instead for this automation is create a BP process where the associated input cases will automatically be marked for reply after a window of time has passed if there is no answer. While this is not ideal, and I would hope that the Decipher team is able to create a better pattern for exception handling at all points of the Document lifecycle. 

[BenLyons]

Hi Charles,

We fully appreciate the need for progression in Decipher's exception handling and it is something we're working on.

If you have some thoughts you'd like to share with the Decipher team, please submit them as an Idea via the Innovate menu above.

Thanks

Ben