Application Launcher

Currently a work in progress…

Area	AgilOne JIRA	Description of functionality after the fix
Actions	AGO-11363	While previously AgilOne did not enforce any consistency with regard to the order of columns in Actions output content, we have found that the recent introduction of the ‘Echo’ content model has upset some of our client’s downstream integrations. In this release we have introduced an update that maintains the order of Actions content columns across saves and executions of an Actions campaign. The order of Actions output columns can still change when a campaign is cloned (i.e. copied). If you rely on the order of columns that Actions outputs, we recommend that if you need to add new content to a previously executed campaign, that you clone the campaign first before adding the new content. Thank you!
Actions	AGO-10979, AGO-11344	When using the “Were included in an AgilOne campaign” and “Were included in an AgilOne campaign with variant” Actions Audience filters, you can now filter by more than one AgilOne campaign at a time. This should significantly improve the performance of Actions campaigns that currently utilize multiple versions of these filters.
Actions	AGO-11188	In Actions, you can now filter date/time based attributes by a relative number of weeks. E.g. Find all customers who purchased a product in the last 3 weeks. Previously you could only filter by days, hours, and minutes. As always, the time frame utilized to filter the audience is calculated at time of execution. In the previous example, if the campaign runs at 8am, the audience will be filtered to include anyone who purchased a product since three weeks ago at 8am (i.e. today at 8am minus 3 weeks * 7 days/week * 24 hours/day * 60 minutes/hour * 60 seconds/minutes).
Platform: IRE	AGO-11352	To enable better performance reporting of AgilOne’s Identity Resolution Engine (IRE) we have begun to make IRE more verbose in its procedures and informative of how it reached each outcome. In this release we are making sure that each intermediary dataset in the IRE process is maintained for post-completion analysis. Previously, intermediary tables were truncated to minimize disk usage and the final result was poorly labeled for any sort of post-completion analysis.
Platform: DW Tracker API	AGO-11353	We have enhanced our DW Tracker API so that it can ingest all email events in real time. This should enable additional real time use cases around email engagement, should your Email Service Provider support informing AgilOne of email sends, opens, and clicks in real time.
Actions	AGO-11371	Now Actions users can refine by an event’s time stamp and search term in Actions audience filters and content models. This will enable our clients to filter product browsed/abandoned events within Actions content so that only recently browsed/abandoned products are exported. Additionally, this will enable Actions users to find all customers who searched on their website using a specific word or phrase.

1835 Release - 2018-09-25