Home
Administrator's Guide
Journey Records Validation
When records enter a Journey, users can set validation on the records.

Administrator's Guide
- An Introduction to Unica Journey
  Unica Journey is a goal-based orchestration solution to craft, execute, and visualize context-driven, personalized, multi-step omnichannel customer experiences.
- New navigation UI
  Unica has introduced New UI.
- Journey Multi Partition
- Clean-up Journey Audiences
- Unica Journey integrations
- Process of Starting and Stopping Journey
- Journey user roles and permissions
  Before you begin using Unica Journey, you should assign roles and permissions to users.
- Journey interaction logging
  Interaction Logging for Journey is executed as a scheduled job. The scheduling parameters are set in application.properties file of the Journey Engine. The following is an example of the setting:
- Journey logging
  In Journey version 12.1.2 and earlier, the property JOURNEY_LOGGING, in the journey_master_config.properties file, was only used for tracing the audience.
- Journey Records Validation
  When records enter a Journey, users can set validation on the records.
- Journey GDPR
- Kafka authentication using SSL
- Kafka authentication using Kerberos
- Configure Web Application servers Tomcat for SSL
  On every application server on which a Unica application is deployed, configure the web application server to use the certificates you have decided to employ.
- Mailchimp Configuration
  Configuration of Mailchimp as external source with Journey.
- Settings
  Use the settings menu to manage the Journey integrations like Email connectors, SMS connectors, CRM connections, and REST integrations.

Journey Records Validation

When records enter a Journey, users can set validation on the records.

When the Validations_On_Journey_Records property is set to Yes, the validation is performed on Email format, Data type on required fields, and minimum and maximum length of Data Definition for the required fields.

By default, the Validations_On_Journey_Records property is set to Yes.

This property can be handled from Platform side under Platform Configuration. You can navigate under Platform configuration settings: Settings for Affinium|Journey|Journey_Configurations.

Validations_On_Journey_Records: This flag defines whether to run validation on Journey records.

Possible values: Yes / No.

Note:

If the Validations_On_Journey_Records property is set to No, and the user adds some fields in data deduplication setting, the empty and NULL data will not be accepted for data deduplication fields.
After setting the flag, you must log out from Platform and Journey and log back in to both applications for the changes to reflect.
For any reason, if the Validations_On_Journey_Records property is not accessible in Journey from Platform, you can alternatively set the journey.journeyrecords.validationrules property in the application.properties file from Journey web.

Rate this topic

5 stars 4 stars 3 stars 2 stars 1 star

Comment on this topic.

By clicking this box, you acknowledge that you are NOT a U.S. Federal Government employee or agency, nor are you submitting information with respect to or on behalf of one. HCL provides software and services to U.S. Federal Government customers through its partners immixGroup, Inc. Contact this team at https://hcltechsw.com/resources/us-government-contact. Do not include any personal data in this Comment box.