Issue:

All documents are classified as unknown after upgrading to 3.1.2.5 for batches sent through an encrypted batch class. This only effects encrypted batch classes that were already imported to a 3.1.2.4 system which is then upgraded to 3.1.2.5.

 

Solution:

Between release 3.1.2.4 and 3.1.2.5, there was a change to the encryption schema for encrypted batch classes. When upgrading from 3.1.2.4 to 3.1.2.5, if the batch class was encrypted before the upgrade, all batch instances will have documents classified as unknown document types.

The solution to this is after you upgrade from 3.1.2.4 to 3.1.2.5, you will need to ‘learn files’ in the encrypted batch class before sending any batch instances though the encrypted batch class.

Was this article helpful to you?

J.D. Abbey

Comments are closed.