topic Re: Where does Verification Exception reason get stored? in Product Forum

Where does Verification Exception reason get stored?

denzain — Tue, 22 Mar 2022 21:11:15 GMT

Dear all,

While performing verification in Decipher, if the user has to mark a document as exception (right click > Set as an exception) a new popup appears to record the exception reasons.
Here I have added a few exception reasons. The question is are they stored in the Decipher database at all? If yes which table has this information? I have gone through all the tables but unable to find it. Please help.

The exception reason appearing on the 'Description' column of [Batch] table is always the same generic message - 'All Documents were marked as exception and the batch is also marked as exception' Where does the description and text from above screenshot go?

Re: Where does Verification Exception reason get stored?

Ben.Lyons1 — Wed, 23 Mar 2022 13:37:39 GMT

Hi Kalash,

The exception detail is in the Document table, in the Notes column. You can quickly find them using the IsExceptional column as a filter e.g. WHERE IsExceptional Is Not NULL.

Thanks

Ben

Re: Where does Verification Exception reason get stored?

Athiban_Mahamathi — Mon, 25 Sep 2023 11:01:07 GMT

Hi@Ben.Lyons1,

Notes column stores only the Exception reason detail. Can you please let me know where the exception description will be stored ?

Re: Where does Verification Exception reason get stored?

Ben.Lyons1 — Mon, 25 Sep 2023 12:03:19 GMT

Hi @Athiban Mahamathi Mathialagan,

It looks to me like it's all in there.

The description set in the Document Type will automatically appear when the respective reason is selected, the user can then add to or overtype the details.

You can see in this example I've added the text "- Additional exception info" when marking the document as an exception. A use could have deleted the "Test exception" text as well.

Thanks

Ben

Re: Where does Verification Exception reason get stored?

Athiban_Mahamathi — Tue, 26 Sep 2023 01:39:34 GMT

Hi @Ben.Lyons1,

Thanks. I am able to see both error reason and description.

Regards,

Athiban