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

Reports

The “Jobs Pending Completion Report”, which is printed after shipping orders, has been renamed “Shipped Orders Report”.  The format of the report has also changed to be similar to other new reports (version 7.08.01).

All reports, under the Reports tab, have been modified to prompt and print the date in the selected Date Format from System Settings (version 7.09.00).

Order Entry

When using a language other than English, some of the drop-down value translations exceeded the size on the Surfacing Options screen.  This has been corrected (version 7.08.01).

When creating an order and selecting a design that forced wrap parameters, the wrap flag was set.  If the design was changed to one that does not require wrap, the wrap flag was not accessible, so it could not be de-selected.  This has been corrected (version 7.08.01).

When an uncut order with no frame measurements was done for a traditional multi-focal (flat top, round seg), the "seg height" default for the left eye was not correctly calculated (version 7.09.00).

The "Force SRC blanks when AR requested" flag in the "Blank Selection" system settings flag needed to be ignored when glass blanks are processed by blank selection. (Version 7.09.00)

When processing IOT lenticular digital blanks, if the LNAM associated with the lens style was longer than 15 characters, the value entered in the lenticular bowl size in the F12/Surf screen was not being retained.  (Version 7.09.00)

In certain situations, blank selection could pick a finished lens for a job, but then give an error that the blank was too thick.  This has been corrected (version 7.09.00).

Statements and Payments

When entering payments and determining whether or not to automatically apply eligible discounts, the program was using the system date to determine whether the account was over-due, rather than using the payment date.  This affected payments that were entered with dates in the past (version 7.09.00).

If the option to show only recent transactions on the statement is checked (on the Statement tab in System Parameters), then the "start date" for transactions can be entered when printing the statement.  When this option is used:

  • all transactions that are not fully paid will be printed, no matter how old
  • all fully paid / reconciled transactions dated from the start date (inclusive) to the statement date (inclusive) will be printed

When the "Suppress paid trx before start date from statement" checkbox is NOT checked, then all transactions that had activity in the past 30 days will be printed on the statement (this would include invoices that were paid by a payment that was dated in the past 30 days).  This option results in longer statements, but that include more detail. (version 7.09.00).


Device Interfaces

A change has been made to the handling of the CLBS block in the Essilor LMS file to check the DO= label.  One file is created if DO=B, or two files if DO=R or DO=L is sent (version 7.08.01).

This change to create two files if separate DO=L and DO-R lines were sent, or one file with the eye extension as part of the label in the case of single-eye jobs, has been reversed in version 7.09.00.  This reverts the behaviour back to that before version 7.08.01. For the time being, Essilor Digital customers must use the PAIR mode interface in DEO (which has been the only supported model up until now).  Support for the SINGLE mode interface will be implemented at a future date (version 7.09.00).

When using the ESS table, if entries exist for AR=yes and AR=no, and TINT=N/A, the logic was not picking up the entries for LNAM, instead falling back to unable to select an LNAM code.  This has been corrected (version 7.08.01).

The Symbol LS2208 scanner was losing scans if you scanned trays too quickly.  This has been corrected (version 7.08.02).

Miscellaneous Changes

When entering the lens style in a VCA label table entry, if "zzzzzz" (lower-case") is entered, it will be automatically converted to "ZZZZZZ" (upper-case). (version 7.09.00).




  • No labels