The database interfaces (MySQL, SQL, and Oracle) in v4.D.0.0 are not backwards compatible with previous versions. When using a database interface and are upgrading from v4.C.3.3 or prior, additional parameters will need to be added as outputs to the stored procedure.
The newly introduced parameters in v4.D.0.0 are:
- DwellTime: The amount of time to display the server response on the scanner screen (milliseconds). This parameter is required and non-nullable. Suggested value between 15000 and 90000, depending on implementation.
- AudibleKey: The name of the audible to play as configured on the RaPTr Scanner. A "Good" AudibleKey will play the sound file associated with the "Good" audible that is configured on RaPTr Scanner. AudibleKeys allow for the user to customize which sound is played and when instead of audibles being predicated on the PalletStatus response before. This parameter can be null.
- MetaDataDisplay: The metadata section of the RaPTr Scanner UI can be populated with HTML via the stored procedure by returning a string of HTML inside the MetaDataDisplay parameter. This parameter can be null.
Parameters for a MySQL Stored Procedure compatible with v4.D.0.0:
Parameters for a SQL Stored Procedure compatible with v4.D.0.0:
Parameters for an Oracle Stored Procedure compatible with v4.D.0.0: