Idea Details

Easily readable decision logs for Decipher

Last activity 21 days ago
Ismo Lehtiniemi's profile image
By: Ismo Lehtiniemi
07-24-2021 10:11

I would like to have some transparency for the decisions which Decipher uses to recognize specific field values.

Currently there are situations where either Decipher selects values that make no sense, or where Decipher does not select some values after countless training documents.

I would suggest to add some sort of easily readable log files, which would tell the user why some specific value was selected or why some field was not filled-in.

The log entries could be for example something like:
"Field 'Invoice number' was recognized based on a header value".

"Field 'Total amount' was not filled-in due to the  excluded header -values."

"Field 'xxx' was recognized based on the relative field location".

"Field 'yyy' was recognized by the existing Machine Learning models."

Ideas Portal

If you like this idea – vote! Ideas with over 20 votes will be highlighted to our Product review teams.
• Discussion is healthy! If you have a question or comment, don’t be afraid to jump in and start a discussion in the comments section below.
• Community collaboration is key!
This idea is new to the community and hasn’t been reviewed yet. While in the New stage, an idea is open for voting and comments to further the discussion around this idea.
This idea already exists! A change to the Duplicate status will always include a comment linking to the existing idea, so all voting and feedback can be collected in one place.
Need More Info
We’ve reviewed this idea, and determined we need a bit more info before deciding on how to move forward. An update to the Need More Info status will always be accompanied by a comment explaining which additional details are needed. Ideas are still open for voting and comments while in the Need More Info stage.
Under Consideration
We have all the info we need and are currently considering the feasibility of implementing this idea. Ideas in the Under Consideration status are still open to community voting and discussion.
Not Planned
We’ve reviewed this idea, and determined that it’s not feasible to implement right now. Ideas in the Not Planned status are no longer open for voting.
Coming Soon!
We’ve reviewed this idea and have determined that it will be delivered in the near future. Ideas in the Coming Soon! status are not attached to a binding timeline, but there is a concrete plan to implement this idea. Therefore we will have status does not allow for voting.
Congrats! Your idea has been accepted by the team and is now in production! Give yourself a pat on the back – you contributed to the improvement of one of Blue Prism’s products or services!