Defect Articles

The following issues were fixed in the 12.1.2 release of Unica Link:

  • An issue was fixed in which incorrect path used in line 164 of start.bat in Link DesignServer folder.
  • An issue was fixed in which while installation customer failed to rename Apache Tomcat Server folder as server.
  • An issue was fixed in which customer is trying to install link on the same server where they have Unica Journey. The install.bat files fail with error Failed to install Link Application.
  • An issue was fixed in which Link Map with Apache Kafka Adapter fetches data intermittently from Kafka Topic.
  • An issue was fixed in which Link flow does not react on incoming data from Kafka topic.
  • An issue was fixed in which customer has multiple issues with JDBC processing records and inserting.
  • An issue was fixed in which customer was facing deployment error and No Valid License error in hip-rest docker log.
  • An issue was fixed in which Client is not able to publish the journey when they add JDBC connector into journey.
  • An issue was fixed in customer is trying to connect to Unica Link 12.1.0 with Campaign or Journey, but both fail with attached error when trying to send SMS message through Twilio.
  • An issue was fixed in which the client has created a Journey with the JDBC Connector. After successfully publishing the Journey, the data is not being inserted into the database table.
  • An issue was fixed in customer is getting issue while starting link because of misconfiguration.
  • An issue was fixed in which Unica Link requires MongoDB as internal repository.
  • An issue was fixed in which customer is facing SQLite error when publishing Journey.
  • An issue with proxy support in Link has been resolved.
  • An issue was fixed in which customer getting error Fetch failed.java.lang.NullPoinerException while listing table fields through JDBC connector.
  • Customer has reported that the hot fix for MongoDB with the Replica Set feature enabled is not working.
  • An issue with the mailchimp connector encryption has been resolved.
  • An issue was resolved in which customer getting error in packaging the connector.
  • An error was encountered when trying to connect to rest runtime after deploying it on liberty server.