v4.3.6

What's new

• We've made a handful of changes to support our forthcoming B2B module. These are architectural changes that facilitate the creation of plugin code, and have not added new functionality.
• Codes for campaign tracking and ROI tracking applied to the Get basket link in the abandoned cart EDC are now preserved and applied at their destination. [24ee0d7]
• We've added MFTF tests to test our dashboard and various report layouts.

Fixes

• Exclusion rules can now have conditions relating to product attribute sets.
• The imported / not imported filter on some of our report grids now functions as expected.
• We fixed a regression introduced in 4.3.4 that prevented new exclusion rules being saved.
• We now limit product short descriptions to 1000 characters as opposed to 250.
• We've resolved an issue with filtering the Manage Coupon Codes grid of a cart price rule. [fa88f72]

v4.3.5

Fixes

• We fixed an issue whereby redeeming EDC coupon codes generated in versions prior to 4.3.0, in version 4.3.4, caused a fatal error.

v4.3.4

What's new

• Individual coupons generated by the external dynamic endpoint can now have expiry dates independent from the sales rule expiry.
• We've improved our integration test coverage with two new test suites for the Importer and Contact syncs.
• We've added MFTF tests for the module when it is initially enabled.
• Contacts with an invalid store id are now prevented from breaking the sync when we retrieve a store name.
• Subscriber resubscribes that trigger an automated resubscribe email from Engagement Cloud now have the correct Contact Challenged response status marked against the matching importer row.
• Billing City was missing from the list of mappable fields in dotdigital > Data Mapping, and has now been added.
• We've added guest sync to our list of available dotdigital CLI methods.
• Our own custom serializer class is removed in favour of Magento's SerializerInterface.
• We've added some code to allow the retrieval of tier prices during catalog sync. This won’t affect this module's functionality; it supports our forthcoming B2B module.

Fixes

• We fixed a regression introduced in 4.3.1, which stopped some data fields from being captured when syncing customers, subscribers and guests.
• Deleting customers in the Magento admin was triggering two Contact_Delete rows in the importer table. This has been fixed.
• A single unsubscribed, hard bounced, or otherwise rejected contact could prevent a batch of campaign sends going out; this has been fixed.

v4.3.3

What’s new

• We've increased the sync limits for bulk imports into Engagement Cloud. The importer sync now imports up to 100 bulk items on each execution (25 of which can be for contacts), plus up to 100 single items.
• Additional data about the Magento installation is now sent to our sign up microsite when merchants register for Engagement Cloud Chat.
• When fetching a scoped date of birth, we now use store ID instead of website ID, in line with Magento core.

Bug fixes

• Merchants upgrading from 4.2.0 to 4.3.x now have an email_coupon_attribute table created as expected.
• We've fixed a bug in the Web Behavior Tracking script, triggered by empty product descriptions. [20d9a3d]
• We've fixed an error when fetching the API endpoint for a given store scope.

v4.1.0

Version 4.1.0 was bundled with Magento 2.3.4, and is tagged and documented here as a record. Merchants should upgrade to version 4.3.3 or higher.

What’s new

• We now provide Engagement Cloud Chat via a separate Magento module.
• We made some changes following a Magento architectural review: create() methods have been removed from class constructors, and we’ve added a virtual type to replace an empty block class.
• Changes to our log messages introduced in 3.4.1 have been reverted for now.
• email_catalog table columns changed in 3.4.2 have been restored as deprecated columns.
• Data entered into fieldsets designed to post data direct to Engagement Cloud (i.e. dynamic datafield and dynamic addressbook) will now not save any data to the database.
• When creating new data fields via Engagement Cloud > Data Mapping, we now show an error if your data field name is longer than 20 characters.
• The cross-site scripting fix for Marketing > Exclusion Rules, originally released in 4.0.0, has been refined so that form values are escaped at submission.

Bug fixes

• We now confirm a contact exists in Engagement Cloud before sending cartInsight data during the abandoned cart syncs for campaigns and program enrolment.

v4.3.2

Bug fixes

• We've fixed an issue which caused an order sync failure if an order contains a reference to a product which is no longer in the database. [8fe6ab1]

v4.3.1

What's new

• The classes responsible for syncing contacts and their data fields have been refactored to allow better extensibility by other dotdigital modules.
• We've added the ability to run the wishlist sync from the command line.
• Values entered when adding conditions to exclusion rules (Marketing > Exclusion Rules) are now validated both before and after submission.
• The success message displayed after subscriber sync is now more clearer.
• Two new commands are now available for the dotdigital CLI:
  • dotdigital:connector:enable can configure and enable a connection to Engagement Cloud.
  • dotdigital:connector:automap automaps data fields.
• A duplicated call to create the email_coupon_attribute table has been removed.
• We've added integration test coverage for the review sync.
• Engagement Cloud has been changed to dotdigital in various admin menus.
• In our upgrade schema script, we've removed a redundant method and added some exception handling when dropping indexes.
• We've made some improvements to bring our code into closer alignment with Magento coding standards.

Bug fixes

• Subscribers confirming their subscription, when Configuration > Customers > Newsletter > Need to Confirm is turned on) are now enrolled onto New Subscriber automations as expected. [98aa449]
• We've amended the data synced for store name in order sync, so that it matches the store view name sent with other sync types.
• We've prevented the date of birth (DOB) data field from syncing today's date if a Magento account holder leaves this field empty.
• Catalog sync now returns an empty array on failure. The previous void return was generating a warning that Magento logs as a critical error.
• We fixed a problem where Magento email templates became unmapped when our connector was installed.
• Exception handling has been added to show a warning if the Magento area code has already been set to a mismatching area when running dotdigital CLI commands.

Note

• Merchants on Magento Commerce should upgrade our Dotdigitalgroup_Enterprise module to 1.0.5 when upgrading to 4.3.1 of Dotdigitalgroup_Email, and re-run automap data fields.

v4.3.0

What’s new

• We now provide Engagement Cloud Chat via a separate Magento module. For upgrade instructions, see here.
• Merchants can now add Engagement Cloud's Web Behavior Tracking in the connector configuration.
• The data sent via our Web Behaviour Tracking script will now include product data and search data where available.
• The insight data schema for orders has changed. Configurable and bundle products no longer output as separate line items; instead, parent data is used to augment child products.
• We've added parent_id to catalog insight data schema.
• We've added a new tool to improve the way you create dynamic content links for coupon codes. Coupon codes can now be resent to customers if they have not yet been redeemed.
• We've added the ability to run the review sync from the command line.
• We've removed the 'Script version' field from Engagement Cloud > Configuration > Tracking. Merchants can still set the config key, if required, via CLI.
• If subscribers are deleted in Magento, we will now try to update Engagement Cloud only if subscriber sync is enabled.
• We've simplified subscriber sync by sourcing a store id from the store currently being synced, rather than from a Magento table.
• When creating new data fields via Engagement Cloud > Data Mapping, we now show an error if your data field name is longer than 20 characters.
• We have deprecated some of our External Dynamic Content URLs. We’ve added notes on how to replace these in your campaigns.
• Data entered into fieldsets designed to post data direct to Engagement Cloud (i.e. dynamic datafield and dynamic addressbook) will now not save any data to the database.
• We made some changes following a Magento architectural review: create() methods have been removed from class constructors, and we’ve added a virtual type to replace an empty block class.
• Changes to our log messages introduced in 3.4.1 have been reverted for now, in preparation for the Magento 2.3.4 patch release.
• email_catalog table columns changed in 3.4.2 have been restored as deprecated columns, prior to the 2.3.4 submission.
• We've added extra logic to our SMTP MessagePlugin to set the correct encoding on pre-assembled Zend messages.

Bug fixes

• We've fixed a bug affecting Engagement Cloud accounts in 'GMT minus' timezones, where customer birthdays would fall a day early.
• We fixed a problem with reviews being saved without a valid store id.
• A single suppressed contact could prevent a batch of abandoned cart email sends going out; this has now been fixed.

v4.2.0

Bug fixes

• We now confirm a contact exists in Engagement Cloud before sending cartInsight data during the abandoned cart syncs for campaigns and program enrolment.
• We fixed a problem where catalog sync was breaking while trying to load a non-existent parent product.
• Private marketing preferences are now hidden from the customer, even when nested inside a category.
• We’ve fixed a bug in the order sync that happened if the connector couldn't find the products for an order.

[Note: This is a patch release that would ordinarily be 4.0.1. However, we have submitted 4.1.0 to Magento for their bundled release in 2.3.4. The above changes are not included, and we must keep the whole 4.1.x line free for bundle release patches.]

v4.0.0

What’s new

• Our connector now ships with live chat functionality. Existing clients can enable chat via Engagement Cloud > Chat Settings to start using this new channel.
• Merchants can now sync additional campaigns from Engagement Cloud to Magento. This enables merchants to map custom templates to any transactional email in Magento.
• We’ve improved the way we set from name and from email values during transactional email sends. All versions of Magento 2, including 2.2.8, now send using the friendly from name that is set in Engagement Cloud, and that is stored in the email_template table. [a5fab58]
• Sale price and total price figures in cart insight data now include tax, in line with the prices presented in the basket EDC.

Bug fixes

• We’ve made a small change to our migration scripts to ensure that only wishlists with valid customers are migrated.
• We’ve written a workaround to handle duplicate rows in the email_contact_consent table.
• Products without website IDs now won't break the catalog sync.
• We’ve patched a potential cross-site scripting exploit in Marketing > Exclusion Rules.
• We’ve updated the way we set a refresh token in our OAuth Connect block, in order to fix a Magento integration test.
• Subscribers who unsubscribe will now be updated so that their SUBSCRIBER_STATUS data field in Engagement Cloud is set to 'Unsubscribed'.