What's New at spektr

Features

Calculation nodes: stop at the first match

Rolling out now behind a feature flag: ask us to switch it on for your workspace. A new "Only evaluate until first match" toggle on the Calculation node returns the first matching segment's score instead of summing every match. The toggle is off by default, so existing nodes behave exactly as before. Timeline and score widgets mark the segments below the match as not evaluated.

What this changes for you: Nothing changes until the flag is on and the toggle is set on a node. If you model first-match lists (for example MCC or country risk lists), one Calculation node can now replace a router-and-merge setup.

Related-entity emails in the form_submit event

The form_submit webhook event now carries a relatedEntities array: for every related entity submitted with an email, you get its spektrId, email and stored name fields, plus company name and number for companies. Entities without an email are left out, duplicates within one entity field are merged, and the array is empty when no submitted entity has an email. Existing fields are unchanged, and the new structure is documented in the public webhook docs.

What this changes for you: If you consume form_submit events, you no longer need a separate lookup to reach related-entity email addresses. No change otherwise.

Improvements

Ratio conditions no longer fire on a zero base

A % of or × of rule condition whose base is zero or empty now counts as not met, for every operator. Previously, a rule like sum(outgoing) > 90% of sum(incoming) could fire for a customer with no incoming transactions at all. Backtest reports flag these cases in a new Zero base column, and real-time, periodic and backtest runs now agree.

What this changes for you: Rules stop firing when there is nothing to compare against. Expect fewer cases from ratio conditions on customers with one-sided activity.

Case ID on the case header

Every case now shows its Case ID in the header, with the full ID on hover and a copy action. Pasting the copied ID into the Cases list search takes you straight back to the case.

What this changes for you: No workflow change. Referencing a case in a message or an audit note is now a copy-paste.

Monitoring alerts named after their scenario

Monitoring alerts no longer all read "Monitoring Alert". A single-scenario alert takes the scenario's name, and an alert spanning several scenarios reads "Multiple changes detected" ("Multiple scenarios hit" for no-action alerts). The Alert type still shows Monitoring alert.

What this changes for you: Alert lists are easier to scan. If your team filters or documents alerts by the old generic name, update those references.

Granular CPR protection fields in the Scenario node

Scenario rules can now target individual CPR protection attributes: Protection Type, Status and Effective From appear as separate fields next to Protections, with date operators on Effective From. A rule matches when any protection on the person satisfies it. The existing Protections field with has changed is untouched.

What this changes for you: You can alert on the protections that matter instead of every protection change. Existing scenarios behave as before.

Duplicate rules, events and formulas in transaction rules

The delete button on each rule, event and formula in the transaction rule node is now a three-dot menu with Duplicate and Delete. Duplicate inserts a copy below the original, named with a "(duplicate)" suffix and its own ID, so building a variant no longer means re-entering every condition.

What this changes for you: Only the menu is new; everything else works as before.

Clearer categories on Dow Jones Direct alerts

Dow Jones Direct hit cards now spell out what each code on a match means: its DJ name, subject, status and the spektr category it raised, instead of raw codes. The monitoring rule dialogs also gain an info icon per category (Sanctions, PEP, Adverse media, Watchlist) explaining which DJ content lands where.

What this changes for you: No change to what fires or how categories are assigned. The labels on existing alerts are now readable.

Android SDK on Maven Central

The spektr Android SDK is now published on Maven Central, the standard public catalogue for Android libraries. Each release is signed so you can verify it comes from spektr, and new versions publish automatically.

This release also includes bug fixes, platform and performance work.

‍