13 posts tagged with "Screening"

Added DriversLicense, SocialSecurityNumber (SSN), and EmployerIdentificationNumber (EIN) to SearchCriteria in batch and to SecondaryIdentifiers in configuration. Right now it's only supported for LexisNexis and any custom providers that want to implement it.

New "AutonomyLevel" property added to BatchMetadataDto. Depending on the value, the matches will be auto-resolved using an AI Agent when they come back from the provider, and auto-close the Screening Results task. Possible values: Manual (default), Semi-Autonomous, Fully Autonomous

New "LastActionedBy" property added to MatchDto. This new proporty will be used to identify who actioned the resolution of the match, i.e Screning Agent, Screening Provider or manually by user (manuallyByUser@test.com).

Added validations in the Screening Receptor when a batch is created and results are sent back from the provider to check:

• That all the entities being returned for the batch search results to the receptor belong to the batch.
• That the match.providerId returned for the batch search results to the receptor exists in the list of the batch providers.

Also, added fields to the Screening Command API in order to support implementation of Alias Screening. For all the endpoints, entityAliases can be sent as null or an empty list if not using Alias Screening.

Update BatchExternalIds to use their own model (BatchExternalId instead of ExternalId), as it does not make sense for a BatchExternalId to have EntityAliasId since BatchExternalId is specifically related to the batch, not any of its entities. This should not affect any clients as Alias Screening has not been enabled yet.

Added fields to support implementation of Alias Screening. There are no breaking changes here, so adapter implementations will continue to work as normal without the need of making any change.

Added PassportNumber to SearchCriteria in batch and to SecondaryIdentifiers in configuration. Right now it's only supported for LexisNexis and any custom providers that want to implement it.

Added support for RDC and WCO for the feature outlined in the previous post through our RDC and WCO adapters, as well as our AdapterMock implementation.

New fields PlaceOfBirthISO2, PlaceOfBirthISO3, CitizenshipISO2, CitizenshipISO3, RegisteredCountryISO2, RegisteredCountryISO3, Address.CountryISO2 and Address.CountryISO3 added to the Screening Entity Search Criteria.

Affected Endpoints​

New field OtherInformation added to the SecondaryIdentifiers of a Screening Provider's Configuration.

• POST /api/configuration
• POST /api/configuration/provider
• PATCH /api/configuration/provider/\{providerId\}
• GET /api/configuration
• GET /api/configuration/provider/\{providerId\}

New field OtherInformation added to the Screening Entity Search Criteria.

• POST /api/batch
• POST /api/entity
• PUT /api/entity/\{entityId\}
• GET /api/batch/\{id\}
• GET /api/batch/journey/\{journeyId\}
• GET /api/batch/journey/\{journeyId\}/process/\{processId\}
• GET /api/batch/\{batchId\}/entity
• GET /api/batch/\{batchId\}/entity/\{entityId\}
• GET /api/entity/\{entityId\}
• POST /api/entity/getentitieslist

When calling the create batch endpoint, if the new batch is overriding any previous batches for the journey, it will now send the AdditionalSettings as part of each of the overridden batches to the adapters. Also updated the LexisNexis adapter Screen endpoint to use these AdditionalSettings for the AcceptList deletion, so entities are removed from the correct AcceptLists of the overridden batches.