Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

to be released…

Info

Released on July 24, 2024

Reports

  • Fixed an issue where the Orders in Process Report had an incorrect watermark.

  • Jobs waiting for lenses - Added fields in system settings to control how deleted orders are placed in the report.

  • Time at Station Report - changeD changed the calculation of Time Elapsed to include holiday dates.

  • Volume Discount Report - is now accessible.

EOQ

See the EOQ guide /wiki/spaces/RXUN/pages/2805858305 for full details

  • Revised the forecasting algorithm to generate more useful min/max recommendations by better accounting for sales trends.

  • Revised the forecasting algorithm to generate more useful min/max recommendations when run partway through the month.

  • Revised the forecasting algorithm to generate more more useful min/max recommendations when using a short sales history.

  • Added the ability to view a stock item’s usage history from the EOQ screen.

  • Added the ability to view a stock item’s supply time from the EOQ screen.

  • Fixed an issue where the displayed Daily Forecast Usage was incorrect.

  • Added a new parameter to the calculation options called “Cap trend by % of real usage” that controls how far the forecast usage is allowed to deviate from the real usage this month. The new System setting “Cap EOQ trend forecast at % of real sales this month” under the Inventory tab sets the default value for this parameter.

  • Added a new parameter to the calculation options called “Generate DATA\EOQ-CALC.LOG” that creates a file that explains how the system computed the recommended min/max values for each item .

  • Min/Max fields are now editable in the form below the data grid as well as in the grid itself.

API

...

Added new key num-total-lenses to GET /wip/breakdown to count the number of lenses in progress

...

    • The count of jobs with at least one breakage entered for a particular breakage reason

    • The count of all lenses broken for a particular breakage reason

    Changed GET/v2/orders/{orderIdentifier}/pick to now return the lens bin for the right and left eye as well as the current job station code and description.

  • The get Wip 30 days API was not returning values for the current date. This has been resolved.

  • GET /rxsite/stylematerials no longer requires the parameters startstyle or endstyle. These are now optional.

  • Version 1 Add Order endpoint now accepts up to 1024 incoming trace points

  • Fixed an issue with Version 2 Add Order endpoint not accepting Z-points for the right eye

  • Version 1 Add Order endpoint now accepts up to 100 separate trace point lines, each line can hold multiple trace points separated by a “;”

System Settings

  • Inventory tab

    • Added new fields to control when deleted orders are included in the “Jobs waiting for lenses” report. Note that the fields are only active if the ORDER1 ORDERS1 flag “Enter reason code when deleting an order” is checked.

  • Orders1 tab

    • Added a new check box “Force calculated date wanted”. When checked this flag will disable the date wanted flag on an Rx order. It also causes the date-wanted, if supplied in a raw order file to be ignored.

  • Devices tab

    • Added field “A or NB tolerence for recalc”. This setting will check the existing A and B measurements against those of the new tracing. If either the A or the B are equal-to or greater than the tolerence entry, the order will be recalculated.

Pricing

  • When deleting a price list, in some cases, supporting price records were not always removed. This has been resolved.

  • When pricing ADDON’s, in some cases the ADDON price for a finished lenses was not being applied. This has been resolved.

Inventory

  • Lens picking

    • When partial pick is active and only one lens is picked, in some cases the pick flags for both lenses were being checked. This has been resolved.

Customer Service

...

Lens Style Configuration

  • Lens styles can now have default values for the following tags: ERDRUP / ERDRIN / ERSGUP / ERSGIN / ERNRUP / ERNRIN. The default style will be used for orders that do not have a specific value set for the tag. Stored values for these tags will not be cleared from the order when a job is outsourced as uncut.

Customer Service

  • When using F2/Clear Trace on the order entry screen, and changing to use box measurements, the calculated values for the brow, cheek, temple and nasal quadrants were not being zeroed out, causing those values to still impact the calculation of blanksize

Devices

  • OMA interface

    • Fix an issue with traces not auto-attaching

Place lenses into Bin

...

  • Fix search issue when selected key set to “Customer;Patient”. Sometimes the search would fail if a comma existed in the patient name.

  • When doing “View / Inventory” on an order, a new tab has been added to allow the viewing of the breakages and their data.

Orders Maintenance

  • When an order has a trace that uses an adjusted left trace, the “Adjusted Trace” text does not appear in the order’s trace box. It does appear if the right trace points are adjusted. This has been resolved.

  • Access to the date wanted flag is now controlled by a system setup variable in the “Orders1” tab.

Remote Order Processing

  • Change to now recognize labels FMFR and FRAM (previously were being saved as VCA overrides).

  • If a raw file supplies the date wanted ( _WDATE), the value is only used if the new flag “Force calculated date wanted” in the setup-Orders1 tab is unchecked. Otherwise it is ignored.

  • Added a new label _DISCOUNTCODE, can be used instead of _REMAKECODE. If both labels are sent in the raw file, only the _DISCOUNTCODE will be used.

Printer Routing

  • Printer routing rules now support up to 10 conditions per rule

  • Printer routing rules and orders now support up to 300 characters for the routing comment field, which also increases the size of the _ROUTER field

  • The routing rule description on the order (the value included by _ROUTEC) has been changed to support multiple lines

  • The routing rule tester screen now support order lookup by PO number

VCA Interface

  • The tag _FLFIT will now be accepted from UPL sessions and stored as a VCA override on the order.