Brady Workstation - Data Automation Release Notes

Data Automation Release Notes

 

• When a channel is set up with multiple templates in a folder, the data file needs to specify the template, but not its extension. If the data file included graphic file paths and contained two or more instances of the template name without the extension, printing would fail for that data file. 
• If a data file included two rows with the same template name, and both rows included graphic file paths, the mapping would fail.

New Features and Enhancements

• Usability improvements to channel setup, especially mapping fields. 
  • A preview of the template is visible while mapping fields. 
  • A preview of the data table is visible while mapping fields. 
  • Drag and drop from the data table to the template to map fields. 
  • Automatically map data columns to template objects with the same name. 
• Use multiple Brady Workstation templates for a single channel. The data file specifies which template to use for each record. 
• Microsoft Excel files (.xls and .xlsx) can be used as the data file, as well as text files (.txt, .csv). 
• Mapped network drive letters can be used when specifying file and folder locations. 
• A setting for default number of copies has been added to the printer setup. 
• Supports templates with counters, including counters in a combined field. 
• Supports new BradyPrinter S3700 and M511 printers. 

Issues Fixed

• A tooltip has been added to the stop channel button for clarity.
• When specifying the template file, if you accidentally picked a data file, the error message was confusing. It is no longer possible to choose the wrong type of file when selecting a template. Also, the error message if there is a problem with the template file provides more useful information. 
• After mapping fields, if you reopened the mapping window it did not display the existing settings. 
• If a channel fails, the Data Automation service no longer stops. (300586, 304716, 308336.)
• If a watch folder located on a network drive got disconnected and reconnected, the software would not process files placed in that watch folder until the channel was manually stopped and restarted. 
• Some label supplies incorrectly produced an error message stating that it was the wrong supply. 

R 2.15 Issues Fixed – April 14, 2023

• When printing to A55-2-483 labels on a BradyPrinter A5500 flag printer, a message incorrectly advised that the wrong label supply was loaded in the printer. 
• The PR 600 Plus printer was missing from the list of printers.

R 2.14 – January 25, 2023

New Features and Enhancements

• Supports Codabar barcodes.
• Supports upcoming printers. 

Issues Fixed

• When generating two-sided labels, if the content on side 1 stayed the same and only side 2 changed, the software would print only the first label. 
• Mappings on an existing channel could not be revised. Attempting to do so resulted in an illegible error message.

 

R 2.13.1 Issues Fixed - October 5, 2022

• In some cases the software would display a message saying that the Brady Data Automation Windows service was not responding. The Brady Data Automation service could not be started, restarted, or resumed in Data Automation or in the Windows Services app.

New Features and Enhancements

• Supports Aztec barcodes.
• Windows Server 2016, 2019, and 2022 are supported operating systems. 
• Graphics quality adjustments set for placeholder graphics are used when importing graphics from a spreadsheet or database.

Issues Fixed

• The trial period began when the app was installed rather than when it was first used. 
• Barcodes set up in the template using the Combine Fields feature were not printed if they also had Fit to Frame set. Note that if a label has multiple barcodes with Fit to Frame set, all barcodes will resize to the dimensions of the first one. 
• A data file with a row beginning with the character # would not print and showed an error condition in the history. 
• If the template included a barcode set to Fit to Frame, the barcode would not print. Note that when restricting a barcode to a small size, if you assign a large data value to the barcode, the result may not be scannable when printed on a 300 dpi printer because the resolution is too small to capture the detail.