Welcome
Unica Content Integration
Content Integration facilitates easy integration with Content Management Systems and enables searching content from the Content Management Systems.
Release Notes
Release Notes for version 12.1.11
Known Issues
The following are the Known Issues in Unica Content Integration 12.1.11.

Unica Platform
Release Notes
System Requirements
Installation Guides
Upgrade Guide
Administrator Guides
Reports
GDPR Guide
Unica Content Integration
Content Integration facilitates easy integration with Content Management Systems and enables searching content from the Content Management Systems.
- Release Notes
  - Release Notes for version 12.1.11
    - System requirements and compatibility
      Unica Content Integration operates as part of the HCL Marketing Software suite of products. Unica Content Integration requires Unica Platform 12.1.11.
    - Unica Content Integration Overview
    - New Features in version 12.1.11
      New features were introduced in Unica Content Integration for 12.1.11 release.
    - Known Issues
      The following are the Known Issues in Unica Content Integration 12.1.11.
    - Before you contact HCL technical support
      If you encounter a problem that you cannot resolve by referring the documentation, your company's designated support contact can log a call with HCL technical support. Use these guidelines to ensure that your problem is resolved efficiently and successfully.
- Installation and Configuration Guide
- Developer Guide
- User's Guide
Licensing Guide
PDFs
Glossary
Notices

Known Issues

The following are the Known Issues in Unica Content Integration 12.1.11.


Issue ID	Description
HMA-349370	DX autosync offer creation fails when URL of type attribute has NULL value set in the template, as well as NULL value being passed as DX contents attribute value.
HMA-408343	When attempting to deploy `asset-viewer.war` on a 12.1.11 setup running on Red Hat Enterprise Linux (RHEL) with JBoss EAP and IBM DB2 (including fastupgrade base setup), the deployment operation fails and rolls back. Workaround: Add JVM argument in jboss/bin/standalone.conf : `export JAVA_OPTS="$JAVA_OPTS -Dlog4j2.Configuration.allowedProtocols=vfs,vfszip,vfsfile"`.