...
An issue was corrected where, when a device requested an order by PO number, if there were two orders with the same PO number, one completed today (pending completion), and another that is active, the interface would find only the pending completion order and therefore return a job not found condition. It will now return the active order.
When processing some API’s and other RxUniverse menu functions, if you tried to locate an order using the order’s PO number, it would not always locate the active order if another order completed today (pending completion) with the same PO# was found.
The blank list produced when calculating an order was not correct when blank substitution logic was used. The “Mixed” flag in blank substitution was doing the opposite of what it was intended to do.
When using PO number to request orders from devices, if there was a pending completed order with the same PO number as an active order, the device interface would located the pending completed order and not return the active order. This has been corrected.
When a remote order requests a frame that has an attached shape, the circumference was not being set on the order. This has been corrected.
A previous change was made to always handle DO as DOENG for engravers. The Device Interface Parameters, Other2 tab, has been changed to add a new checkbox “Send DO as DOENG for Engravers”. This will allow labs to have the ability to turn this option ON or OFF.
When a order has had a breakage, and the order goes through an ART manual blocker a second time, the values sent for GPRVM and KPRVM are not the same ones as the original call before a breakage was done. This has been corrected.
When a tracer uploads a 2-eye trace as an upload session and not a tracer session, the left-eye trace was not being saved. This has been corrected.
When making an active job a remake, the original order is now checked to see if a previous remake had been done. If so, the user is now prompted with a warning message.
When calling the list of available devices using the API_DEVICES endpoint, the call was failing. This has been corrected.