6 posts tagged with "Rules Manager"

Rules Manager now supports granular permissions for detection rules, allowing access to be configured by action. Permissions can be assigned to users or teams in Security Configuration, making it possible to separate rule authoring from publishing.

Key enhancements include:

• New Rule Manager permissions for viewing lists, viewing rule details, editing drafts, running backtests, viewing backtest results, publishing, archiving, and importing/exporting draft rules
• A Submit for approval action for draft detection rules that are ready to be reviewed
• A publish approval flow where users with Rule Publish permission can Approve or Reject a submitted rule
• Rejection notes recorded in the rule activity trail, providing context for why a publish request was rejected
• Approval status surfaced on the draft rules list, with the ability to identify rules awaiting approval or recently rejected

These updates provide more control over who can perform specific Rule Manager actions and support maker-checker workflows for publishing detection rules.

User Guide Reference: [TM User Guide > Rules Manager](/user-guides/fenergo-transaction-monitoring/the-business-rule-manager

Reference lists used in rules now support multiple columns on a single master list. Instead of maintaining several near-duplicate lists (one per indicator), maintain one master list with a column for each membership indicator and pick the column to evaluate at the rule level.

Key enhancements include:

• A single master list with multiple membership-indicator columns (e.g. EEA Country, FATF Increased Monitoring, EU AML High-Risk Third Country on one country list)
• A new Column selector in the rule builder when using in reference list / not in reference list — leave empty to match the full value set
• Case-insensitive membership values — 1, Y, Yes, True, On count as members; empty, 0, N, No, False, Off do not
• Automatic rule updates for live rules when the underlying list is republished including audit logs.
• Publish-time validation that flags rules whose selected column has been removed from the latest list version, with the change recorded in the rule activity tab

Backtesting now uses schedule-driven activations to simulate rule execution more accurately. Instead of replaying every day in a selected date range, the system calculates when the rule would have executed based on its configured schedule (daily, weekly, or monthly).

Key enhancements include:

• Calendar highlights showing actual activation days

• A detailed list of activation timestamps used in the simulation

• Enforcement of activation limits:

  • Daily: up to 31 activations
  • Weekly: up to 12 activations
  • Monthly: up to 12 activations

• Date range validation based on activation count, with clear feedback if limits are exceeded

An optimisation has been implemented to ensure more robust and predictable rule execution when using the ANY-true and ALL-true operators.

As part of this optimisation, ANY-true groups will only exit the rule execution when all referenced parameters in the conditions have null values or if they all result in a 'not present' result , while ALL-true exits execution when any referenced field is null or results in a not-present result .

Fields that are present but do not meet the specified condition are evaluated normally and impact only the condition outcome, not rule execution flow.

For example :

ANY-true: (field x == a; field y == b) -> exit if x is None AND y is None ALL-true: (field x == a; field y == b) -> exit if x is None OR y is None

Calculations can now be grouped with entity data rules in the past transaction section. This enhancement supports definition of multiple aggregate/calculation groups, each with its own Entity data rule relationship, and conditional logic (Any True / All True) can be applied at the parent level for enhanced detection capabilities.

A new option where users can select when a lookback query can start from. The options are 'immediately prior to the rule execution time' or 'a specific number of days in the past'. this allows the user to exclude a certain time period or to avoid overlapping time periods, when comparing two aggregates. This enhancement allows for more flexibility in AML rule building by supporting selection of specific starting points when building a lookback query