0.36.0 : Sanction screening, PATCH, better agregate creation and performance improvements

Sanction screening

We've partnered with our friends at Opensanctions to add to Marble

• Real time sanction checks, fully self hosted with unlimited checks, or connecting to Opensanction pay as you go API
• Over 240 lists, available and selectable, updated several times / day, with a warning when the last refresh is older than 24h
• Configurable sensibility threshold in the settings, driving a state of the art matching algorithm using both fuzzy matching and phonetic matching
• Capacity to force the outcome of the scenario in case there's a sanction hit
• Complete case management review interface, with the detail of each hit
• Whitelisting of counterparts : you can define a unique identifier (account number, phone number...) and decide to whitelist the discarded hits to avoid repeat alerts
• Refine of the search : an operator can add additional data (after asking the customer for documents for eg) and restart the search for more precise results
  The decision API will be updated in the next release.

See also our documentation for how to deploy a sanction check scenario, and review hits, in our public documentation.

Sanction screening is a separate module sold with a specific licence, reach out to us if you'd like to know more. As part of our commitment, NGO and non profit organisations can obtain a licence key for free.

Cleaner interface for agregate building

The interface for creating agregate has been completely refurbished, clarifying the object selected, and the fields used as filters.

Patch API

A new method is available for the ingestion API : Patch
You can now update a part of the object when using this method instead or resenting the complete payload.
When creating an object, all fields set as required are still mandatory.

Performance increase

We've added agregate persistence during a scenario run. Each agregate is now calculated only once during each decision, removing DB load and accelerating scenarios using several times the same agregates in their rules

Fix

• Open API specs are now correct when downloaded from the front end
• Random crash when accessing a test run

Sanction checks screens :

New agregate creation