Known issues
The following table lists the known issues in Unica Journey 12.1:
| Defect ID | Known Issue |
|---|---|
| HMA-312568 | Unica Journey and Unica Link application URLs should have the same domain names. Unica Journey andUnica Link applications deployed on different domains will not work. |
| HMA-312416 | Canvas keeps moving to the bottom right when any splits (decision, engagement) is dragged and dropped on canvas. |
| HMA-312391 | No usage information is available for JourneyEncryptionUtility and need to convert it into Unix
compatibility level using dos2unix. |
| HMA-312365 | Longer description is not shown completely when hovered over an Entry Source, Data Definition, or Journey in their listing pages. |
| HMA-312214 | Underscore is not supported with Contains operator in Decision Split control. |
| HMA-312164 | For date based goal validation message date format shown in warning message should be same as Date set in goal. |
| HMA-312140 | Getting undefined in count on Journey intermittently. |
| HMA-312105 | With Unica Platform login type set to IBM Security Access Manager, user should login to Journey from Unica Platform. Login directly to Unica Journey is not supported. |
| HMA-312082 | Invalid dates passed in entry source are getting incorrectly processed. Journey does not restrict these dates, user would need to send valid date in format as specified in data definition. |
| HMA-312023 | User not able to search Entry Source, Unica Journey and Data Definitions with non-English characters. |
| HMA-311993 | In Decision Split – Date gets processed without matching the year date format part. You will need to enter the date in correct format as specified in data definition. |
| HMA-311812 | Uploading file to entry source while Kafka service or engine is down would lead to incorrect data processing in Journey. |
| HMA-311445 | User would need to enter the characters supported for Kafka topic names. Any invalid characters not supported for Kafka topic names would lead to incorrect behavior in publish touch point. |
| HMA-311066 | Delete or clean-up of Kafka topics created by Publish control is not available. Manually deleting these topics can lead system in inconsistent state. |
| HMA-310794 | Even if the user clicks on cancel while configuring a touchpoint, and open the Journey again from listing page, Touchpoint is shown as configured. |
| HMA-310709 | Journey Application and Unica Platform is not able to run in single instance of Tomcat. Unica Platform needs to be up and running to run Journey application. |
| HMA-310351 / UL-171 | While using Mailchimp connection, if user uses the custom tags then its only get assigned to contacts and no system defined tags are applied to contacts in Mailchimp. |
| HMA - 310348 / UL-184 | While using Mailchimp connection, data once uploaded in mailchimp contact will not get updated again from Journey application. |
| N/A | Unica Deliver integration with Unica Journey is supported only with Kafka does not have any authentication mechanism. |
| NA | Unica Journey and Unica Link applications URL should be having same domain names. Unica Journey and Unica Link applications deployed on different domains will not work. |
| HMA -312560 | Link interface (touch points) and connection listing details will be shown in english only |
| HMA -312266 | Journey installer does not support silent mode installation. |
| HMA -315161 | Browser crashes - Unable to upload a file of size approx 1.6 GB |
| HMA - 316262 | User is unable to add significant field for In use Data Definition in case of Paused Journey. |
| HMA - 316264 | Journey is not getting completed after achieving contact based goal if journey is paused and published. |