to be released
Order Entry
When entering an order using the OPC codes, a browse button has been added to allow the user to search through the stock database.
A new field has been added to the order for frame status. This is a drop-list type field that allows the user to select the frame status for the order. The field has been added under the salesman field. The “Routing” button has been moved to the top right of the order screen.
When entering lenses by OPC code, sometimes the RX info would not get filled in by the lens properties.
When pricing the addons, in some cases, the addon did not price, even if there was a price entered for it. This has been corrected.
Prism thinning prism from digital vendors (label PTPRVM in the LMS file) is now saved as the prism thinning amount for digital jobs. For both digital and toric jobs, when a remake is done on a job, the amount of prism thinning from the original job is retrieved and placed into the "Remake Prism Thinning Amount" field on the F12 screen from order entry. This allows the original prism for thinning to be used for the remake, or the lab can modify that as desired.
When deleting an order with breakage, extra inventory transactions were being created. This has been corrected.
After pressing the search button in the frame information block for the frame manufacturer, after the browse, the screen places the cursor in the Account # field instead of the frame manufacturer field. This has been corrected
Digital Designs
The custom _LTLVL, _LTDIA and _BLEND labels, previous allowed only for Crossbows and Essilor designs, may not be used for A2Vision designs as well. This allows use of the edge blending and custom blended design segment width features to be used with A2Vision as they are with Crossbows.
When using a digital calculator, where the calculator does not return SVAL in the LMS file, and the front curve of the blank is exactly 0.00, the calculation of SVAL and AVAL by Rx-Universe was incorrect.
Customer Service
The “Job Status” filter has a new selection “Unvalid” that will limit the order in the grid to unvalid jobs. Note that archived orders are not shown.
Statements
When printing a statement for a buying group member, we now print the original amount of each transaction. Since payments are made by the buying group, the member really should not have visibility to what transactions have been paid (or not) by the buying group. Showing only the original amount of each transaction allows the buying group member to see all information about their work, while respecting the privacy of the buying group transactions. .
Remote Orders
The remote order process has been modified to create orders that have a frame status of “Frame to follow” as “unvalid” orders. This is actually controlled by a new flag in the “System Settings/Roe” tab, “Make frame-to-follow jobs unvalid”.
The Eyefinity translation table (used for Eyefinity orders only) has been modified to expand the main Eyefinity code field to 40 characters. This now accommodates AR and Mirror coating descriptions which exceeded the previous limit (Eyefinity allows 30 characters for the description, in addition to the 2-character pricing code).
Remote and digital processors were still processing some files after the daily backup time was hit, due to not checking the time often enough in the programs.
Job History was not always being updated when a work ticket was printed for an “unvalid” order. This has been corrected.
API endpoints
A new endpoint to request a job to be canceled has been added.
A new endpoint to request the orders that have gone through a job station for a given date range.
Purchase Orders
When exporting Purchase Orders to Rx-xplore, if the PO had more than 3000 lines, it was causing an out-of-bounds error. This has been corrected.
A transaction history has been added to the Purchase Orders. It is accessed by right-clicking on a PO and selecting the PO History.
When releasing a PO, the user record is checked for the “Release authorization limit” before the PO is released.
Inventory
When receiving lens, either with or without a Purchase order, a new field has been added to the input screen for the vendor invoice number. This number is used when running the inventory transaction report and selecting the “Receive” transaction code. It allows the user to limit the transactions to a specific vendor invoice.
Devices
A received trace can now be saved as a pattern. New flags have been added to the “System settings / Device” tab, “Auto create saved pattern” and “Save pattern as calc only”. See the documentation in “Devices / Auto-attach trace” Auto-Attach Trace for information on how to use these new flags.