---
title: "1841.1/2 Release - 2018-12-13"
date: "2025-09-12T05:57:24+00:00"
summary: "AgilOne 1841.1/2 release: Bug fixes and UI improvements for Actions, Calendar, and data transfers. Enhances campaign management."
image:
type: "announcement"
url: "/customer-data-platform/release/2018-12-13/79851-184112-release-2018-12-13"
id: "5d45daba-1031-496a-ba7f-bbd64905dcb3"
---

Currently a work in progress…

**Area**

**AgilOne JIRA**

**Description of functionality after the fix**

Actions

AGO-11529

For clients that push AgilOne Actions Campaigns to CheetahMail, we have squashed a bug that was resulting in some data not being successfully pushed to a CheetahMail xDB.

Actions

AGO-11429

If your stores (i.e. organizations) have a hierarchical relationship, in Actions, we have cloned two common filters to take advantage of this parent-child relationship:

*   Purchased a product in an organization hierarchy
*   Purchased a product using a promotion in an organization hierarchy

Actions

AGO-11502, AGO-11503, AGO-11624

We have significantly overhauled the user interface of the AgilOne Actions choose channel screen to better visualize the options available to the user. Previously if you were trying to push data to a third party (e.g. Monetate), you had to know which data transfer medium they used (e. g. SFTP). Now instead of memorizing ‘Monetate uses SFTP’ and then clicking on ‘SFTP’, you can just click on ‘Monetate’.

Calendar

AGO-11512

We have minorly improved the clarity of the Execution Calendar user interface. If you do not have access to the execution calendar in AgilOne Hub, please reach out to your Customer Success Manager or the AgilOne Help Desk and request access.

Actions

AGO-11604

Some clients experienced Actions campaign failures due to removing content models from a previously executed campaign. Due to the backend data structure, after the first execution of a campaign, output content can only be added, not removed. Therefore we have blocked Actions users from being able to remove content models after the first execution of a campaign. If you would like to remove a content model please clone the campaign and then edit the clone.

Actions

AGO-11622

We squashed a bug that prevented Actions users from being able to use the following filter conditions on dates in campaign content model refinements:

*   in the range of
*   in the next
*   in future range of
*   in between