Valid for Sitecore
7.5
Release Notes
The latest release information about the E-mail Campaign Manager module.
Some of the issues described on this page contain internal reference numbers. You can use these reference numbers when communicating with Sitecore about a particular issue or feature.
1. Release History
October 14, 2014
The E-mail Campaign Manager 2.2 rev.141007 is released.
Tested with Sitecore CMS 7.5 rev.141003.
Compatibility
This version of the module only runs on Sitecore 7.5 or later.
Change log.
New features
- The ability to pause and resume A/B-testing
- The new public ECM API for main ECM functionality
- MVC message support by ECM
Important changes
- ECM is fully supported by Sitecore CMS 7.5.
- Dispatch has been optimized to work with Sitecore CMS 7.5.
- A separate package for installing ECM on a CD server has been introduced to replace manual installation.
- ECM reports have been optimized for Sitecore 7.5:
- The reports use aggregated data instead of raw data
- All the queries are now stored in items and can be easily customized
- All items with queries are stored under /sitecore/system/Modules/E-mail Campaign Manager/System/Queries
- The ability to send a triggered message from the CD-server in distributed environments has been added.
- The Design Importer module is not supported by Sitecore CMS 7.5 and thus can't be used with ECM 2.2.
- The Recipient Queued and Send in Progress states have been removed from the engagement plan and moved to a separate ECM storage (MongoDB collection by default).
Issues resolved
- When you deactivated a triggered message, which had been sent at least once, you would get the following error: "The campaign start date for this message is not set". This has been fixed. (4404)
- The incorrect unsubscribed date in the unsubscribed details report appeared after the recipient was unsubscribed. This has been fixed. (4156)
- No error message was displayed when you did not select A/B Variants to send in quick test. This has been fixed. (5437)
- No error message was displayed when you tried to start an AB test with no A/B Variants selected. This has been fixed. (5438)
- No error message was displayed when you tried to initiate an email preview with no variants selected. This has been fixed. (5439)
- No error message was displayed when you tried to initiate a spam check with no variants selected. This has been fixed. (5440)
- The dates on the Email Preview and Spam Check tabs had different formats. This has been fixed. (4634)
- There was a wrong date and time format in the Message Info panel as per the user settings in User Manager - Regional ISO Code. This has been fixed. Now the date and time format is taken from the user settings. (3750)
- The system showed three different error messages when the sacEndpoint was incorrect. This has been fixed. Now only displays one error message. (4651)
- The Email Preview and Spam check tabs were not refreshed after switching the language. This has been fixed. (4676)
- The A/B Variants buttons on the Email Preview and Spam Check tabs did not save the state and it was always selected when the tab was refreshed. This has been fixed. (4888)
- An unexpected message appeared when Copy to draft message from Top 10 best messages list command was used. This has been fixed. (4363)
- The invalid view state message appeared during large dispatches. This has been fixed. (4706)
- An empty row appeared in the Insert Token dialog when an existing token was deleted. This has been fixed. (5533)
- The Search Messages list, displayed the wrong dispatch time. This has been fixed. (5624)
- The "Unsubscribe from all" link was not present when the message content language was changed. This has been fixed. (5819)
- The “Wait operation timed out” exception appeared on the ECM user interface and in the logs. This has been fixed. (5860)
- The incorrect time was displayed under the Message Info after a message dispatch had been scheduled. This has been fixed. (5887)
- The error message: "selected time and date is in the past" was displayed incorrectly. This has been fixed. (5888)
- The Search function did not work for the special symbols: ' and ". This has been fixed. (5983)
- If there was a live user session, there were problems enrolling a contact to an engagement plan during dispatch. This has been fixed. (6022)
- In some cases ECM would send more emails than the expected number. This has been fixed. (6026)
- ECM 2 did not support the Danish language. This has been fixed. (385938)
- The CD/CM environment setup was not generally stable for handling email events. This has been fixed. (6294)
- Aggregation for the CD/CM environment might not work correctly. This has been fixed. (5842)
- Aggregation and reports might not work correctly if two messages are opened in one session with the same link to the same goal. This has been fixed. (6291)
- Internal and external links might not open if you use different actions. This has been fixed. (6293)
- An exception appeared in the log file after opening a message. This has been fixed. (5825)
- The dispatch process switched to the Pause state on a Dedicated environment. This has been fixed. (6317)
- One of dedicated servers wasn't involved in the dispatch process. This has been fixed. (6319)
- ECM now generates a valid UserAgent header for previewing and dispatching e-mail messages. ECM therefore works correctly when strict URL rewriting rules are configured for the Sitecore solution. (405843, 62778)
2. Known issues
This page contains the known issues that were found in ECM 2.2.
- Internal and external links may not work correctly when using other ports than 80. (6388)
Workaround:
The Base URL may be changed from the Content Editor at /sitecore/content/Home/Email Campaign. Although the error message still appears, the links work correctly. - The aggregation doesn't work correctly when using customProvider="mongo". (6607)
Workaround:
Install the update patch for ECM 2.2. To download the patch, visit the ECM 2.2 Downloads page. - ECM 2.2 does not track email opens for messages sent using ECM 2.1 and opened after upgrading to ECM 2.2. (424554)
Workaround:
1. Download the RegisterEmailOpened.html file.
2. Put this file into the /sitecore modules/shell/EmailCampaign/ folder.