Using Lexis Nexis Connector in Digital Journeys

The Lexis Nexis Connector consists of a digital journey, a client side script, and an endpoint. Below are the steps used when calling the connector.

1. Before calling the connector, the parameters must be set. The environment settings required for the API search are set through the below variables. The Lexis Nexis platform uses a SOAP/ xml format, but the search function and the returned data is in REST/ JSON format.

Setting the Paramenters Example

Copy

const clientId = getAppSetting("lexn-client-id")

const password = getAppSetting("lexn-password")

const userId = getAppSetting("lexn-user-id")

const searchUrl = getAppSetting("lexn-url")

const roleTypeUser = getAppSetting("lexn-role-type-user")

const roleTypeRole = getAppSetting("lexn-role-type-role")



const searchLibraryName = "FTOS_EXTD_LEXN_Search"

const searchBindingName = "BasicHttpBinding_ISearch";

const searchWebApiClient = importWebApiClient("FTOS_EXTD_LEXN_Search", searchUrl, "BasicHttpBinding_ISearch");



const response = searchWebApiClient.search(contextSettings, configSettings, inputConfig)

2. Use the ebs.callActionByNameAsync function with the FTOS_EXTD_LEXN_Search parameter when searching for certain information from the Lexis Nexis database in the digital journey.

3. The FTOS_EXTD_LEXN_Search endpoint is called. The response is partially parsed at data model level and returned fully in a JSON object.

Calling from the Digital Journey Frontend Example

Copy

let reqObj = {

entityType: formScope.entityType,

clientReferance: formData.model.clientReference,

dppa: formData.model.dppa,

glba: formData.model.glba,

predifinedSearchName: formData.model.predifinedSearchName,

writeResultToDatabase: formData.model.writeResultToDatabase,

assingResultToEmailNotification: formData.model.assingResultToEmailNotification,

assingResultToRolesOrUsers: formData.model.assingResultToRolesOrUsers,

assingResultToType: formData.model.assingResultToType,

nameFull: formData.model.nameFull,

nameFirst: formData.model.nameFirst,

nameLast: formData.model.nameLast,

nameGeneration: formData.model.nameGeneration,

nameMaidenName: formData.model.nameMaidenName,

addressStreet1: formData.model.addressStreet1,

addressStreet2: formData.model.addressStreet2,

addressCity: formData.model.addressCity,

addressPostalCode: formData.model.addressPostalCode,

addressCountry: formData.model.addressCountry,

additionalInfoDay: formData.model.additionalInfoDay,

additionalInfoMonth: formData.model.additionalInfoMonth,

additionalInfoYear: formData.model.additionalInfoYear,

additionalInfoUnparsed: formData.model.additionalInfoUnparsed,

additionalInfoLabel: formData.model.additionalInfoLabel,

additionalInfoType: formData.model.additionalInfoType,

gender: formData.model.gender,

recordId: formData.id

}

ebs.showLoadingPanel()

ebs.callActionByNameAsync("FTOS_EXTD_LEXN_Search", reqObj)

.then((result) => {

if (result.IsSuccess == true) {

ebs.showMessage("Success", "success")

formData.refreshForm()

} else {

ebs.showMessage("error", "error")

}

})

HINT
As a developer, the data can be obtained from the data model or from the JSON object.