New features and changes in version 12.1.6

Unica Campaign 12.1.6 includes a number of new features and changes. These are listed underneath.

For a list of newly supported and discontinued platforms, see the Recommended Software Environments and Minimum System Requirements guide.

Upgrade Paths

Unica Campaign supports the following upgrade paths:

  • 12.1.x → 12.1.6
  • 12.1.0.x → 12.1.6

Customers on versions earlier than 8.6.x must:

  • perform a Fast Upgrade from existing version to version 8.6.0 (for more information, see HCL Unica 8.6.0 Fast Upgrade Guide).
  • perform a Fast Upgrade from version 8.6.0 to version 12.1.0 (for more information, see HCL Unica 12.1.0 Fast Upgrade Guide).
  • perform an in-place upgrade from version 12.1.0 to version 12.1.6.

Customers on versions earlier than 11.1.x.x can:

  • perform a Fast Upgrade from existing version to version 12.1.0 (for more information, see HCL Unica 12.1.0 Fast Upgrade Guide).
  • perform an in-place upgrade from version 12.1.0 to version 12.1.6.

Customers on versions 11.1.x.x/12.0.x.x can use one of the following options for upgrade:

  • Option 1
    • perform an in-place upgrade from existing version to version 12.1.0.
    • perform an in-place upgrade from version 12.1.0 to version 12.1.6.
  • Option 2
    • perform a Fast Upgrade from existing version to version 12.1.0 (for more information, see HCL Unica 12.1.0 Fast Upgrade Guide).
    • perform an in-place upgrade from version 12.1.0 to verison 12.1.6.

Remove Highcharts and replace with D3 for Sanky reports in Campaign

To show the flowchart in sankey graph, we were using Highcharts (third-party library). Highcharts over time had various issues such as loss of information for huge data, library vulnerability issues and limitation to extension for new features.

We have now replaced the Highcharts library with more robust and flexible D3 library and incorporated new features such as colour theme, zoom support, toggle of labels etc.

D3 library is highly customizable and easily allows for extension of features in the Sankey graph.

Campaign Fusion

Input cells that are included and excluded inside the Merge process box are shown in green and red respectively, inside a tooltip.

Delete All Annotations' toolbar option with FC in Edit mode

Delete All Annotations toolbar option is added with the flowchart in edit mode to delete all annotations inside a flowchart in one go.

Disable Campaign Flowchart Execution Status Emails

Unica Campaign can send email notifications to user's "About flowchart" status if the value of enableEmailCommunication configuration property (Campaign|partitions| partition[n]|server|flowchartRun) is set to TRUE.

Auto re-execution of scheduled Flowchart failure

The flowchart is designed to automatically retry a failed process box a certain number of times with a specified delay in between each retry, but only during scheduled runs. The flowchart will mark the status as failed if it is unable to retrieve a database connection within the retry interval.

The configuration parameters for the number of retries (numberOfRetries) and delay between retries (delayBetweenRetries) are still customizable under the Campaign|partitions| partition[n]|server|flowchartRun settings, with a default value of zero. This means that by default, the flowchart will not automatically retry any failed process boxes during scheduled runs.

It is important to note that this behaviour only applies to scheduled runs, so if the flowchart is run manually or triggered in some other way, the retry mechanism may not be activated. Additionally, if the retry interval is too long or the number of retries is too high, it could potentially cause performance issues or other problems, so these parameters should be carefully considered and adjusted as needed.

Save different versions of Campaign flowcharts

The flowchart version is an older working copy of an active flowchart that serves as a backup and allows for flowchart auditing in the future. This versioning feature is applicable to any session or campaign.

Flowcharts are stored in .ses file format. The .ses file is saved on disk and used when opening a flowchart. When saving a flowchart, it is exclusively saved to the .ses file. However, versions of the flowchart are saved and loaded from a database. The .ses file can be manipulated using various utilities, but versions are read-only and can only be deleted, not updated. Opening a version loads it from the database into memory without overwriting the .ses file.

To save a version, the Save Version feature must be used, which saves the version and updates the .ses file simultaneously. It's important to note that the utilities can only be applied to the .ses file and not on the versions. Therefore, if you intend to use the utilities, ensure that you operate on the .ses file.