Acquia CDP
1930 Release - 2019-08-06
| Area | AgilOne JIRA | Description of functionality after the fix |
|---|---|---|
| Campaigns+ | AGO-12223 | For Campaigns+ users, we patched a bug in the execution calendar that was preventing you from accessing the campaigns shown there. |
| Campaigns+ | AGO-12240 | Also for Campaigns+ users, we added a guardrail to prevent users from giving two variants the same name. This will ensure that you, and the AgilOne platform, can easily distinguish two separate variants downstream. |
| Platform | AGO-12260 | In Actions, we have added a guardrail to prevent users from being able to assign the same campaign two different execution schedules. Now when you schedule a campaign the application will check if a schedule already exists before allowing you to schedule. |
| Platform | AGO-9620 | We fixed a bug that was preventing the application from accurately calculating distance to store and closest store metrics when either a pop-up store switched zip codes, or a retail store closed. |
| Platform: Euromessage Input Connector | AGO-12271 | If your environment pulls data using AgilOne’s Euromessage Input Connector, we have implemented a performance improvement that reduces the number of API calls AgilOne fires when a campaign has zero events (e. g. send, open, click, etc.) to return. Previously we were attempting to pull all events for all campaigns, irregardless if the campaign had events to return or not. |
In addition, we have made several behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.
Acquia CDP