Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

to be released….

API’s

GET/orders/detail

  • the endpoint was returning “unkown job type” for Edge-only and Addon orders. This has been resolved.

  • the endpoint was missing the rtClass field

  • added the shipToMethod label

  • fixed issue that was preventing some of the fields related to each eye from being sent (rt/lt LensStyle, rt/lt LensMaterial, rt/lt Sph, rt/tl Cyl, etc)

POST/orders/add

  • Fix issue with the OCHT fields not being interpreted properly for SV(Single Vision) lenses

  • When a traceID included a SHAP trace, the SHAP was not being passed to the order, resulting in no tracing being used by the order

POST/orders/addStock -

  • when running the endpoint, the order number assigned to the the order was not being returned when the add was successful

  • Make sure there is at lest one valid item before creating the stock order. Verify that all quaquantities for the valid line items are not 0

Frame Inventory

When the frame module is active, programs and functions that require “frame inventory” will check to see if it’s active before allowing the programs or functions to be accessed or processed.

Remote Orders

The remote order process was replacing the Ship-to sent in the remote order file with the one from the customer. The program has been changed to keep a ship-to when sent.

Reports

Orders in process - the report has been modified to replace the patient name with the purchase order number if the system setting, “Use PO num instead of patient in JT e-mails” in the “E-mail” tab is checked.

Shipping Methods

The carrier codes that display based on the shipping method selected were not being properly displayed. This has been fixed.

  • No labels