Skip to main content

SCS/Track 3.6.0-0 (January 3, 2017)

Michael Grabowski
Updated

January 3, 2017

AdLauncher™ 3.6.0-0

Community Advertising Services™ 3.6.0-0

Classified Order Entry™ 3.6.0-0

SCS/Track™ 3.6.0-0

 

Community Advertising Services (CAS)

  • All references in the CAS URL that would use adtrack or admax as the application name have been changed to track or oe, respectively. Using URLs with names starting with ad would cause ad blockers to prevent access to CAS pages. This was especially troublesome when customers outside of the newspaper would access CAS for proofing or viewing their ads. Any sites using adtrack in their base URL should consider using an alternate URL if they have customers experiencing problems accessing the system.

  • Improved the way cookies are handled within CAS. Previously they would not always get set correctly causing unexpected behavior. The most notable place where this could be seen was within Ad Submit causing CAS to hang during the submission process or files to not get uploaded.

  • Custom forms used by Ad Submit, Ad Create, Classified Order Entry and CAS Reports now support embedding static images.

  • Custom forms now properly preserve the checked value of checkbox fields, previously those values would be lost.

Classified Order Entry

  • Classified Order Entry now supports the ability to upload multiple images in the context of web based ads. These files are uploaded into SCS/Track and require that application to use this feature. Once the order entry process is finished and the classified ad is approved and sent into SCS/Track it can be configured to receive the ad, do an automated pickup bringing the files from the upload into the new ad, paginate those files to some location and marking that ad as finished. The preview image that appears in SCS/Track for that ad is the composed print image for that ad. The option Allow Web Content in the prebuy configuration allows this behavior to be configured on the package level. If the web text field is added to the custom classified entry form, that text is also stored in the ad folder in SCS/Track.

  • All fields, including custom fields, that are part of the classified order entry form are passed into AdMAX. If that information is passed to SCS/Track like in the above case of a web based ad, those fields are stored in a JSON file in the ad folder.

  • There are now three options for scheduling an ad in classified order entry: None, Start Date or Manual Entry. These options are set on the product level when configuring the prebuy in AdMAX.

  • None: If all products within a prebuy have this set as a scheduling type, the behavior of classified order entry previous to this enhancement is preserved. A start date is selected for the entire package, the number of runs in each product are determined at setup time and cannot be decided by the user except to add multiple buys of the same products and schedules. Certain products if they are optional may be removed from the list of scheduled products.

  • Start Date: If any of the products within a prebuy have this set as a scheduling type, the drop-down for the start date appears next to this product. If a start date is selected and there are products in the package that use the None option, those products will automatically get the same start date as the earliest start date selected here. Certain products if they are optional may be removed from the list of scheduled products.

  • Manual: If any of the products within a prebuy have this set as a scheduling type, the drop-down with the start date next to this product is disabled, but a calendar icon appears. Clicking on the calendar icon opens a calendar and allows the user to select any desired run dates. The drop-down with the start date is filled in with the earliest selected run date for that product. Certain products if they are optional may be removed from the list of scheduled products.

  • Ad formats now support two types, a standard print format and a web format. The web ad format should be written in HTML and can use the same tagging and template setup that the print ads currently use.

  • A Show Web Preview option has been added on the prebuy level, if this is set the composed HTML output configured from ad formats appears on the page.

  • A Show Print Preview option has been added on the prebuy level, if this is set the composed print output configured from ad formats appears on the page. This is the preview that has always appeared in classified order entry, but now it may be disabled.

  • Fixed a bug when saving values in classified order entry that may have caused strange behavior or loss of certain fields or ad text when going through the process.

  • Prebuy groups are managed through the translation tables allowing for short and long (HTML web description) descriptions. New custom text is also available for the Prebuy Groups tab. All tabs in classified order entry are now customizable using CSS. A new option to require a user to login before continuing with the order entry process has been added in classified order entry settings called Require Login Before Taking a Classified Ad. If that flag is set, the user is prompted to create an account or login when first arriving on the classified order entry page.

  • The prebuy group and classified code can be passed through the URL to the classified order entry page allowing a site the option to bypass the prebuy group tab or the prebuy group and classification tab.

AdLauncher

  • The native look and feel of the AdLauncher has been improved on both Windows and Macs.

  • Increasing the size of the AdLauncher window grows the ad list, not the log area.

  • Columns can be reordered and column values are sortable. The size and coordinates of the window, order of the columns and sort order of the column values are all preserved when the AdLauncher is closed and then reopened. This information is preserved per workstation not by user.

  • When checking out an ad already checked out by another user the message contains the user's name that has the ad checked out, not the tag {USERID}.

  • A bug was fixed that prevented logging into the AdLauncher if a password contained special characters and the preferences (for the local AdLauncher) are accessible and can be changed even if the user cannot log in.

SCS/Track

  • The page group id in SCS/Track now supports a value from 1 to 999. Higher page group values of 100 or more are not used by Layout-8000 and can be used to indicate gang ads or special pagination conditions in SCS/Track.

  • Certain touch devices would not properly close the popup that would display ad information in Ad Inquiry when clicking on an order number. The popup would remain when returning to Ad Inquiry. It is now closed.

  • Certain touch devices did not allow the user to enter into the title or comments field on the ad proofing and markup page - this has been improved to work more consistently across all types of devices.

  • There is a new option in the Source table called Pickup From Submission. If that value is set the model ad id is treated as the confirmation number and the pickup will be done from a submission instead of another ad. This is used in conjunction with the changes to Classified Order Entry detailed early in these release notes.

  • The Vision Data interface now maps the proof_contact_name, proof_contact_phone and proof_contact_email elements. If a value is passed in the proof_contact_name that is used instead of the base customer name for the contact info. If a value is passed in the proof_contact_phone that is used instead of the base telephone element. The proof_contact_email now sets the proof email in SCS/Track, which previous to this version could not be passed via the Vision Data interface. 

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk