Application Launcher

Area	AgilOne JIRA	Description of functionality after the fix
Actions	AGO-8639	The filters “Placed first order” and “Placed last order” were not working correctly : they were looking at the first/last transactions of customers prior to deduping, instead of considering the master customer profile (ie after deduping). We had retired those filters while correcting this behavior, and we are slowly enabling those filters again for specific tenants (please contact our AgilOne CSM if you are looking to use those filters).
Actions	AGO-9508, AGO-9249	Similar to the issue above, the content model for “Last Abandoned Products” was looking at the wrong granularity (checking individual customers, instead of looking at their aggregated mastercustomer profile after deduping). This has been fixed.
Actions	AGO-9493	When selecting an audience for your campaign, the “IN” operator was not working when the values had single quotes in them. This bug was fixed, and everything is now working as expected.
Metrics, Dashboards	AGO-9495	Selecting valid reports to add to your Dashboards became easier : the search UI now only displays reports that have run at least once (reports that have never run cannot be added to a Dashboard).
360 Profile	AGO-9540	The 360 Profiles Journey search functionality was unable to retrieve results whenever multiple words were entered in the Event Type field. This is now working as expected.
Actions	AGO-9627	We added a new functionality to Actions campaigns : now you can switch your campaign to another execution channel (e.g. change a SendGrid campaign to push to SFTP instead). This change i very interesting for cases like testing/reviewing the audience and content of your campaign before executing the “real” campaign : simply copy your future campaign, change the channel on the copy to point to the right execution channel (e.g. SFTP), execute the copy and review. To switch the channel, simply click on the “…” menu of your campaign in the campaign listing page, then select “Change channel (beta)”. This is a beta functionality, so you should be careful not to blindly execute a “real” campaign if you just changed its channel : in particular, always review the “Destination” step and the “Content” step to ensure that you are still sending the expected content to the right place (e.g. Facebook campaigns do not send content, and you also want to make sure the campaign goes to the right Ad Account before sending, etc…). If you encounter any issue with this functionality, please contact your AgilOne CSM and let her/him know your feedback.

1737 Release - 2017-09-15