📄️ Custom Screening Adapter Overview
Consumers may need to use their own Screening Provider or a different Screening provider which is not supported by FenX or planned for our roadmap. For these situations, the Fenergo SaaS Platform allows consumers to setup an external adapter which they can host. That Adapter can then be targeted by the FenX application as an External Screening Provider and provided it implements the agreed interface, will function just like the OOTB screening providers.
📄️ Custom Screening Adapter Configuration Walkthrough
To implement the screening adapter pattern - follow the steps outlined below. Using the below referenced APIs. The API pattern used for an adapter is asynchronous, so calls sent to a client adapter reply with just HTTP 200 and then clients call the Receptor to respond.
📄️ Custom Screening Adapter Implementation
Once the custom screening adapter has been configured in Fenergo (and tested) it can then be used from within Journeys. What this means is that when a Screening Task is configured in a journey, Fenergo will send a Screen Request out to the configured providers. A correctly configured client implemented custom adapter will need to be capable of the following: