Skip to main content

Configuring Components

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

alt_text

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 API.
  • 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 Experience 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 Connection and assign it a unique Connection Code along with a Name. Connection Codes must be unique across your organization.
  • Configure a Component with the required logic and, if required, select the Connection from the previous step.
  • Configure the Component's Experience Rules, if required, to personalize the Component's responses.

Available Components​

Conscia's Universal API Connector allows you the flexibility to connect to any REST or GraphQL API endpoint and configure any request. The Mapper, Metadata, and Data Transformation Script Components allow for limitless transformation, decisioning logic, and dependency chaining.

Conscia also has pre-configured Component types for a variety of vendors. These provide specific configuration options. The following platforms have Components for the DX Engine to add personalization and orchestration capabilities.