This blog post contains information about Orchestration Components in the Conscia Digital Experience Engine (DX Engine), which is part of the Conscia’s SaaS Digital Experience Orchestration (DXO) offering. If you have information or questions about Components, please comment on this blog post. This blog post is part of a series All about the Conscia DX Engine.
Orchestration Components represent individual steps in an orchestration process. One Component might invoke a Webservice API and another in the same flow might transform its JSON response before a third Component uses that data.
Each Component has properties defined by its Component Type. The properties of Component Type define the user interface for working with Components of that type. For example, Universal API Components have properties that let you configure the Webservice API that they invoke; Object Mapper components have properties that let you configure JSON object mapping. The Type of a Component also determines how the DX Engine invokes that Component.
If a Component consumes the response of another Component, or uses a Context value enriched by another Component, then the DX Engine registers a dependency between those Components. Before invoking a Component, the DX Engine invokes Components that set Context values and Components with responses used by that Component. These dependencies appear in the Visualizer in the DX Studio User Interface.
Components can have Sub Components.
You can use Conscia Webservice APIs to manage and manage Component definitions.
Deliverystack.net 
2 thoughts on “All about Orchestration Components in the DX Engine”