Fixed defects
The following table lists defects that are fixed in Unica Interact V12.1.9.
| Issue ID | Description |
|---|---|
| HMA-373736 | API Authentication was updating USM_USER Table in each API call. |
| HMA-373735 | AdminServlet could be accessed without proper authorization. |
| HMA-373535 | Error in one scheduled task was preventing all tasks from being loaded. |
| HMA-372998 | In ExecuteBatch, if the first command failed, the subsequent commands in the batch were still getting executed. |
| HMA-372792 | Campaign segments were not working when audience level contained certain special characters. |
| HMA-371852 | The value of system added offer attribute ScoreInDouble was getting rounded off to a whole number. |
| HMA-371496 | A scheduled triggered action was getting processed multiple times where there were multiple Interact run time instances. |
| HMA-371456 | If both positive and negative actions were configured for an event pattern, an action was getting invoked multiple times. |
| HMA-370029 | From the Simulator UI, offers are were not served when there were more than one interaction point for the selected. |
| HMA-369917 | For an event pattern that included multiple events, and had both positive and negative actions configured, the same action was getting incorrectly invoked multiple times. |
| HMA-369687 | Delayed event pattern actions were still invoked even if the originating event patterns were already disabled at the scheduled time. |
| HMA-369294 | A scheduled event action was getting processed multiple times where there were multiple Interact run time instances. |
| HMA-369186 | Navigating to IC page for an IC with more than 1000 flowcharts was generating an
ORA-01795 error. |
| HMA-368893 | Incorrect UpdateTime was stamped in event pattern states. |
| HMA-367540 | UA_Offer table was hard-coded in SQL query in Interact design time. |
| HMA-366855 | Could not search offer codes which contained uppercase characters. |
| HMA-366790 | Earlier returned offers were overwritten by the later getOffers and contact/response event failures. |
| HMA-365821 | java.io.OptionalDataException was occuring when processing requests were created using older versions of interact_client.jar and sent via Java API. |
| HMA-365444 | When cross session response data was retrieved but failed to get processed, such records were getting stuck in a situation that prevented them from being reprocessed. |
| HMA-365233 | Simultaneous export actions were getting initiated on Coverage results and led to database connection depletion. |
| HMA-364730 | Contact and response data was not written to folder /unica/Interact/loaderStagingData/DefaultInteractRuntimeInstance/. |
| HMA-364524 | Classes were missing in interact_client.jar JsonUtils. |
| HMA-363663 | Interact design time upgrade was supposed to only migrate partitions that had
InteractInstalled=yes. |
| HMA-363661 | Interact design time was not working with multi-partitions. |
| HMA-363475 | Runtime exception related to effective date and/or expiration date were encountered when
calling getOffers. |
| HMA-363434 | There were problems with permanent derived fields in Interactive flowchart with French version locale. |
| HMA-362052 | On the FlexOffers UI, if user updated a single rule, all rules that were selected were getting updated. |
| HMA-361887 | A smart rule could not be edited if it was referencing a segment that was redrafted in Segment Central. |
| HMA-355974 | Cancel and Add buttons were missing on FlexOffer Add New Rule window. |
| HMA-351897 | Security token was included in the URLs of some UI pages that was communicating with the server. |
| HMA-321111 | Incorrect URL existed in Interact REST API documentation. |