4 posts tagged with "Rules Manager"

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