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 30 Next »

to be released …

Order Entry

  • Under certain circumstances, the True Curve was being set to zero. This has been corrected.

  • When the browse button was pushed for the Right OPC (under Select by OPC), it was selecting the Left OPC. This has been corrected.

  • Fix issue where BSI was getting set to zero under certain circumstances which was causing cut out/cribbing issues.

  • Change made to no longer clear the frame information fields when changing the frame status or when frame status is None, Other or Lens Only. If there is frame information sent on the order we always want to keep it regardless of the frame status.

Customer Service

  • When doing a copy or remake of an order, the Order Valid time was being copied from the original order. This has been fixed.

Digital Orders

  • When “Re-calc job on auto-attach” is checked, a change was made to make sure that toric calculations are now being done before submitting digital orders to a digital calculator. This was causing some settings to not be updated. ie. FCSGUP and FCSGIN

API

  • The add order endpoints (V1 and V2) will now check if the submitted PO is already in use for the customer and return an error if so.

  • Add Order V2 will now return an additional array called creationRemarks that will include any additional informative notes about the order

  • Add Order v1 now documents the structure of the returned object in the case of a success

  • The POST/orders/waitingForFrames will no longer include deleted orders

  • Required string parameters will no longer accept an empty string as a valid value

  • Alpha-numeric order numbers are not located when trying to find an order, this has been fixed.

System Settings

  • Fixed issue where the user was prompted to save changes to the Default SHAP on the ROE tab when there were no changes made.

  • Added new flags to the Inventory tab to allow frame and miscellaneous items better control over the creation of inventory transactions when an order is un-valid.

  • Changed the description of labels regarding Lens Safety Allowance for finished lenses and also changed the help screens to make them clearer. This was also done on the lens style database.

  • Added new system settings that will allow the lab to specify the options that should be passed to PDPrint (if using). See the PDPrint manual for available options.

    • The following options are managed by Rx-Universe and are not supported: -lk, -c, -s, -o, and -p

    • These can be set individually for each of Work Ticket, Trace Only Work Ticket, AR Envelope, Invoice, and Stock Invoice

Remote Labs

  • Modified the remote lab database to allow better control of the order type when sending an order to an outside lab.

  • Outsourced orders will no longer send the tag _FRSKU in the generated raw file. This was causing issues when outsourcing from a lab with Frame Inventory to another lab with Frame Inventory when labs used different SKUs for frames.

Inventory transactions

Frame and miscellaneous items can now control if an inventory transaction is created when an order is un-valid. Prior to this, there was only one flag that controlled lens, frames and miscellaneous items.

Inventory Counts

You can now input counts from flat files. Refer to Inventory Count document to see how this new method operates.

Order completion

When un-shipping an order, at times an unwanted inventory adjustment transaction would appear. This has been fixed.

Price Lists

  • Fixed an issue where the displayed Kind of Lens was incorrect when editing a price list

  • Fixed an issue where the check to see if a new price list duplicates an existing one was not run correctly

Devices

  • OMA interface

    • When auto-attaching a trace using the tray number, at times the frame edge type was not being updated correctly. This has been fixed.

    • Alpha-numeric order numbers are no longer working

  • The fields related to setting maximum prism for devices have been clarified on the device setup screens, and the help messages similarly clarified.

  • No labels