...
Info |
---|
Released on June 26, 2024 |
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.
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.
Fix issue with some deleted orders having a zero value for the last modified date.
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
XML Exports
Order exports will now include the most recently entered non-reversed breakage event.
RXXORDD is a program that exports deleted orders to be used by Rx-Reports. RXXORDD used to export all deleted orders. It has been changed to now allow a date range and a customer range. The date range is based off of a new key on the order file - Last Modified Date, When RXXORDD is called from the Day End, the From Date will be the date of the last day end, and the To Date will be today’s date (or whatever date the user enters). The customer range will be First to Last. When RXXORDD is called from Run Specific program, the user can enter whatever date and customer range they want.
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 orderAdd 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
Added new key num-total-lenses to GET /wip/breakdown to count the number of lenses in progress
Added new V1 endpoint GET breakages/today that returns breakage information since the last scheduled day-end
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
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.
View file name PDPRINTManual.pdf 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.
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.
...
When doing a lens cycle count, if a lens in the count range was locked by another Rx-Universe process during the freeze, not all lenses desired would be included in the freeze count range. This has been corrected.
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.
The fields related to setting maximum prism for devices have been clarified on the device setup screens, and the help messages similarly clarified.
Reports
Fixed an issue where the Orders in Process Report had an incorrect watermark.
Place lenses into Bin
When an order was assigned a bin, the process was not saving the bin with the order. This has been resolved.