SCS/Track 4.1.0-2 (June 25, 2018) – Support resources

June 25, 2018

SCS/Track™ 4.1.0-2

SCS/Track

There is an option in Ad Inquiry settings that allows a site to turn off renaming of files during the pickup process. This means that only the primary document, primary image and any supplemental files configured in the system will be renamed if their file names start with the source ad id.
The AdLauncher has recently added functionality to delete files that are not used by the primary InDesign document upon check-in. A new option is available to allow the user doing the check-in to skip cleanup of these files, which is especially useful if the work on the document is not complete.
Resolved a problem with markup notes. The red X in the upper right corner of a markup box either could not be seen due to scaling or the click area was not big enough. This was a scaling issue and typically only an issue in large full page ads. Issue reported by The Columbian (Vancouver, WA).
Resolved a problem when indexing custom fields. Custom fields that allowed multiple line entry would cause issues in the Ad Inquiry index and make the results returned by searches incorrect. Issue reported by Times-Shamrock (Scranton, PA).
Fixed a bug that would not properly escape double quotes when producing CAS reports. This would cause the fields on an export to a Spreadsheet to be incorrect - splitting fields across multiple lines. Issue reported by Times-Shamrock (Scranton, PA).
Fixed a bug that would display the expected size (in the actual vs expected size when doing size checks on the Ad Info page) differently than the actual size of the ad in the Ad Info summary section. Those sizes are now both correct and are identical. Issue reported by Hometown News (Ft. Pierce, FL).
Custom fields are now stored as untokenized fields in the index. This now allows custom fields to be sorted in the Ad Inquiry list. Issue reported by Times-Shamrock specifically for the Complexity field (Scranton, PA).
Searches would not always return correctly in Ad Inquiry due to a 32-bit vs 64-bit incompatibility. This issue has been resolved.