Release v1.4 - Save manual screening searches & results, various performance & UX improvements · checkmarble/marble

Features

View a full history of manual screening searches, tagged by who did it. Save the results of a relevant manual screening for later consultation.

Self-foldable sidebar, for better screen space usage
A large design system harmonization is in progress - revamping buttons, modals, panels and much more throughout the app. Part 1 is releasing in this version
All pages now reliably redirect long form UUID path params in the app to the short UUID format
Allow transactions, events tables to "belong to" several "person" tables via links: This unlocks hybrid B2B&B2C usecases where a transaction may be attached to either an organization account or a natural person account, combined with precise screening of the owner user. Any given transaction may still belong to only one user at a time.
Offload screening result details to the blob storage (using the offloading bucket, similar to rule execution details). This will serve to avoid a massive increase in Database size growth when using the screening features
Improve the performance of user search queries when processing delta files in continuous screening (requires Motiva v0.9.2+)
Marble screening now works with custom datasets alongside LexisNexis or Opensanctions data - previously this only worked as a full replacement (see doc)
Progressively rolling out (on the backend first) a release plan of Marble where we release "-rcX" tags at first, before the publicly available stable release

Reintroduce CSP which was accidentally and silently broken by the migration to tanstack start
User data links and "next case" button in app open in a new tab instead of navigating
Correct an error blocking decision workflows for decisions whose payload includes IP or GPS data
Create the attached Firebase user when seeding a first org with admin via env params
Pivot values are now soft-deleted, so that old cases cannot be unlinked from their reference customer if the data model changes
Avoid creating duplicate alerts in continuous screening in case of retries (requires Redis)
Fix "rule hit" conditions in decision to case workflows, which was broken for screening rules