What's New at spektr

Features

Comments are now required on D&B monitoring decisions

When you accept or reject changes detected by D&B monitoring, you now add a short comment before the decision is submitted. One comment covers the whole submission, whether you review staged changes one by one or accept or reject everything from the alert header. The comment is saved on the alert with your initials and a timestamp, so the reasoning behind each decision stays on record.

What this changes for you: Your team can no longer submit an accept or reject decision without a reason. Anyone reviewing ownership or structure changes from D&B monitoring should expect the extra required field.

Customer record lists in transaction monitoring conditions

Aggregation filters in transaction monitoring can now test a transaction field against a list stored on the customer record, using "is in" and "is not in". A rule can flag payments to countries outside the customer's own declared list, with no hard-coded values to maintain. The field picker only offers list-typed fields, and real-time, periodic and backtest runs all produce the same result.

What this changes for you: No change to existing workflows. This becomes relevant when you build monitoring rules keyed off customer-specific lists.

Connection graph changes now land on the timeline

Every link or unlink on the connection graph now writes a timeline event on both records, with who did it and when. Linking and unlinking are also restricted to users with the graph-edit permission: everyone else sees those actions blocked in the UI.

What this changes for you: Users without the graph-edit permission can no longer link or unlink entities on the connection graph. If someone on your team loses that option, check their permissions.

Improvements

Add your own conditions next to an applied matrix

Rule groups with a matrix applied are no longer read-only. You can add your own conditions alongside the matrix on Router, Scenario and Transaction Rule nodes, joined with AND/OR, and they stay in place when the matrix is re-synced.

What this changes for you: Rules that combine a matrix with extra conditions no longer need workarounds.

Select every matching transaction in the report picker

Attaching transactions to a case report now works in two steps: the header checkbox selects the current page, then a banner offers to select every transaction matching your filters across all pages. Saving attaches the full set, so a long list can no longer be filed with only its first page attached.

What this changes for you: If you attach transactions to reports, watch for the banner after ticking the header checkbox: selecting everything now takes one extra click.

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