08-27-2013 02:32 PM
Let me play the role of a customer for a second and ask a question:
"I've upgraded to 13.0.0.68 and all of my existing Scan Batch logic written in the Unity API is broken! My Scan Batches are being created in some strange status and the batches themselves won't transition to the designated queue until I transition out of this 'Unknown' status! What's the deal?"
08-27-2013 03:02 PM
After already releasing version 13 of our software (including the Unity API) we discovered some issues with a few pre-Awaiting Index queues and assigning Scan Batches to them through the Unity API. The Scan Batches weren't correctly being assigned (for example) to the Awaiting Document Seperation queue when a developer would create a given batch using the API.
To correct this issue, we made a significant change to our already existing BatchManagement logic that could break any Unity API Batch solutions created before version 13.0.0.58. Instead of batches starting in the 'Awaiting Index' queue when they're created in the API, we had to compensate for those pre-Index statuses by creating another place for them to start called 'Unknown'.
This means that:
For any further questions or concerns please feel free to contact your first line of API Support for assistance. If you are unsure who your first line of API Support is, please contact us at apisupport@hyland.com and we can point you in the right direction. We are happy to assist you in troubleshooting if you are part of an API Certified organization. If you are not API Certified, we can put you in contact with our Custom Solutions Group who would be able to assist you as a billable service.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.