Skip to content

v1.2.0 - Screening with LexisNexis data

Choose a tag to compare

View all tags
@Pascal-Delange Pascal-Delange released this 10 Jun 09:25
· 1 commit to main since this release
v1.2.0
d8b21d4

Features

  • Marble screening is now compatible for use with LexisNexis sanctions, PEP and adverse media lists! Access to 26M profiles, fully on-prem (no data sent to any 3rd party) & 100% compatible with continuous screening, including new advanced filters on PEP categories & secondary PEP. Reach out to the Marble sales team to explore the option.
  • Add rule builder operator to check on customer risk level (as computed from user risk scoring feature)

Improvements

  • Store a "no hit" continuous_screening row when search is completed from an updated dataset, even if no hits were found
  • Expose the (screening or regular) rule id on decision rule details in decisions public API

Bug fixes

  • Fix missing family relative field in screening hits
  • Fix screening whitelisting option no longer appearing in case of false positive hit
  • Correct error where field creation in data model was incorrectly failing in some cases
  • Fix translation issue on screening status (displaying "{{count}}")
  • "New draft" scenario was no longer navigating to the new draft version
  • Redirect to signed URL rather than streaming results through backend API for continuous screening data indexing
  • Backport new continuous screening related query params in ingestion API from /v1beta to /v1 public API
  • Using Opensanctions data, perform a search on client user data even for generic "legal entity" data (not "person" or "organization") in the datasets
  • Clearer error mesage in the interface for decision screening rule failure (all input fields empty or null)
  • Preprocessing steps (ignore words from a custom list & named entity recognition), if configured, are now blocking (an error or time out will fail the decision) + correct an error when reading custom list for preprocessing

Requires

  • Marble backend v1.2.1
  • Marble frontend v1.2.0
  • Motiva v0.9.0

Warning

Customers already using the screening feature must replace the OPENSANCTIONS_API_HOST environment variable with SCREENING_OPENSANCTIONS_API_HOST (or SCREENING_LEXISNEXIS_API_HOST if using LexisNexis lists). Same prefix to add for SCREENING_OPENSANCTIONS_AUTH_METHOD and SCREENING_OPENSANCTIONS_API_KEY.

Assets 2
Loading