Filter in the case manager, and new operators

This release contains two new features :

Filters and search in the case manager

• you can now sort an inbox by case creation date (up and down)
• a search field has been added to each inbox. You can type any part of a case name to filter the list of the inbox with this value. We added a fuzzy matching to maximise the results.

New operators in agregates

The following operators can now be used within agregates : Is / Is not Null, Start with, End with.
So, for eg you can now make the sum of the transactions where the status is not NULL and the beneficiary account number starts with "GB"

A fix for a requested licence key in OSS version has been posted too.

v0.32 Product discovery & in-depth nesting

v0.32.0 drasticaly improves the way your building complex rules : you are no longer limited to one level of nesting.

Rule builder

You can now create subcalculations without limitations within each rule condition, by adding brackets to each part of the condition and allowing.
The new system is VERY flexible. You can now add multiple subcalculation to each part of a condition, using the new "modeling" menu of the toolbox.
It's now very easy to create rule such as (SUM of past transaction in last 5h ) + current transaction amount > (3x the sum of transaction amount of last month) + 5000

Discoverability & OSS

You can now see all product functionalities, even when your licence does not cover it. You can contact us in a few clicks if you want to upgrade!

Scenario homepage

Minor redesign for better accessibility

0.31.0 - Case name templates

Case name templating

In this first real product release of 2025, we are bringing proper case name templating into Marble.
When using automated workflows for decision to case, you can now template the case name using attributes from the payload or ingested data, in the same way as it's done in the rule builder. Previously, the case name would be composed of the payload object type and the object_id.
For now, this should make case viewing in the case manager inbox much easier, and with this being done, case search by name should be coming very soon.

You can access the case name templating by clicking the case name box in the scenario workflow setup page.

New year's bugfixes

This week's near year release is small, and only contains bug fixes. Stay tuned for more product-based work next week !

Bugfixes

• Fix a display error on the "is round number" operator modale, in french and arabic
• Fix a bug where the csv file name was incorrectly encoded for the "download list values as csv" feature
• Fix an error on the POST /decisions/all public API endpoint, that would return an error if any scenario matching the received object has no live version
• Upgrade a dependency with a reported vulnerability

New operators, lists loaded by CSV and lots of fix

One last one for the road !
As the end of the year is near, here's our 30th release for 2024, packed with usefulness

New operators

• Start with / end with : makes it easy to check the beginning or the end of a string against another value or list. Very useful for getting the country out of the IBAN, the phone operator suffix or the email domain name
• Is multiple of : you can now check with ease if a number is round, and set the thresholds.

Load lists by CSV

No more need to enter values manually to update lists : you can now upload CSV up to 9999 values for your lists. And if you need to update those, you can download them

Case manager

We're still chasing the clicks on the road to efficiency in the case manager

• If a case holds a single decision, it's now displayed by default

Test run

You can now stop an existing test run at any time.

Fixes :

• Unclickable part in the decision viewer
• Access to analytics for all roles
• Adding a description on an object of the data model works again

Documentation 📖

Schematics of Marble technical and functional architecture added to the repo: see the installation/deployment.md page

v0.29.1

What's Changed

• fix: version typo in docker-compose.yaml by @balzdur in #63

Full Changelog: v0.29.0...v0.29.1

Test run, new date operator and case manager efficiency

Right in time for the holidays, it's one of our largest release yet!

Test run

Modifying a scenario or a rule safely is challenging : you'll want to check the impact on detection volumes and efficiency before pushing to production.
With our test run feature, you can know modify an existing scenario, and run the new version in parallel during a set period.

Marble provides you in realtime the difference between both version, both in scenario outcome and rule by rule.
You are now able to check for abnormalities, wrong checks and volume mismatch before releasing a new version of a scenario in production. And you can keep the test run synthesis as an audit proof for the rationale behind every modification.

The test run allows you to compare a scenario version to a live one and define a maximum duration for the run.
Available for SaaS or under self-hosted licencing

Case manager efficiency

With our latest phase of case manager redesign, we're now reducing context switching with :

• Alert prioritization : a default activated toggle displays only the rules generating a hit for the case in each decisions
• Direct to decision display : the decision tab is now set as the default display when opening a case
• Foldable case history : the case timeline is accessible through a button on the right side of the screen and can be folded to save space for investigations
• Trigger object display : the trigger object is now easily accessible at the right of each linked decision
• Pivot accessibility : the pivot value has been moved to the top of each decision trigger object, making it easy to reach and copy in your own back-office.
  Those improvements should significantly reduce the number of clicks needed to overview a case and start the investigation.

We've also added the possibility to upload several files at once to a case.

Hour / Day / Month / Year operator

The builder now allows you to get an extract of a timestamp to use within rules. Based on a timestamp, you can extract the hour, the day of the week (1 = monday), the day of the month, the month of the year or the year.
It's now really easy to check if an operation happened in the middle of the night, or to integrate specific checks during weekends.
You'll need to set the timezone of your instance in the new setting / scenario tab.

Self-hosting

API timeout delays can now be configured

⚠️ API breaking change

We unfortunately had to make a breaking change to the decisions listing API. The GET /decisions endpoint no longer returns the count nested object, the start_index and the end_index of the returned items. Instead, the endpoint now returns a has_next_page boolean field that lets you know if a next pagination page is available. See our documentation page for the up-to-date details.
We absolutely hate to make breaking changes to our public API, but this was one case where the implementation proved fundamentally not scalable, on a feature that we expect was not widely used by API, and where we preferred to make the breaking change now rather than later.

Bugfixes and others

• data model tables, fields, links can now only be created in lower case alphanumeric and "_", and must start with a letter. Backward compatibility is maintained for older fields and tables, but this will avoid errors in the future
• The timeout durations for the API endpoints can now be configured, for self-hosted users of Marble. See the .env.example file for examples (use the BATCH_TIMEOUT_SECOND environment variable)
• Fix a bug where a "required" field in a table could not be added once there were objects ingested into the table. "Requiredness" is now enforced at ingestion time, not in the table itself.

---

We're not done for this year, stay tuned !

Scenario home page, null value handling in rules, UI revamp finished

Features

This week

• we added a brand new home page for every scenario. This is now the entry point to find everything related to the scenario's set up: scheduled and manual batch executions, workflows, versions... with links to the relevant documentation. In the long term, this will also make it easier for us to add more features and configuration at the scenario level.
• we added translation support for the arabic language. The app will also automatically adapt its layout (right to left) when used with the arabic locale. As before, the locale can be selected at the top-left (well, top-right in arabic) corner, next to the logout button, by clicking on the "Marble" logo. Please note that some of the translations have been added automatically by Copilot translation, so feel free to point out any corrections to us (for instance by proposing a pull request). Many thanks to @Morghim for the contribution.
• we now allow to gracefully handle NULL values (and empty string) during the rule execution, by using the "is empty"/"is not empty" operators ! See the screenshots below, documentation will be added shortly for this feature here

Improvements

We also finished a UI revamp that had been in the works for a few weeks. The case manager and scenario page now have a refreshed look, to make some features more easily discoverable (e.g. rule snoozing from the case manager), and also to make place on the screen for future features we want to add.

Bugfixes

• Batch executions of a scenario now properly make all decisions with the scenario version defined on the batch, instead of using the currently live version
• Better line breaking on long rule names
• PG_PASSWORD etc environment variables are no longer required if PG_CONNECTION_STRING is passed
• thresholds for decisions are now capped at -10000 / + 10000, and the limit is enforced in the builder

Some illustrations

New scenario home page

Revamped case manager views

Null value handling in rules

Creating the rule

Decisions with the rule

0.27.0

This week's release contains more bugfixes and small improvements

We are working on the next big feature, coming soon !

App

• layout improvements
• better (formatted) display of timestamps in rule executions
• no longer possible to create a field called "id" in the data model which was causing errors (the name is reserved)

API

• It is now possible to configure a separate database for ingested data (separate from the main db containing organizations, scenarios, decisions, cases...). This is mostly useful for our managed service, but may be helpful for some self-hosted deployments at scale.
• Fix a bug where a scheduled execution that found no objects on which to create decisions, remained stuck in "processing" status
• You can now pass the "allowssl" parameter for the DB connection (through the PG_SSL_MODE env variable). The default value if not passed is now set to prefered (though we recommend require in production).
• Finally, you can also configure the DB connection by using the PG_CONNECTION_STRING env variable (instead of passing PG_USER, PG_PASSWORD etc separately). This can be useful as it gives you more granular control on the options passed.

UI improvements and bugfixes

This week's release is lightweight, it mostly includes improvements on some UI pages and some bug fixes (which hopefully you had not noticed).
Also contains some performance improvements if you are creating large volumes of decisions.

Stay tuned for more the next big feature in a couple of weeks !