Technical Items
Introduction
These notes are intended for people with a good knowledge of SQL and also a good understanding of the TransLution database. The information is not intended for general users of the software. Each section listed below is covered in detail.
It is often useful to know what a status line means for a specific scanner job or sales order. This section describes each of these. Sometimes a line in a certain status will not be visible from the front end but it can of course still be seen in the database.
This describes how to view errors that occurred with EazyScan posts, how to track that information back to what was scanned on the scanner and also, how to track successful posts through to Syspro. Some of the details covered here only exist in Version 3.06 and later.
It may be useful to know where layout data is stored. It is not recommended to edit this data directly in the database but if the results are not what is expected this information could prove useful
TransLution relies on a piece of software called commserver to manage communication with scales. This covers how to configure commserver and requires and understanding of serial communications.
This is a table that logs which function area or workflow was last selected by a user on a given EazyTouch device. This is useful when determining which function area is active if banners are required to show function area specific information.
This section deals with setting up TransLution to send emails to users on errors.
This table logs all operator entry or scanned data that was invalid and resulted in an error to the user.
TL Selector Overlay Audit Trail
Here we cover how the Audit trail for the TL selector works and how to determine which rows have been changed and how to use that data in a report or a label.
General Grid Overlay Audit Trail
Here we cover how the Audit trail for the General Grid works and how to determine which rows have been changed and how to use that data in a report or a label.