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

• Add alert score as a detection rule setting
• Add Alert scoring on all alert grids
• Add alert score on Alert details

Alert Grids Realignment of alert grids:

• Ensuring All Alerts, My Alerts, Grouped Alerts and Alerts with this transaction grids are aligned and contain the relevant dataset including Alert Score and Stage
• Ensuring each alert grid has the full set of available action, per row and in bulk
• Aligning sorting and filtering on each grid, default sorting by date
• Introducing saved filters
• Extend default view to 20 rows with option to extend to 50
• Include closed alerts on dashboard
• Improve bulk select usability

Transaction Grids Realignment of tramsaction grids:

• Ensuring transaction grids are aligned and uniform
• Add external id
• Add sorting and filtering, default sorting by date

Other CX Enhancements

• Add Alert Outcome chip to confirmation modal and completed alert
• Add sticky tabs to Alert dashbaord

This feature will allow clients to create alerts that are not necessarily transaction driven. Alerts can be created via API against an entity. These alerts can be assessed in alert tasks with supporting commentary and documentation.

Alert Groups​

Alert groups can be created from the All Alerts/My Alerts dashboard and viewed on the new Groups tab.

Bulk Assignment​

Alerts can be assigned in bulk.

Bulk Assessment​

Alerts which are assigned to a user can be assessed in bulk.

Entity Access layers for Alerts​

Alerts access is controlled based on entities access layers.

The TM Rule Execution API lets you trigger the execution of scheduled rules for a specific date — supporting both standard scheduled runs and targeted reruns after data or configuration corrections.

Alerts Integrated Workflow - new alerts workflow using Fenergo Alert Object, new Alerts Dashbaord with associated alerts permissions set. Configurable Alert journey. Transaction and alerts view from Entity Profile.

Placed restrictions on ID integer fields to only accept 32-bit integer values

The new set of APIs provide observability capabilities, allowing users to track the progress and outcomes of data loads and validations more effectively. This eliminates the need for extensive technical intervention, streamlining the monitoring process and improving overall system transparency.

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.