Skip to content

v0.53.0 - AI assist in rule creation, case manager batch actions

Choose a tag to compare

View all tags
@Pascal-Delange Pascal-Delange released this 23 Oct 11:56
· 10 commits to main since this release
v0.53.0
af9d3de

Deployment Warning

Caution

Marble v0.53 introduces a simple but important breaking change in deployment environment configuration.
Simply put:

  • The Marble frontend container now expects MARBLE_API_URL instead of MARBLE_API_URL_SERVER (with the same value: this is the url at which the frontend server can reach the backend api server)
  • The Marble backend container now expects a mandatory FIREBASE_API_KEY (it is no longer useful to set it on the frontend)

Warning

Another, more minor, breaking change is introduced on the format of accepted PostgreSQL connection strings. It remains possible to define the Postgres connection parameters via the PG_HOSTNAME, PG_PORT, PG_USER... variables OR alternatively through the PG_CONNECTION_STRING environment variable. However, if using PG_CONNECTION_STRING, only the URL format (postgresql://[user[:password]@][netloc][:port][/dbname][?param1=value1&...]) is now allowed: the "key:value" format ("host=... user=... password=...") is now explicitly rejected. This is because it is incompatible with a new feature (integrated analytics) that we are introducing soon.

Note

ℹ️ Firebase emulator specific change:
If you run the demo Marble app with the Firebase auth emulator, the frontend now also expects TEST_FIREBASE_AUTH_EMULATOR_HOST instead of FIREBASE_AUTH_EMULATOR_HOST.

More generally, only configuration strictly specific to the frontend has been kept in the frontend container. All configuration that is useful for both the frontend and backend, is now exposed by the backend for the frontend (via MARBLE_API_URL).

Further, all remaining endpoints that called the backend API directly from the app (browser side) have been modified to route through the frontend server, so it is now easier to restrict how the backend is exposed.

This week's version of Marble comes with bulk changes in the case manager and introduces AI assistance in rule building.

Features

  • We are starting to bring AI to assist in rule building ! In this release a description of the rule you're building is displayed live. It helps validate you are correctly building what you intent to, and instantly understand any rules ever created. More assistance coming soon. [only available in SaaS environment now]
  • The case manager now supports bulk changes. Select multiple cases and in one click: move them to another inbox, assign them to a user or close them all.

Improvements

  • New iteration on the Investigation AI review : improved analysis guidelines, output structure, and improved handling of cases with lots of decisions.
  • Workflows modifications now have an audit trail
  • Massive improvements on French and Arabic translations
  • Additional fields are available to refine a Screening search.
  • The screening API documentation has been fixed.
  • Improvements on the critical path of decision creation, avoiding a write-read bottleneck with degraded performance on the POST /decisions/all path
  • Simplification of Marble configuration steps - duplicated environment variables have been centralized on the backend API, some required variables that were not useful for end users have been made optional

Versions used

  • backend: europe-west1-docker.pkg.dev/marble-infra/marble/marble-backend:v0.53.3
  • frontend: europe-west1-docker.pkg.dev/marble-infra/marble/marble-frontend:v0.53.1
Assets 2
Loading