New features and changes in version 12.1.3

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

The following list mentions the support for new platforms, in Unica Journey 12.1.3:

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

  • Log4j Security vulnerability fixes

    Unica v12.1.3 now uses log4j v2.17.1. This version addresses the critical vulnerabilities identified in log4j. It includes the security fixes mentioned in the following Unica Knowledgebase article:

    https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0095491

    For more details related to the fixes in log4j 2.17.1, see https://logging.apache.org/log4j/2.x/security.html.

  • Mask PS data on Journey UI

    Customer specific private information can now be masked from display in the Journey UI. This allows user to specify which DD fields to mask in the Journey UI and they will be displayed with random characters masked out. For example Email will be displayed as s*****@g**.c**

  • Add Failure status to all failed calls in the Journey in Stats list view

    As a marketer, there's a need to know why some of the connectors fail during execution. The Stats List view will now display reason for failures - like "Required fields missing" or "Bad Request", etc. when connectors fail during execution

  • Add reason for Rejected records on Stats view on Journey

    Journey Stats View now displays reason why some records are rejected during Journey execution like Invalid Email id, Invalid mobile, Required field missing etc

  • Disable Email and SMS validation based on a flag

    A global flag is now added to DISABLE validations during Journey records processing - like email format, data type checking, etc. This allows Journey execution without validations.

  • Old template files have been renamed to match their description

    The Journey accelerators in earlier release were not given appropriate names to match what their functionality is. This has been resolved now with meaningful names.

  • Improve Journey logging for better troubleshooting including Journey specific logs

    Journey application logging has been improved now to provide more details for troubleshooting and debugging issues, including Journey specific log files.

  • While configuring any deliver touchpoint a need preview of communication from Journey is available

    While configuring any deliver touchpoint preview of communication from Journey is now provided. This is available in the communication list to verify the communication selected. This allows to preview what the end communication will look like before executing the Journey

  • Changed Push ID to Install ID

    In create Data Definition page, the Journey significant field Push ID is renamed to Install ID to maintain consistency across all Unica products.

  • Journey Audience archival

    For audiences whose Journey has ended, their details are moved to another table to improve performance in all Touchpoints and Journey Controls. The archival does not impact the statistics and reports.