New features and changes in version 12.1.2

Enhanced Triggered Actions

The formerly known feature of “Trigger Messages” is completely rewritten with a number of enhancements on both functionality and user experience, and renamed to “Triggered Actions”.

1. A refreshed, more user friendly user interface replaces the old one.
2. Offer lists can be used in place of offers for more flexibility.
3. Triggered actions can be directly linked to outbound gateways without creating intermediate outbound channels and handlers
4. Outbound channels can still be created in UI as a conceptual layer for wrapping one or multiple gateways.
5. When an offer or an offer list is used in a triggered action, expressions can be used for dynamically deciding its eligibility, calculating its score, and parameterizing its attribute values.

Support of offer lists in FlexOffers

Besides using individual offers in FlexOffers rules, both static and dynamic offer lists can be used.

Offer lists are applied in rules as same way as offers, so all the currently supported features are available, such as using predicates for eligibility, scoring, and attribute parameterization. This gives a flexibility of reusing same rules with everchanging offers referenced by those rules.

Enhancements to event patterns

1. A new type of event pattern “Sequence” is added. This new type allows a series of events to be required in an event pattern, and all those events have to occur in the configured order, with an optional time frame between adjacent events.
2. A condition can be added for each event in an event pattern such that the event has to be posted with the configured parameter and value to be counted to this pattern.
3. A same event can be used in an event pattern multiple times, given they have different conditions.

Integration with Contact Central

The triggered actions created in Interact can be integrated with Contact Central.

1. While defining each outbound gateway (except Journey gateway), it can be configured whether or not messages sent through this gateway should be integrated with Contact Central.
2. During the run time, Interact verifies with Contact Central and decide whether to send each message.

Support of SSDB offer attributes

Offer attributes of SSDB type can be used for parameterization.

Upgrade on caching

1. The embedded EHCache is upgraded to 3.9.6.
2. The option of distributed EHCache is removed. If a current environment uses this option, it will be migrated to distributed Ignite. If this configuration is still detected during the startup of Interact run time, the initialization will fail.

Better handling of duplicate cell codes and attribute names

When a cell code or an offer attribute name is found to have duplicates, instead of throwing an error and failing the deployment, a warning is logged and the most recently updated cell/attribute is used in the run time.