New features and changes in version 12.1.9

In Unica Journey 12.1.9, we have introduced some new features, and we have made changes to some existing features or functionality.

The following list mentions the new features, and the changes to existing features, in Unica Journey 12.1.9:

REST API header change

If engine's application.properties contain a key say rest.touchpoint.global.headers=<list of key value pairs>, then these headers will be implicitly during runtime while making rest call.

REST touch point enhancement to provide 'scope' and choose 'Grant Type' for oauth2.0

Enhanced rest touch point UX so that user can choose appropriate grant type for Oauth 2.0 authorization type Also added the ability to provide scope field which is required by Oauth2.0.

Multiple kafka topics

Unica Journey supports writing to any Kafka instance other than the one used internally. The Publish touchpoint allows selecting a Kafka instance and configuring the desired topic.

Entry source linked Journey details

Entry Source detailed page to display the journey(s) that this Entry Source is associated with. When a user navigates to the detailed page for a specific Entry Source, user should be able to see the journey(s) and Data Definition (DD) that this Entry Source is associated with.

Journey-Audit trail

The system shows a detailed log of all significant activities over Journey UI, including but not limited to the creation, modification, and deletion of tasks or objects. The information such as user IDs, timestamps, updates, edits, save, etc. All activities must be recorded and published in the History tab of the Journey.

Retry mechanism for failed delivery of messages

The goal of this feature is to ensure that audiences who were stuck or whose communication couldn't be processed for any reason are not moved to the next touchpoint until the communication is successfully sent at the touchpoint where the audience was stuck. There will be an "error" statistics on a particular touchpoint for and clicking on this status will open the panel to retry sending the communication.

Renter Audience in the Journey

This feature provides the ability for the audience to reenter within the same journey, irrespective of the current stage of the audience in the journey. The existing audience within a journey, even if they have completed the journey, will have the option to reenter the same journey.

Push stats enhancement

A new event, Dismissed, is supported by Deliver and is available to be displayed for Deliver Push communication in a Journey.

Opt in Opt��out Support

Journey touchpoint should respect the contact central preferences before executing for Opt-in Opt-out specific to the channel and Do not send communication if customers are opted out.

Web �� clustering

Journey web requires clustering for high availability also some Data refreshes and REST calls are handled from web side too. This story is supported only on Docker Environment.

Support for performing data migration activities

Added support to perform data migration activities by running set of SQL queries.

Sometimes, in some versions of Journey, there was a need to perform large database updates for moving large amount of data across tables, or performing aggregate operations on the existing data, and storing statistics in other tables. Use the data migration utility for performing this migration with the help of SQL queries. In case of an upgrade, before turning the Journey Web or Journey Engine up, you must run this utility.

Journey Analytical reports