Journey Multi Partition

From V12.1.7 onward, Journey will support multi partition. For users upgrading to 12.1.7, if there is more than one partition in their system then it might lead to cross-partition references amongst the various entities in the Journey application.

Example of cross-partition reference:

Entry source ES001 created by a user of partition1, is being used in a Journey JS0001 created by user of partition2.

An administrator should run following query before the upgrade.

select * from organisations

If this query returns only one record and with id column value as 1, then such system can be upgraded directly to 12.1.7. Otherwise, user will have to get in touch with support team to check and fix cross-partition references present in the system (if any)

Prior to 12.1.7, a user could access entities belonged to other partition.
  • From 12.1.7 onward, user’s view will be restricted to the entities of his own partition. e.g. user of partition1 can see only those entry sources, data definitions, templates, Journeys and folders which belong to their partition.

    Accessing entities of other partition in any way will result in an error 404 (not found). This is to ensure that any malliecious user does not invoke Journey's rest APIs to access cross-partition resources.

  • A Journey will not accept the data coming via an entry source which belong to different partition. In such case system will log an error. However, if a given entry source is used in multiple Journeys and some of those belong to the partition of the entry source, then the data will be sent to only those Journeys.
  • A Journey will not be able to publish the data to an entry source which belong to different partition via publish action touchpoint. In such case, system will log an error and the audience will move to next touchpoint.
  • If a client id /secret pair is used to input the audience data through /api/entry sources/rest/data, then such pair should belong to the partition of an entry source. Otherwise, system will give an error 404 not found. In such case, the administrator will have to generate a new client id/secret pair by logging as the user of an entry source's partition. All the references of existing client id/secret pair in the downstream applications will have to be corrected as well.

  • A user cannot copy a Journey with references of entry source or data definition of other partition. Else, system will give 404 not found error to the user.

Configuration changes in platform configuration.

On clean installation of 12.1.7 or upgrade to 12.1.7, a new node partitions will be added in the Journey application's node. Administrator will have to create one or more partitions by clicking on partition template node and specifying the partition name. The number of partitions and their names must match with those present in other installed unica products like campaign, deliver etc.

On adding partition Node, for example partition1, following attributes will appear when user clicks on partition node (e.g. Affinium|Journey|partitions|partition1)
  • Link_Configured (default No)
  • Deliver_Configured (default No)
  • Contact_Central_Configured (default No)
  • Dedup_End_Audience (default No)
  • Goal_Max_Allowed (default 15)
  • Mask_Exported_Audience_Data (default No) - This property is specific to engine. If the property is set to Yes, then maskable fields in audience details will be masked while publishing the audience details to csv or kafka topic in publish action touchpoint. If the Full_Mask_Exported_Audience_Data property is set to Yes, then maskable fields in audience details will be fully masked.
  • Full_Mask_Exported_Audience_Data (default No) - This property is applicable for both web and engine. In case of journey web, if the audience details pop-up is visible and clickable in the first place on journey canvas, then the values of maskable fields will be completed masked if this property is set to Yes and will be partially masked if the property is set to No.

    In case of journey engine, when the audience data is published to csv file or kafka topic on publish action touchpoint and if both the properties Full_Mask_Exported_Audience_Data and Mask_Exported_Audience_Data is set to Yes, then the values of maskable fields in that data will be completed masked and will be partially masked if the property is set to No.

Following Nodes will be added in each of the partition node

Journey Configurations
  • Journey_Waittime_Configurations
  • Sync_Contact_and_Response_Tables
  • Validations_On_Journey_Records
  • Validation_Headers - Enable/Disable Audience Details Pop-up depending on the headers and its value configured in Journey Configurations under: Affinium|Journey|partition|partition1|Journey_Configurations|Validation_Headers

    If all the mentioned headers found in the http request and each header contains at least one of the supported values mentioned in the configuration, then Audience details pop-up will be shown to the user. Header names and values are not case sensitive i.e. they will match without considering their case (upper/lower). In each of the triplets which consists of header name, supported value(s) and field separator (in case of multiple values), administrator can choose the field separator of their choice. If the value separator field is kept blank, then entire value will be considered as a single supported value.

    • Validation_Header_Template
  • Link Configuration
  • Deliver Configuration
  • Integration
Note: The settings in as well as global settings in platform configurations (i.e. settings outside the partitions) have been retained for customer's reference.
  • Engagement_Split_Waittime
  • Decision_Split_Waittime
  • Max_No_Of_Days_In_Delay_Evaluation
  • Max_No_Of_Days_In_Delay_Expression
  • Sync_Contact_and_Response_Tables
  • Validations_On_Journey_Records - [Default value is Yes]
Link Configuration
  • Link_URL - [change_me]
  • Link_Data_Source_User - [change_me]
  • Link_Data_Source_Name - [change_me]
  • LinkProjectName - _app_journey [Default - Should be kept as is for all partitions]
  • Application - journey[Default - Should be kept as is for all partitions]
Note: Link application does not support multiple partitions. Hence, Link integration can be used only for one partition.

Deliver Configuration

  • Deliver_URL - User needs to configure valid Deliver TMS URL [change_me]
    Note: The configuration Affinium|Journey|Deliver_Configurations|Unsubscription_Attribute is still global i.e. it is not present at partition level.
  • preferredCognitiveServiceProvider

From V12.1.7, Journey Engine will also read the partition configuration from platform on startup. Any changes in the configuration inside partition node will require restart of Journey Web and Journey Engine.

Upgrading Journey to 12.1.7 requires platform to be upgraded to 12.1.7.