September 5, 2018
- A few modifications have been made to the way Gang Ad children and parents are treated with respect to routing ads and changing job statuses. These changes are outlined here:
- Routing a child ad out of a FINAL station directly using the CAS toolbar will likewise remove the parent ad from a FINAL station and route it to the same location as the child. This will change the parents status from Finished to In Progress.
- Sending a child ad that is at a FINAL station out to proof will likewise remove the parent ad from a FINAL station and route it to the same location as the child. This is typically a Proof Out station or something similar, although the parent ad will NOT actually be in a mark-up state. This will change the parent's status from Finished to In Progress.
- Checking out a child ad that is at a FINAL station will likewise remove the parent ad from a FINAL station and assign it to the same user that checked out the child ad. This will change the parent's status from Finished to In Progress.
Extended the CAS report limit to 260,000 records maximum. It is doubtful a report will ever hit that limit and more likely CAS will timeout before it even gets near that number of records. CAS reporting through the browser is not well suited for large record sets or reports that are time intensive, due to various timeout issues related to the browser. Alternate reporting options for these types of reports should be discussed with SCS.
There was a bug that prevented files from getting paginated properly if using the Paginate by Run option. This issue has been resolved. This was reported by Times-Shamrock (Scranton, PA) and currently only applies to this site.
If an ad was sent out to proof from the AdLauncher, it did not call the send proof email command. Therefore the ad would go out to proof but no email would be sent. This issue was reported by The Durango Herald (Durango, CO) and has been resolved. This fix requires an AdLauncher update.
When updating accounts as part of the order entry interface, via the SCS XML import, the salesperson on the imported ad is set as the default salesperson on that ad's account - only if it is a new account that does not currently exist in SCS/Track and the Ad Inquiry setting Do not update salespeople on Account from OE is set to FALSE. All existing accounts, whether they have a salesperson or not on record, remain unchanged.
Fixed an issue that would prevent the request to restore a user's forgotten password from working properly. The link emailed to the user to reset his password would give them an error for an expired or invalid session.
Improved email source formatting for email messages going out of SCS/Track (CAS) with respect to email addresses in the TO, CC, BCC and REPLY-TO fields. This formatting resolves issues with email blocking by certain providers.
Please sign in to leave a comment.