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

to be released ….

Reports

  • Orders Production Report - Breakage

    • Fixed an issue where the Lenses Shipped Today/Frames Shipped Today counts sometimes included orders that were shipped on previous days.

    • If using Breakage Sub Codes the Department column will now include the department description

  • ViStar Production Statistics Report

    • Fixed an issue where DAYS/JOB column was calculated incorrectly when running the report for a single customer

    • Fixed an issue where the total breakages could be calculate wrong if there were more than 50 breakages reasons included on the report

    • Fixed an issue where the report would lock up when trying to count orders with different materials for each lens

    • The Lens Breakage table will now be in alphabetical order

    • If using Breakage Subcodes the Lens Breakage table will now group breakages under “Department Description - Reason Description”, omitting the Shift and Position.

  • When XSL templates are used for a report, if the report size is large, it would give a message and exit the report. This has been enhanced to give the user a choice to try and print it, or abandonne the report.

Printer Routing

  • Added new conditions (see Setting Up Routing Rules - Rx-Universe - Confluence (atlassian.net))

    • Add <=

    • |Cylinder| <=

    • Prism <=

    • FRNT >=

    • FRNT <=

    • A <=

    • A >=

    • B <=

    • B <=

    • CRIB <=

    • CRIB >=

    • ELLH <=

    • ELLH >=

    • GBASE <=

    • GBASE >=

    • GCROS <=

    • GCROS >=

    • _LOHPRVM >=

    • _LOHPRVM <=

    • BACK >=

    • BACK <=

    • BCTHK >=

    • BCTHK <=

    • CTHNP >=

    • CTHNP <=

    • Has Trace

    • Has No Trace

  • Renamed some conditions

    • “Mat Type =” is now “Material Type =”

    • “Style Group =” is now “Lens Style Group =”

    • “Is Priority” is now “Is Hot Job”

    • “Stock Num =” is now “Lens Stock Num =”

    • “N/A” is now “(none)”

  • Changed the order of the condition dropdown to put related conditions closer together

Inventory

  • Lens adjustments

    • When adjusting down, modified to not allow the on-hand quantity go below the in-process quantity.

  • Lens picking

    • If partial picking is active, the program always required a left lens be entered

API

  • Fixed an issue where calling GET /rxsite/stockfinished with a larger value than the total number of available records would generate invalid JSON.

  • GET /rxsite/stockfinished now accepts an optional parameter called lastChangedDate that allows you to only retrieve lenses changed since a particular date.

  • Fixed an issue with GET /orders/cust where calling the endpoint with the designated VSP account included deleted orders and could list orders more than once.

  • Fixed an issue where job status was not being returned for completed orders completed in a previous day

User defined documents

This includes the XML work tickets, the AR Envelope, the Trace-only Work ticket and the Additional documents.

The printing of the user defined documents will now check the associated switches to determine what paper size will be sent to the printer. It will be either letter size, A4 size or get the size from the resulting PDF.

Device Parameters

Added a new flag in the Edger tab for OMA device. The flag allows the LDPRVM label to be overridden by the PRVM value when an OMA device communicates with RxUniverse.

Customer Service

A new search key has been added to the “Select Key” field. It is called “Last Modified YYYYMMDD;hhmm”. This new key will allow the user to list the orders based on the last date/ time they were modified. The new last date time field can be viewed in the “View Order Flags” also.

The key search by patient name is no longer case sensitive.

Order Entry

Under certain conditions, modifying an order could create extra traces that were not valid.

Worktickets

Remote Orders

When a frame-to-follow order was received, if there was a frame from frame inventory selected for the order, the tracing used on the frame inventory was not being used if a default trace was available.

  • No labels