Skip to main content

Custom External Policy Field Provider

Learn about how to use the Fenergo SaaS platform to interact with External Data Functionality that can fill specific data fields and data groups such as addresses.

📄️ External Policy Provider for single Fields and Data Groups

Clients can configure specific fields or a data group in their policy to connect to Three types of external data sources which can fill those policy requirements. These allow users to Search for Suggestions and Validate a Selection for a single specific field through the FenX User Interface or to fill a Collection of fields in a data group. This document will detail how to configure and test that functionality. The capability is enabled through the Policy Providers Command and Query APIs.

📄️ Single Field External Validate API Walkthrough

Clients can configure a specific single field in their policy which will invoke a client hosted adapter when the user saves the content on the form or attempts to complete a task on the UI. The call to that adapter will send whatever has been typed into the text box and your implementation can match that and determine if the value is a valid result. If the Value is invalid, a Real-Time response will be displayed as an error message on screen along with whatever message your adapter returns. ALSO: The validator call when sent from within a journey will also send the Entity Id (for the target of that Journey) and the Draft Entity Id which is where the data changes are made.

📄️ Multi Field External Search and Details API

Clients can configure a multi cardinality data group in their policy which will invoke a client hosted adapter when the user types into a search box. The content from the search box will be sent in a call to that adapter and the implementation can search a repository or data store for matching results and return an ordered list of formatted data back. The result set is sent back Real-Time and the response will be displayed as a list of options on the UI. The user can then select one of the matching items and the ID of the selected item is sent to a second endpoint to retrieve the details mapped to the configured fields.