Versions Compared

Key

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

...

System Settings

  • New fields have been added to the Work Tickets tab in System settings to allow integration with SatisLoh E-Ticket

Job Stations

  • A new tab has been added for the SatisLoh E-Ticket for the E-Ticket specific information.

Device Parameters

  • OMA device maintenance screens. Added a new field in the “OTHER2” tab. “VCA communication delay (ms)”. This field allow for an entry from 0 to 6000 milliseconds. It will add a delay when receiving a request from a device and then the processing of the request.

  • VCA device

    • Change to not do a recalc on auto attach if the order is digital and outsourced (“$OUTSOURCED” in the LDPATH field)

    • The GPRVA and GPRVM labels have been enhanced to send the value returned from an uploading device for all session types except the surface blocker. Previous to this, the uploaded value would only be sent if the session type was for a generator. There is an override that allows the ART blocker to received the uploaded value also.

    • Under certain circumstances, when auto-attaching a trace, the recalc was not always working. This has been fixed.

E-Ticket

The ability to communicate with the SatisLoh E-Ticket system (for electronic job tags) has been added.

Orders

  • Fixed issue with base curve chart selection. If you have a “Base Curve Chart” that also has a specific manufacturer and pre-treatment, this chart was not being used when selecting the best BASE for the order. This has been fixed.

  • Fixed issue with the “Optimum Base Curve”, the displayed curve was not being update right away when you forced a manufacturer for the order. You would have to tab through the cylinder field before it would update the “Optimum Base Curve” on the screen. This has been fixed.

  • In some cases, the selection of the Optimum base curve would fail resulting in a “No optimum base Curve found” message. This has been resolved.

  • When checking for duplicate PO numbers orders that are pending completion will now be treated as inactive

  • Remote orders and API endpoints were not correctly validating cylinder axis based on the system setting whether to allow cylinder axis of 0 or not. This has been corrected.

...