Defect Articles
The following issues were fixed in the 12.1.1 release of Unica Link:
- When publishing a Journey, with database control defined, an error was appearing as there were two icons for the JDBC connector.
- Hierarchical field support on Journey’s field mapping screen.
- When user clicked the Back button on the Mapping screen to reach the Action screen, the Group by Tag field, on the Action screen, was automatically getting enabled.
- In Journey, the Choose option on Field Mapping screen, for Mailchimp connector or Mandrill connector, was misaligned.
- An error appeared when connecting a single field to the Mailchimp connector. The error did not appear when multiple fields were selected.
- The Contact Update response in Salesforce was being displayed as Success, instead of True. Contact update is now in sync with Contact Create.
- Improved error handling has been implemented to help in reporting the root causes of error without breaking the process run.
- An issue was fixed which was causing Link to intermittently start in various environments.
- An issue was fixed in which building a Kafka Link container, as root, resulted in failure.
- An issue was fixed which was causing a 500 error to be produced when publishing Journey on Windows installer.
- An issue was fixed in which the Admin Tool was not working due to MongoDB not being installed on the default port.
- An issue was fixed in which the SQLite file for
oauth2
tokens was locked. - An issue was fixed in which the Overwrite option from the Copy to project feature was appending numbers to the schema name.
- An issue was fixed in which the installer was not picking up the latest platform: platform_app_2.zip.
- An issue was fixed by adding a new property scope to nodes (the same as the cache node), which controlled whether the decision was made on the flow variable or the cache value.
- An issue was fixed by adding a default value to the cache functionality.
- An issue was fixed in which Windows directory forward slashes were causing intermediate file computation failure in the Append mode.
- An issue was fixed by replacing Placeholder fields, in email subjects, with
dynamic input from a
CSV
file. - A fix was provided to accommodate a new property
connector version
during error response generation. - An error Server HCH Runtime : Unable to deploy : 404 Not Found was displayed when saving create/publish Custom Connector.
- When configuring Unica Link in SSL, the logs indicated that Link had started, but the native-install.sh was unable to retrieve the status
- Customer unable to find 'testapp' as mentioned in 'Creating Link Connector tutorial' documentation.
- Error
404
appeared when accessing connections in Journey.