Fixed defects
Version 12.1.3
This section lists fixed defects in Unica Deliver, version 12.1.3.
Issue | Issue ID | Description |
URLs were not getting saved in message template in Quick Builder. | HMA-338235, HMA-338156 | URL links in SMS template was not getting saved from Quick builder. It was getting saved from the message editor. |
URL Link was not available under sent email when communication was created in Quick Builder. | HMA-336469, HMA-336373 | URL Links were not working for images if users created email from Quick builder. |
For Quick builder, the Cancel operation, for email configuration, was not working properly. | HMA-335619, HMA-335611 | Email configuration fields in Quick builder were not getting blank when user canceled it after entering values and coming back to email configuration. |
In APP Push was not getting published if you copy-and-paste text with any formating. | HMA-335581 |
In APP Push was not getting published if you copy-and-paste text with any formating (for example, text with color). Workaround: First, copy-and-paste the text to a text-based editor to remove all formatting, and then copy-and-paste it from the text-based editor to In APP Push communication and format it as per your requirement. |
The last letter was trimmed in the personalized field. | HMA-335523, HMA-335468 | In Quick Builder for Email, if the user inserted a personalized field before any text, the last letter was getting trimmed. |
Unable to save changes made to the template when done via "Edit layout / default content" from within the communication. | HMA-335342, HMA-335426 | Users were unable to save changes made to the template when the changes were done using "Edit layout / default content" within the communication in Message Editor. The issue is fixed by disabling the menu option "Edit layout / default content". |
Link button and Save button was clickable even though URL/Landing page was not defined. | HMA-335255, HMA-335247 | Link button and Save button was clickable even though URL/Landing page was not defined. |
Email configuration was disappearing from the UI. | HMA-335214, HMA-335155 | In Quick Builder, Email configuration was disappearing from the UI. |
URLs in Quick builder were getting erased for Buttons. | HMA-335213, HMA-335155 | URLs in Quick builder were getting erased for Buttons. |
Communication, created in Quick Builder, was not disappearing from Quick Builder when edited with Message Editor. | HMA-335506, HMA-335151 | Communication, created in Quick Builder, was not disappearing from Quick Builder when it was published from the Message Editor. |
Personalization dropdown UI had white background and did not have a border. | HMA-335057, HMA-335052 | Personalization dropdown UI had white background and did not have a border. |
With SFTP, the OLT file was created in GBs and deliver box never ends. | HMA-335164, HMA-335036 | With SFTP, OLT file was created in GBs and deliver box never ends. Deliver box keeps running for more than 50,000 records. |
& was getting added in the mentioned URL with parameters in email. | HMA-334747 | & was getting added in the mentioned URL with parameters in email. |
Deliverability Monitoring was not displaying properly and a blank page used to appear. | HMA-334734, HMA-334551 | Deliverability Monitoring was not displaying properly and a blank page used to appear. |
In the UCC_RESPONSEATTR table, the Landing page attribute default value was not populated correctly. | HMA-334540, HMA-334418 | In the UCC_RESPONSEATTR table, the Landing page attribute default value was not populated correctly. |
Push was not received by users if it had any built-in personalization field that was used in communication. | HMA-334434 | Push was not received by users, if it had any built-in personalization field used in communication. Built-in personalization field starts from Built-in, when you type #. Ensure that you do not use this when creating Push communication. |
Unica Deliver WSDL SoapUI call was failing with the following error:
|
HMA-327480, HMA-327417 | Unica Deliver WSDL SoapUI call was failing with the following error:
|