Application Launcher

Area	AgilOne JIRA	Description of functionality after the fix
360	AGO-10095	We have patched a bug in the 360 Profiles Overview tab that was incorrectly allowing each sub-section (recent events, recent transactions, etc.) to be scrollable.
Actions	AGO-12142	Actions just became much more user friendly because now we are surfacing detailed descriptions of many Actions filters and content right in the application. No longer do you need to go to Zendesk to review what ‘Average Discount Rate’ means. Now you can just click the information button on ‘Average Discount Rate’ to get a more detailed description.
Actions Campaigns+	AGO-12170	The Campaigns+ listing page has been updated to properly show if a Campaign+ is scheduled.
Actions Campaigns+	AGO-11957, AGO-12039, AGO-12062, AGO-12188	A significant portion of this release was dedicated to developing two new features for Actions Campaigns+. The first of which is the ability to create and test randomly assigned variants of communication creatives via Campaigns+. In Campaigns+ we have gone even further than A/B tests in existing Campaigns. Previously, A/B tests were limited to the SFTP and A1Mailer destinations, but now they can be used across all destinations. Additionally, A/B testing used to be limited to variants randomly assigned by a percentage (e.g. 45% in A, 45% in B, and remaining 10% as Holdout), but now you can also randomly assign individuals into variants based on a quantity (e.g. first 100 in A, next 1000 in B, and drop the remainders).
Actions Campaigns+	AGO-12037, AGO-12038, AGO-12054, AGO-12055, AGO-12084, AGO-12173	The second significant Campaigns+ enhancement we are releasing with this sprint is the ability to on-demand refresh the count of members per segment. If you have a segmented Campaign+ you can now go to the Content screen and request that the count of members per segment be refreshed. Then you can click another button to see the most recent refresh of counts per segment. This allows you to review how your segments are populated, and then adjust them as needed, before you execute the campaign.
Platform: Euromessage Output Connector	AGO-12195	For clients that push Actions Campaigns to Euromessage, we previously required that every DW table start with `A1_` and end with the Campaign ID (e.g. `_5213`). With this enhancement we have made these prepended and appended values optional. Therefore if you have an existing DW table you would like several Actions Campaigns to push to, you can.
Platform: Machine Learning	AGO-12001, AGO-12003	In this release we are simplifying how we integrate the result of our machine learning models into each AgilOne application. Now each 1:1 machine learning model (1 customer belongs to only 1 segment, such as LTC, but not U2P) will be summarized on a new Machine Learning Summary table that is easier to integrate into Actions, Metrics, and 360. Previously, each new model required an additional integration effort before they became useful to the user.
Platform: Responsys Input Connector	AGO-11913	For clients that ingest data from Responsys and perform A/B testing within Responsys (meaning that LAUNCH_STATE CAMPAIGN_VERSION_ID is populated), AgilOne can now map this data and any other custom attributes from Responsys into AgilOne. This allows AgilOne to better accommodate custom data models in Responsys.

In addition, we have made behind the scenes enhancements that may include improvements to stability, performance, and/or internal or unreleased features.

1922 Release - 2019-06-17