2017-02-07 (Sprint 12)

Release Date: February 7, 2017

This release contains several defect fixes and backend enhancements.

Campaign Designer – Duplicate Mailing Instances

There was a defect that caused duplicate mailing instances in a campaign’s mailings. This has been resolved – all mailings now send correctly and display correctly in the campaign reports.

Campaigns – Updated Code

There was a defect that prevented users from editing the Mailing step in a copied campaign. This has been resolved.

Data Input Form Updates

We have removed the “Not Specified” option from demographic fields in event forms, data input forms, and landing pages. It now displays as a blank option that cannot be selected. Similarly, if users choose to use radio buttons, “Not Specified” is no longer created as an automatic option. It does not create a blank radio button.

Higher Logic Syncing

Higher Logic target groups were not retaining their counts after syncing and were reverting to zero. This has been resolved. This was previously deployed to production as a hotfix, and this change incorporates the updated stored procedure into the main code.

Online Version Access

Many clients noted that they were blocked from viewing online versions of mailings. To resolve this, we’ve improved the way we receive online version requests by using Netscaler. We have removed the code that checks for online versions because these checks were causing access to be blocked.

Send Time Optimization – Resend Error

Some clients encountered an error when clicking Resend to Soft Bounces while using Send Time Optimization (STO). The error cancelled all mailings from any future batches that would be sent via STO. To prevent this from occurring, there is new code that sends the subsequent mailings when using STO. Note that this also affects distributed mailings.

Web Tracking Sessions

We’ve improved our web tracking logic to better track users across domains and subdomains. We updated the code that processes incoming data. Previously, it would process one domain/subdomain at a time, causing different page visits within the same session to register as multiple sessions. Now, it looks at all domain/subdomains that are connected to one brand and then processes that data set as one unit. If a user crosses domains/subdomains, the session stays the same for the user and in our database.