6 docs tagged with "Object/Property Mapper"

Many Conscia DX Engine solutions involve Orchestration Components that each invoke different Webservice APIs to gather related data. Logic to select, validate, filter, merge, and otherwise blend data can depend on data from any number of Components.

This recipe demonstrates preparing and supplying product data for something like a highly detailed product comparison page. We are accessing data from multiple sources, and using Conscia to unify arrays of product data in real-time to deliver a richer and more performant web experience.

There is often a requirement to manage static values in your projects. Orchestration Components can be used for this purpose in Conscia. This recipe manages the Merchant Account identifier for the Adyen payment provider with this method.

Splitting Traffic with Multiple Data Sources

With an example that retrieves a product category tree from Salesforce B2B Core APIs, this document describes how you can use Sub Components to implement recursion with Conscia to access hierarchical data structures in third-party products. Many third-party APIs provide access to hierarchical data one level at a time. Calling code must retrieve the child nodes for a root node and then retrieve the child nodes of those child nodes and then retrieve the child nodes of those grandchild nodes, continuing to some level of depth or until there are no more descendants. Where an API does not offer a direct way to retrieve an entire hierarchy, solutions can use recursion to access the entire node tree. This scenario is common in generating website navigation elements or similar hierarchical structures when the API provider does not offer a comprehensive hierarchy endpoint.

In this recipe, we will show you how to use the DX Engine to stitch data from multiple sources. We will use GitHub Gists to store different parts of a product detail page. We will then use the DX Engine to fetch the data from the Gists and stitch it together into a single JSON object.