--- title: "1807 Release - 2018-03-07" date: "2025-09-12T05:57:24+00:00" summary: "Discover key updates in AgilOne's 1807 release, including GDPR compliance, improved Actions features, and enhanced Metrics reporting." image: type: "announcement" url: "/customer-data-platform/release/2018-03-07/79921-1807-release-2018-03-07" id: "a584d722-8874-492f-a648-e3d875e100b3" --- **Area** **AgilOne JIRA** **Description of functionality after the fix** 360 Profiles, Real-Time Events AGO-10483 The SourceProductNumber field in the Journey tab of 360 Profiles was not being populated for real-time events such as productBrowsed. We’ve fixed that to display the SourceProductNumbers. Actions AGO-10465 For Actions content models that fetch product attributes, you can now refine by product category attributes. For example, you may wish to export the last products purchased within the Women’s Bottoms product category, you can now apply such a filter to the content. Actions AGO-10381 In Actions we have found that it can get confusing which refinement filters are being used when the same attribute applies to multiple entities, most commonly ‘transaction type’, ‘product type’, and ‘organization type’. Therefore, we have added the name of the entity to all refinement filters, so that if you see the filter ‘type’ you will know if it refers to a transaction, a product, or an organization. Actions AGO-10440 In Actions you can now utilize the transaction currency and organization country to better segment your audiences based upon their transaction behavior. Actions AGO-10444, AGO-10476 We have added the ability to select multiple calculated content models in a single Actions campaign. In Actions content there exists a distinction between content that is 1:1 customer to content, vs. content that is 1:many customer to content. Only one content model that explodes the result set, that is 1:many, can be added per campaign. Since calculated content models are only 1:1, and do not explode the result set, we are now allowing the user to add multiple calculated content models to a single campaign. GDPR AGO-10046, AGO-10497, AGO-10505 To prepare with new GDPR regulations AgilOne has developing many behind the scenes features to handle purging or anonymizing the personal data of data subjects. Outside of standard retention policies, purging customer data is brand new to AgilOne. In this release we developed processes to purge data from our Actions, Metrics, and Data Export reporting layers. We also developed processes to mark custom data models as relevant to GDPR purge requests. And we built a user interface that AgilOne Support can utilize to invoke and monitor purge process. Metrics: Cube Reports AGO-10378 The “Chart Settings” button in Cube Reports was incorrectly showing a ” +” icon. We have now fixed it to correctly show a “gear” icon. Metrics: Cube Reports AGO-10479 In Cube Reports, charting can now handle column dimensions in the report. Each combination of column dimenionsion value and measure is exposed as “data series” in the Charting Settings dialog. To make the charts readable, users cannot create a chart when 2 or more column dimensions are included in the report. Metrics: Cube Reports, Template Reports AGO-10357 Reworked the UI for the “Chart Settings” dialog in Cube and Template Reports. The dialog should now be more intuitive, and minimizes the amount of user input needed for creating a chart. The dialog also collects all customizable options for the chart under the “Customize” tab. Metrics: Cube Reports, Template Reports AGO-10454 Charts can now have customizable colors for each data series. The default color palette has also been improved for better visibility of colors. Metrics: Cube Reports, Template Reports AGO-10457 Chart axes and value labels will now have number formatting that can be set by the user. We’ve also introduced a setting for min/max axes bounds. Platform AGO-10469 Introduced a new attribute called “emailHash” in our data model which hashes a customer email address using SHA256. This attribute can be included in the Content step when creating an Actions campaign for external systems to consume.