Application Launcher

Area	AgilOne JIRA	Description of functionality after the fix
Actions	AGO-9704	We updated the lookup on the filter AOV to be dynamic instead of static (like it used to be). This way, any configuration that was done on the AOV bucketization for your tenant will automatically be reflected there.
Actions	AGO-9684	We improved the way to select the PrimaryPhone when we dedupe customers together. Now, it will pick, in order of priority (and in the case where there are multiple choices) : Non-null phone numbers… …that are not opted-out… …that are associated with the customer record that placed the most recent order… …that were updated the most recently. Selecting all the phone records that match each rule, the algorithm will pick the latest survivor (the one that fit the best those rules, in the order presented above).
Platform	AGO-9683	For clients that have a tenant configured to compute customer summaries by including only Demand/Cancel/Returned transaction items (for instance, or other similar configuration), we fixed an issue where some of the computations were not honoring the configuration (they were still computing only on Shipped/Returned items).
360 Profiles, Dashboards, Actions	AGO-9680, AGO-9678, AGO-9490, AGO-9489, AGO-9465, AGO-9334	Small UI improvements.
Metrics, Cube reports	AGO-9638	We added an option in the drop-down menu (on the reports listing page), called “Report Details” : this will show you all the measures, dimensions and filters used by your report without trying to load it (thus, saving a lot of time). It enables you to quickly find the report you were looking for.
Actions	AGO-9609	We removed the Actions filters that were using “Days since” (full list below). They were actually redundant with other existing filters that offered more capabilities, and it was creating some confusion (and they were not being used either). The full list of filters that were removed (and their corresponding existing filter, or replacement) is the following : Days since last order : please use Last Transaction Date instead (and use “in the last”, or “in the range of” as comparator if you want to enter a number of days, for instance) Days since first order : please use First Transaction Date instead (and use “in the last”, or “in the range of” as comparator if you want to enter a number of days, for instance) Days since last web login : please use Last Web Login Date instead (and use “in the last”, or “in the range of” as comparator if you want to enter a number of days, for instance) Days since first web login : please use First Web Login Date instead (and use “in the last”, or “in the range of” as comparator if you want to enter a number of days, for instance)
Actions, Platform, NCOA	AGO-9579	This applies only to clients that have NCOA enabled for their tenant (US and Canada only) We are now surfacing NCOA processing attributes as part of Actions filters (under the “Customer Summary” folder in Audience filters). This enables you to easily select all customers who have recently been processed through NCOA, and select only the ones who moved recently (for instance), or by move type as well. Here are the new filters, and their capabilities : NCOADateUpdate : this is the date at which the record last went through NCOA processing. This is currently in a UNIX epoch format (e. g. “1507060487001”), but we will soon release a “human-readable” translation (e.g. YYYYMMDD format) of that filter. MoveType : this is the type of move that was registered within the USPS NCOA database. The possible values are : I for Individual Match, F for Family Match, B for Business Name Match. MoveDate : this is the date at which the move was registered with USPS in the NCOA database. This is in the format “YYYYMM”, e.g. “201401” is a move that was registered on January 2014 (the actual move could have happened earlier or later, the NCOA database cannot provide that information).
Actions	AGO-9446	We retired an unused filter (“Transaction with total”). This filter was redundant with “Spent more than [amount] in a timeframe”. If you would like to leverage this new filter, please reach out to your AgilOne team and we will configure it for you.

1739 Release - 2017-09-28