Known Limitations
This section lists known limitations in Unica Collaborate version 12.1.
| Issues | ID | Description |
|---|---|---|
| The Regenerate code option for a Campaign code cannot be used if that campaign is linked to a Corporate Campaign in Unica Collaborate. | Enhancement 130246 | If the campaign code is regenerated, the linked Corporate Campaign becomes inaccessible with a 500 error. |
| List Count is not displayed when List tables are created without indexes on the DB2 10.5 BLU database. | Defect 177025 | When the tables are created in the BLU-enabled DB2 10.5 database, indexes are not created. Users are not able to see the list count for Lists, On-demand Campaigns, or Corporate Campaigns. |
| Template IDs must be alphanumeric. | DEF 058998 | When creating a list, advanced list, On-demand Campaign, or Corporate Campaign, the template ID must be in alphanumeric characters only, even if automatic template ID generation is disabled. |
| Codes that are entered in Unicode characters produce error. | DEF 059161 | When entering the code for a list, advanced list, On-demand Campaign, or Corporate Campaign, Unicode characters produce an error. The code must be entered in alphanumeric ASCII characters only. |
| User variable value cannot accept double-byte characters for SQL server database. | DEF 059517 | When using Unica Collaborate with an SQL Server database, a user variable cannot be assigned a value that includes double-byte characters. These characters are replaced by a "?" character. |
| Migrating a campaign, flowchart, or template from one environment to another. | N/A | While migrating a campaign, flowchart, or template from one environment to another, if there are any user variables defined in the form for which values must be updated in Lookup tables, then the form must be opened, saved and published after importing the template into the target environment. While saving the form after importing, the lookup tables values are updated from Unica Collaborate application. |