Application Launcher

Area	AgilOne JIRA	Description of functionality after the fix
Platform, Actions, Metrics, 360 Profiles	AGO-8543	We identified and fixed a bug in the way PrimaryStore was computed.
Platform	AGO-8565	While the platform supported UTF-8 Unicode characters, validation/ standardization elements of our Data Quality Engine would try to convert such characters back to Latin characters. We fixed that and fully support international characters (e.g. mandarin, turkish, etc…)
Platform	AGO-8531, AGO-8773	We found a corner case where, if the Last Name of a customer was NULL and the First Name was not NULL, the validation & genrization code would output that record with a Last Name containing the First Name, a NULL First Name and a NULL Gender. This had a very small impact (small number of such records), yet the incorrect Gender could lead to missing certain customers when executing campaigns. We fixed this and our validation component now outputs the expected values, as well as the proper genderization.
Platform	AGO-8659, AGO-8698	We now support exporting data into txt, csv, tsv or other similar extensions via our SFTP and S3 connectors. Note that the actual data is still in a csv-like format (delimiter and separator being defined in the connector by your AgilOne team).
Actions	AGO-8755	We exposed the DPV Confirmation results that we get from USPS for US addresses in Actions as a filter and content for your campaigns. The new filter is called “DPV Confirmed”, and can take the values “Y” (when the address is DPV confirmed) and “N” (when the address is not certified).
Actions	AGO-8766, AGO-8791	We made various performance optimizations in the way the Actions filters and their underlying queries work.
Actions	AGO-8605	The Actions campaign listing page now displays at a glance whether the campaign is scheduled as well as its last execution status and date/ time. The schedule will display “-” if no schedule exists on that campaign (either already went through that schedule, or never scheduled) , “ONCE” if it is scheduled to run once in the future, “DAILY”/”WEEKLY”/ “MONTHLY” based on the frequency of the schedule. The Last Execution Status will display the current/latest status of the campaign using icons (for failed, running, succeeded statuses), and the date/time is the date/time at which the campaign entered that status (e.g. the execution time if the campaign is currently running, or the processing end date/time if the campaign succeeded). For our SendGrid integration : note that this execution status and date/time does not cover any test that was run through the “Test Email” functionality.

1721 Release - 2017-05-25