1823 Release - 2018-06-28 | Acquia Product Documentation

Area	AgilOne JIRA	Description of functionality after the fix
Platform	AGO-10839	Recently some clients who have householding logic enabled have noticed that some transactions are improperly marked as anonymous transactions instead of being properly assigned a master customer. This has been rectified so that all transaction records are properly assigned the correct master customer. If you do not have houeholding logic enabled, then you were not susceptible to this issue.
Actions	AGO-10792	Actions users often need to send an Actions campaign in a fixed (i.e. previously determined) data format to a downstream destination, with very little input from AgilOne on the required format/content. For example, many email service providers (ESP) require fixed data formats, including specific content columns in a specific order. Now when an Actions user selects the destination table within the destination tab of the campaign workflow, they can click the schema information button (i) to see what data structure is required for the destination table they have selected. No more guessing or memorizing what content is required for each destination.
Actions	AGO-10927	Continuing our effort to make the AgilOne application more self documenting and user friendly, we have added many new information buttons (i) throughout the Actions campaign workflow. In the future we hope to add more documentation within Metrics and 360 as well! Please email product@agilone.com if you ever spot any out of date documentation.
Actions & Metrics	AGO-10982	Within Actions and Metrics you can now search for campaigns or reports by their unique resource identifier. To perform this search, within the Actions or Metrics search bar, please enter ‘##’ and then the unique identifier of the campaign or report you are referencing, e.g. ##3215 will return campaign or report 3215.

Area	AgilOne JIRA	Description of functionality after the fix
Platform	AGO-10839	Recently some clients who have householding logic enabled have noticed that some transactions are improperly marked as anonymous transactions instead of being properly assigned a master customer. This has been rectified so that all transaction records are properly assigned the correct master customer. If you do not have houeholding logic enabled, then you were not susceptible to this issue.
Actions	AGO-10792	Actions users often need to send an Actions campaign in a fixed (i.e. previously determined) data format to a downstream destination, with very little input from AgilOne on the required format/content. For example, many email service providers (ESP) require fixed data formats, including specific content columns in a specific order. Now when an Actions user selects the destination table within the destination tab of the campaign workflow, they can click the schema information button (i) to see what data structure is required for the destination table they have selected. No more guessing or memorizing what content is required for each destination.
Actions	AGO-10927	Continuing our effort to make the AgilOne application more self documenting and user friendly, we have added many new information buttons (i) throughout the Actions campaign workflow. In the future we hope to add more documentation within Metrics and 360 as well! Please email product@agilone.com if you ever spot any out of date documentation.
Actions & Metrics	AGO-10982	Within Actions and Metrics you can now search for campaigns or reports by their unique resource identifier. To perform this search, within the Actions or Metrics search bar, please enter ‘##’ and then the unique identifier of the campaign or report you are referencing, e.g. ##3215 will return campaign or report 3215.