Application Launcher

Area	AgilOne JIRA	Description of functionality after the fix
Actions	AGO-1054	To more easily enable recurring birthday campaigns AgilOne has developed a new Actions audience filter: ‘Days Until Next Birthday’. You can utilize the ‘Days Until Next Birthday’ filter to segment an audience based on whether their birthday is approaching or recently occurred.
Actions	AGO-10688	We are increasing AgilOne’s support for custom event types in Actions. A new Actions audience filter ‘Performed an event with product’ will allow Actions users to segment audiences based on whether they performed any type of event with a product. Previously only ‘Browsed a product’ was supported, but now Actions is capable of segmenting based on ‘Liked a product’ or ‘Signed up for more information about a product’, or any other custom use case a client may have.
Actions	AGO-10710	Removing content from an Actions campaign after it has already been executed once can cause future executions to fail. Therefore we are now disabiling the ability to remove content after a campaign has already been executed. You can still add new content for future executions. If you would like to delete existing content, please clone the campaign, and edit the new copy of the campaign.
Actions	AGO-10758	Today we are introducing a third new Actions audience filter: ‘Purchased a product in a category hierarchy’. This filter is an improvement on the existing ‘Purchased a product in a category’ filter. Previously when you wanted to filter on a parent category, you would have to manually select all child categories. For example, if you wanted to refine on ‘Tops’, you would have to manually pick the child most categories ‘Shirts’, ‘Sweaters’, ‘Tanks’, etc. With the new filter you only have to select ‘Tops’, and the refinement will automatically include all child categories, all the way down to the lowest level.
Actions	AGO-10828	In order to make the AgilOne application more self-documenting we have added many more information buttons within Actions. These buttons (designated by an ‘(i)’ icon) will either provide more details right in the application or link out to our thorough documentation portal in Zendesk. We hope to improve the quality of this documentation and add more documentation within the application going forward.
Actions, Metrics	AGO-10757	We’ve improved folder organization with Actions and Metrics. Folders are now alphabetically sorted making it easy to find them. We have also added a “Recent Folders” dialog which can be accessed via the clock” icon in the Folders area. This new dialog shows recently accessed folders for the user.
GDPR	AGO-10924	We have greatly improved the performance of our GDPR purge process to handle significantly larger customer lists (>250,000 customers at once). After testing our privacy API with some early adopters we found that many of our EU clients are more eager to purge ‘no longer relevant’ customers than we expeted. To accomodate these requests we have iterated upon and improved our GDPR purge workflow to handle very large customer lists.
Metrics: Cube Reports	AGO-10682	Cube Reports allow user to sort on measures and dimensions in a report result. We had a bug where this sort preference was not being reflected in charts. This has now been fixed, and this sort preference is also automatically saved when the report is saved.
Metrics: Cube Reports, Template Reports	AGO-10686	Empty/null values in the result grid of a report were being defaulted to “0” when charted. This was giving rise to some unexpected charting behavior. We’ve fixed it so that empty/null values are not charted in a data series instead of defaulting them to “0”.
Metrics: Cube Reports	AGO-6881	We’ve added the ability to re-order the measures/dimensions in a cube report via a drag/drop mechanism. Dimensions, however, cannot be moved from Rows to Columns/Filters area or vice-versa. The re-ordering mechanism will work within a specific area such as rows, columns or filters but not across them.
Metrics: Cube Reports, Template Reports	AGO-9792	Fixed various bugs related to “Stacked Column” charts. This chart type should now work as expected in various scenarios in Reports.
Metrics: Dashboards	AGO-10896	We experienced a bug where an incorrect timestamp was being displayed for “Report last run on” within Dashboards. We’ve now fixed it to show the correct timestamp.
Platform	AGO-1052	AgilOne’s default data promotion policy is ‘latest is greatest’, in other words the most recent data received is the most up to date. However, in some instances this paradigm breaks down: for example, the latest data can contain conflicting information, or higher quality and more thorough data may exist from an earlier source. Therefore, AgilOne has highly complex and advanced logic to decide which email address, mailling address, phone number, and some key customer attributes (e.g. first name, last name, gender, age, etc.) are promoted from the source data to the master customer in AgilOne. We have now made it easier for our clients to customize this logic based on their specific needs. Please speak with your Customer Succcess Manager if you would like to adjust how AgilOne chooses the winning name & gender, address, email, and phone number for each master customer. Sometimes the default promotion logic can be enhanced just by discussing which sources are highly reliable, and which sources are not.

1813 / 1815 / 1817 Release - 2018-05-29