Configuring Components

Here is a sample set of components listed on the Components page.

Here are some facts about Components:

• Some components require a Connection to be configured, while others simply perform some logic.
• Components can be configured through the UI or via the APIs.
• Components that call a backend data source are restricted to one API-endpoint. For example, Cart API, Pricing API, Checkout API will be different endpoints and hence will require a different component.
• Components may have 'Business Rules' associated with them that are executed in real-time by the rules engine
• The Rules for each Component are triggered based on the Context that is passed to it

Steps to configuring a Component:

• Configure a Connector and assign it a unique Connector Code along with a Name. Connector Codes must be unique across your organization.
• Configure a Component and, as typically required, select the Connector from the previous step.
• Configure the Component's Experience Rules to personalize the Component's responses.

Available Components

The following platforms have Components for the DX Engine to add personalization and orchestration capabilities:

• AWS Opensearch Integration
• Agility
• BigCommerce
• Cloudinary
• commercetools
• Conscia DX Engine Object Mapper Components
• Conscia DX Engine Property Mapper
• Conscia DX Engine DX Graph Components
• Conscia DX Engine Metadata Components
• Conscia DX Engine Universal API Components
• Contentful
• Contentstack
• Elasticsearch
• Kontent.ai
• opensearch
• Sitecore
• Strapi

Conscia is continually working with other vendor platforms in order to grow this list.

If a particular vendor does not appear on the above list, it is important to note that the Generic Webservice Call component can be used. Please let us know if you are interested in a Component that does not appear on this list!