Skip to content

v1.0.0 - Customer Risk Assessment, Semantic data model, perf improvements

Choose a tag to compare

View all tags
@Pascal-Delange Pascal-Delange released this 13 May 11:39
· 3 commits to main since this release
v1.0.0
56e21d8

Features

  • Customer risk assessment fully integrated to Marble is live. Get in touch with the Marble team to activate it!
    Calculate at onboarding and update continuously one or several scores tailored for your needs, to assess each customer risk and tune your detection sensibility to that.

Improvements

  • The whole data model edition experience has been overhauled. Create tables in one batch, not field by field. Attach semantic types to tables and fields for cleaner display throughout the application, and more to come.
  • The full Marble app has been ported to a new frontend framework. Expect much better navigation performance in the short term. In the longer term, this will unlock more user experience improvements for us.
  • In case manager, show the "snooze rules" button only in cases where there are rules to snooze

Bug fixes

  • Silence a non-blocking but high volume error log about continuous screening on ingestion
  • Fix a regression that broke the auto-assignment feature silently in v0.65
  • Proper (non blocking) handling of nul value input on fuzzy string matching opereator
  • Fix blocking error in customer hub on empty name entity if searching by object_id
  • Fix readability issues of some case manager graphs in dark mode
  • Fix some UI glitches and other UI improvements on rule edition (rule name, ...)

--

Container versions

Uses:

  • Marble backend v1.0.4
  • Marble frontend v1.0.7
  • Postgres v16+
  • Motiva v0.7.4+

Breaking changes

Warning

The old, unversioned Marble public API, deprecated a year ago, is gone. See our migration guide and the v1 API documentation.

Note

Until now, Marble depended on an open-source dependency, Convoy, for webhooks dispatching. This was one additional piece of infrastructure to deploy to use the full Marble feature set. As of this version, we migrate to fully internal webhooks sending. New Marble deployments can ignore this message and just deploy without the CONVOY_ environment variables. Existing deployments should CONVOY_ environment variables while upgrading to Marble v1.0, as all existing endpoints will be automatically migrated to the new system.

Assets 2
Loading