Application Launcher

Area	AgilOne JIRA	Description of functionality after the fix
Metrics	AGO-8855	Metrics cube reports can be sorted, and now the sorting will be saved along with the report if you hit “save”.
Metrics, Dashboards	AGO-9235	When on a dashboard, the application allows you to go to any of the reports that are displayed in the widgets, so you can edit them or dig deeper into each of those. This functionality was broken in our last release, so we fixed it.
Actions, SFTP Extracts	AGO-9280	We now support spaces in folder and file names.
General	AGO-9330	In the main navigation UI, we moved your username and tenant name under the ellipsis menu on the top right of the application. This has no impact on functionality, we just think it looks better that way.
Integrations	AGO-9330	AgilOne now integrates with EuroMessage (ESP), to pull the email activity of your customers (sends, opens, clicks, bounces, etc…).
Actions	AGO-9162, AGO-9362	We added a swath of lookups to our Actions filter, to make it easier to pick the right values. The list of filters that have been updated with this change is too long to list out here but you should notice the difference quickly !
Actions, Facebook integration	AGO-9369	With some recent changes in the Facebook API’s authentication flow, we realized that newly created accounts (or accounts that had not yet linked their Ad Account with AgilOne) were not authorizing our integration. We fixed this, and the Faebook integration now works well with any account.
Machine Learning Models	AGO-8969	We released a new version of our Likelihood to Buy model ! It will now produce more accurate results, and it will run faster than before.
Platform, Data feeds	AGO-8944, AGO-9012, AGO-9168, AGO-9169	We made various improvements to the logic we used to pick the best attributes for mastercustomer records from each of their child records (from different source systems). We also split the existing “Preferences” field into 4 different fields : DoNotEmail, DoNotCall, DoNotText, DoNotMail. Those represent the same type of “optin/optout” tracking for each customer, with the same allowed values, but splitting them makes it easier to manage complex use cases when merging records from different source systems. It also allows a much more granular control over how each customer’s preferences are surfaced at the mastercustomer level after deduping. The documentation for the standard Customer feed has been updated to reflect this change. Along with that change, we are deprecating the “Preferences” field in the standard feed. However, you do not need to change your existing feeds, please review the feed documentation for more details.
Actions	AGO-9204, AGO-9043	We made various optimizations to our query generation, so that Actions campaigns become much faster & require less resources to execute. This should ensure that both audience counts and campaigns run faster for you on a daily basis.

1731 Release - 2017-08-14