Home
Administrator Guide
Offer configurations
After installation of Unica Centralized Offer Management, you must configure its properties, and create and assign roles to the users.
Autosync Configurations
Autosync feature is supported for all CMSes. The prerequisite for such a synchronization is that the CMS should send the create, update and expire events to the Content Integration framework and CMS specific plugin needs to be developed in Content integration framework to process the event.

Administrator Guide
- Offer administration concepts
  Offer administration concepts include:
- Offer configurations
  After installation of Unica Centralized Offer Management, you must configure its properties, and create and assign roles to the users.
  - Unica Centralized Offer Management configuration properties
    This section describes the Unica Centralized Offer Management configuration properties.
  - User roles
    Before you begin the admin activities, you should assign roles and permissions to users.
  - Autosync Configurations
    Autosync feature is supported for all CMSes. The prerequisite for such a synchronization is that the CMS should send the create, update and expire events to the Content Integration framework and CMS specific plugin needs to be developed in Content integration framework to process the event.
    - Configuring the COM plugin with the Content Integration node
      You must configure the COM plugin within the Content Integration node.
    - Kafka configurations for Autosync
      There is a new configuration node inside root level Content Integration node, called Kafka configuration. By default, the Content Integration Framework routes the content events received from CMS via application memory.
    - API security filter configuration
      By default, Unica Platform protects webhook invocations. To change the security settings for webhook, create an API security filter under Unica Platform | Security | API management | Unica Content Integration.
- Offer settings
  Use Offer settings to create custom attributes and custom templates.
- Appendix

Autosync Configurations

Autosync feature is supported for all CMSes. The prerequisite for such a synchronization is that the CMS should send the create, update and expire events to the Content Integration framework and CMS specific plugin needs to be developed in Content integration framework to process the event.

Content integration plugin for DX is already shipped with Unica. The plugin expects the events in following manner. This plugin automatically supports all the authentication methods supported by Content Integration Framework.

Content Created event URL

POST <Content Integration framework base URL>/api/AssetPicker/webhook/{systemId}/events/created/{contentId}

Content Updated event URL

POST

<Content Integration framework base URL>/api/AssetPicker/webhook/{systemId}/events/updated/{contentId}

Content Expired event URL

POST

<Content Integration framework base URL>/api/AssetPicker/webhook/{systemId}/events/deleted/{contentId}

DX requires a CustomWorkflowAction to be developed on their side to be able to send these events to Unica. To understand more about CustomWorkflowAction please refer the link: https://help.hcltechsw.com/digital-experience/9.5/wcm/wcm_dev_api_custom_workflow.html .You may also contact HCL DX services team to understand more.

For more information on configuring Unica Content Integration with HCL DX, see the Configuring the out-of-the-box integrations offered by Content Integration topic in Unica Content Integration Installation and Configuration Guide.

Have feedback?
Google Analytics is used to store comments and ratings. To provide a comment or rating for a topic, click Accept All Cookies or Allow All in Cookie Preferences in the footer of this page.