Release v0.47.0 Workflows & displays improvements · checkmarble/marble

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.

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.

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

[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.

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