v0.51.0 - AI KYC enrichment, IP whitelisting, bug fixes

Features

• Let the AI Agent to gather additional data for an analysis, by scouring the web for more infos : negative news, infos on PEP links, job or company informations and integrate those info into the case analysis
• AI agent settings page : allow for custom instructions for analysis and KYC enrichment prompts
• IP whitelisting : limit the access to Marble API and front end to a range of IP

Improvements

• Performance improvements on ingestion, decision creation #1148
• Clarifications on text in login page
• Improve docker image, reducing size
• In data model, allow field "required" update and fix bug on opening field edition with long description

Bugfixes

• Fix syntax error in downloadable openAPI for for v1 API
• Fix error on license server that prevented case auto-assignment to work for self-hosted users
• Sanitization : the app running in "test" mode with the Firebase emulator no longer gives access to the premium features in demo mode
• All inboxes are visible for org admins in case manager & settings
• Fix: "prepare" button is disabled in scenario page while indexes are being created
• Hide "Remind me later" button on closed cases

v0.50.0 - Case manager UI redesign

Release v0.50 is heavy on design improvements. Other than that, it comes with the usual dependency version upgrades and some bug fixes.

Improvements

• Major design harmonization - case manager and scenario homepage #1028
• Allow to configure output format, language in case manager AI auto-review #1132
• Fix an error on creating and viewing rule snoozes in the case manager #1055

Bugfixes

• Fix behavior of "unsnooze" button on cases #1027

v0.49.0 : Improved AI case review, workflows and screening

Features

• (beta) : AI analyst now shows proofs of its reasoning and recommendations : transactions, accounts, user mentionned, all within the case manager. Design is also greatly improved.
• Improvements on screening checks : it's now possible to allow no hits or to whitelist even on partial results. Super useful for high volume processors.
• Custom lists are now supported for screening (bring your own lists)
• Workflows now allow decisions orientation and filters linked to a specific rule hit. Eg : A decision generated because Rule A or B hit can be sent to a specific inbox. The UI has also been improved.
• IP whitelisting will soon be supported. As a preliminary step, the x-real-ip has been added to the API header.
  ⚠️ In order for it to work, it is is imperative that Marble be deployed behind a load balancer that sanitizes the x-real-ip header to avoid spoofing.

Fixes

• Inbox user creation is now possible, without having to set an admin role first
• Within workflow creation, a new inbox is instanly displayed after being created
• Correct validation of string / number in AST constants within workflows
• Help center is no longer hidden behind main menu
• Data model modifications are no longer blocked by a design flaw

Improvements

• Anonymous metrics on AI reviews

Use versions
Frontend : v0.49.1
Backend : v0.49.0

v0.48.0 Automatic case assignment

Better balance your analysts work with automatic case assignment

Investigations can pile up unevenly across teams. With Marble’s automatic case assignment, cases are distributed sequentially and fairly across active users — customizable by inboxes, permissions, and workloads.

This feature is available now, accessible in Marble Licensed plans.

See our updated documentation here

Improvements

• Backend no longer needs to be accessible from outside the customer infrastructure, except for the API (legacy and public v1.0)
• Added anonymous telemetry for screening rules
• Max file size for data upload set at 50MB

Use versions

Frontend : v0.48.1
Backend : v0.48.0

v0.47.0 Workflows & displays improvements

Going further towards complete automation, we're adding advanced workflows to Marble

Features

• Workflows : allow decisions to be oriented in series of easy to configure conditions that can use any field of the object scored, as well as the decision output to send the case to the proper inbox in the case manager.
  Super useful splitting the workload between different country teams, dedicated teams for specific alerts...
  It'll also become the ground we'll build upon to more custom actions when a decision is created.

Uses versions:

• Marble backend v0.47.4
• Marbel frontend v0.47.4

Improvements

• Display enum value options for filters in the aggregate builder #972
• Much better display of columns in the case manager data explorer. This saves space and allows to visualize more data at the same time #975
• Redesigned sign-up page #980
• Automated deletion of unused indexes on ingested data: Still in dry run mode, pending QA #919
• Our official public API v1 has been officially released ! You can find an introduction to it here, and a migration guide here. Existing customers have 6 months to make the (relatively small) changes to consume the new API version.
• Improved audit trail : more events logged
• Creating a new Marble user in your organization now also creates a Firebase user, and sends the email to set up your password automatically. #1085
• New "low" matching threshold for fuzzy text matching in rules and aggregates. #997. Please note that this low threshold is very permissive, use it with caution.
• [self-hosted] We published a better email template for the user creation and password reset email sent by Firebase. Look it up at contrib/firebase_email_reset_mail.html.

Bugfixes

• Fuzzy string matching no longer errors out the decision when given a "null" input #1077
• Restore proper version display for the backend in the help center section of the app #1081

Breaking changes

• [self-hosted] If you launch the marble backend API from the docker-compose file in the https://github.com/checkmarble/marble-backend repository (not https://github.com/checkmarble/marble), then the name of the volume used for the database has been updated and the doc along with it. There is probably no impact for customers because the https://github.com/checkmarble/marble-backend repository is mainly for internal developers, but just be careful if you are using it #1082
• [⚠️⚠️⚠️ self-hosted] Creating a new Marble user in your organization now also creates a Firebase user, and sends the email to set up your password automatically. This requires the permission to create and read users in your Firebase project for the service account used by the Marble backend. Until recently, the Marble doc recommended you use the default Firebase service account on the backend instance, in which case no further changes should be needed.

Disclaimer

From this version on, Marble will gather limited anonymous telemetry data on product usage, to help us improve the key features.

v0.46.0 - Last batch of changes to screening

Improvements

• add Content Security Policy on the frontend app #879
• simplify case investigation box event type filter by grouping types #962
• full details on relatives, positions held for PEP matches in screening review interface #932
• header row is sticky at the top for data exploration in case manager #929

Bug fixes

• do not set an error code on screening that were not run because input pre-formatting left too short an input to search #1066
• store and display the initial query (before ignore numbers/ignore terms preprocessing is applied) for screening #1068 and #958
• fix dataset display when scoping down to import only a subset of lists into yente for sanctions/PEP screening #1073
• restore display of comments left when reviewing a "block and review" decision #960
• fix broken display of decision panel in case manager when displaying contextual values, if long values are present #970

---

Screenshots

Visualize family members, positions held and associates for PEP and sanction hits

v0.45 - AI native screening = -80% false positive

Marble v0.45 brings you the most advanced options to get razor sharp screening for your payments

• Multiple screening per scenarios : set different types of screening, with dedicated parameters and lists, depending on the transaction you’re checking
• Fine tune your screening to drastically improve efficiency : remove numbers or recurring strings, select specific types of entities (companies, individuals, vehicules…) only, and avoid checking narrow strings generating noise.
• Activate the AI Name Entity Recognition for labels, removing the clutter from long strings to extract companies and individual names

Improvements

• Topics are displayed (sanctions, PEP, wanted...) on screening matches

Fix

• Details of the screenings are now also available in the decision/all endpoint
• Handle "index in creation" status when configuration data exploration from case manager

v0.44.0 - PEP & adverse media lists for screening, object annotations in case manager

New features

• You can now put notes (comments, tags, attach files) on the entities you ingested in the case manage's data viewer ! Those notes will be visible both in the investigation timeline of the case where they have been added, and in any other case related to the same user in the future. No need to switch to the main investigation screen to work, you can do most of the investigation while checking the transactions. Even better : the data you are adding stays connected to the object, and will be displayed and useable in any future investigation.

• Get access to all lists available in Opensanctions for you screening requirements: sanctions, PEP, adverse media, crypto wallets and more!

Feature improvements

• improve interface to configure decision grouping mechanism (formerly called "pivot values") in the data model

• recommend use of the latest version of yente for sanction screening

Bugfixes

• restore access link to already reviewed screening hits in case manager #916
• better persist left bar folded/unfolded state #918
• avoid error when trying to move extensions that may have been pre-created by AWS RDS managed admin user (or possibly similar on other managed databases) #1035
• more reliable whitelisting for screening checks, by better taking into account all "equivalent" ids of an entity in Opensanctions data #1040

v0.43.0 - handle Suspicious Acitivity Reports in case manager, bug fixes

Content

This version of Marble most notably adds the possibility to manage suspicious activity reports (SAR) in the case manager, by marking a case as "SAR to do" or "SAR done" and upload the file.
This is the first step on helping customers handle the full SAR workflow, as we are planning to add help on actually writing the report soon.

Bug fixes

• Allow reading from soft-deleted custom lists during scenario evaluation #1022
• Replace migration moving pg_trgm to check if we are extension owner, avoiding a bug for self-hosted AWS RDS users #1021
• Add time to list of previous cases of the customer in case manager right panel #898
• feat: persist user menu display preference (left panel folded) #899

v0.42.0 - improvements on case manager & bugfixes

This week we focus on some product improvements and bugfixes on the case manager, based on customer feedback from last week's big release.
The last missing pieces of the case manager revamp will be following next week!

Improvements

• New icons for decision outcomes, case status
• Better inbox navigation for the case manager:
  • more readable icons
  • resolved cases are now hidden by default in the inbox - optional filter to show only resolved cases
  • cases are now ordered by default by showing "waiting for action" cases (escalated to an inbox, reassigned etc) first, then by oldest cases first. Clicking on the "date" column header inverts the order.
  • new filter to show only unassigned cases
• The decisions table page now shows decisions of the past month only by default, for better response time in edge cases of filters (e.g. no rows matching, ...)

Bug fixes

• Improve translations on several parts of the case manager #883
• Case outcome (false positive, etc) no longer reset if a resolved case is reopened #881
• Navigation between inboxes properly updates the inbox if filters/pagination had already been applied #892
• Placeholder display in the case right panel if no pivot values have been configured #878
• Correct two bugs related to database field accessors in rule builder: one that caused transient errors when opening the rule page, one that caused some database field accessors to be missing in some cases (involving very nested data models) #1000
• Self-assign case on decision and sanction check review #1007
• avoid noisy logs on backend if Segment is disabled #1013