Skip to main content

15 posts tagged with "Screening"

View All Tags

Screening – Added

A new endpoint returns the document state of every match in a batch in one call. For each match that has at least one document, it returns the number of documents provided, still in progress, failed and virus-detected, so a client can check the documents on every hit without requesting each match individually. Matches with no documents are not returned, and only match documents are counted (entity documents are not). The optional onlyBlocking query parameter (default false) limits the response to matches that have a document still in progress, failed or virus-detected, which keeps it small for very large batches. The endpoint is available to tenants where the feature is enabled and returns 403 otherwise.

The existing endpoint that returns the document state of every entity in a batch now also reports the number of failed and virus-detected documents for each entity.

A document counts as failed when its upload or processing did not complete, as virus-detected when the virus scan found malware in it, and as in progress while it is still being uploaded or scanned.

Screening – Updated

Entity responses now include a matchSummary: a per-provider breakdown of the entity's matches by resolution status (unresolved, match, no match). Clients can render batch-level summaries from a single entity list call instead of fetching every entity's matches individually. Counts are per provider, so a client that needs an entity-level total sums across the providers it cares about.

A new endpoint returns the document state of every entity in a batch in one call: for each entity, the number of documents provided and the number still in progress. Entities with no documents are included with zero counts, and only entity documents are counted (match documents are not).

Screening – Added

Virtual documents are now available for Screening in all tenants. Two new endpoints let you attach a document to a screening entity or to an individual match by supplying a link to a file hosted outside Fenergo's storage, instead of uploading the file through the signed-URL flow. The link must be an absolute https:// URL.

The document list endpoints for entities and matches now return a documentUrl field. It is populated for virtual documents and null for documents uploaded through the signed-URL flow.

Screening – Added

A new endpoint is available to evaluate the Screening Expiry snapshot for a journey. Given a journey ID and a list of process IDs, it returns the expiry status of each process's active screening batch, broken down by provider.

Screening – Added

Screening now supports uploading, reusing, and deleting documents at both the entity level and the individual match level within a batch, using the same upload-URL/reuse pattern as other document flows in the platform. New materiality endpoints let users escalate and de-escalate a materiality task on an entity, trigger aggregate entity materiality calculation for a batch, and retrieve the full materiality assessment history for an entity.

A number of existing Batch, Entity, and Match endpoints have also been extended with new fields to support this materiality workflow: journey type and main legal entity on batch creation and retrieval, entity-level materiality assessment/escalation/impacted-client details, and match-level classification data and last-actioned-by information.

Screening – Added

New V3 Entity endpoints are now available. These replace the existing V1/V2 entity endpoints and introduce two key improvements: support for multiple addresses per entity in SearchCriteria, and per-configuration-set targeting when toggling Ongoing Screening.

Additionally, the ConfigurationSetId field is now exposed in the Ongoing Screening results callback, enabling adapters to identify which configuration set a screening result belongs to.

Screening – Updated

Added validation in the receptor for the ScreenResponseDto to ensure that entities is not null. This is not a breaking change, because sending entities as null was silently failing before, but now we've improved the endpoint so it returns a 400 with the details of the error instead of silently failing down the line.

Screening – Updated

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.

Screening – Added

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 property will be used to identify who actioned the resolution of the match, i.e KYRA:Screen, Screening Provider or manually by user (manuallyByUser@test.com).

Screening – Updated

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.