We added the ability to create aggregatedRulesfor any entity type.It means that the System can now track transactions and trigger Alertsbased not only on transactions of individual Sub-Accounts but also on transactions across multiple Sub-Accounts within a specified hierarchy.
Now, when configuring the Rule, the User needs to specify the Entity Type for which the System creates Rule and aggregate transactions to calculate Alerts .
For example, if the Rule is created with entity type Platform Account, then Alerts are calculated for a specific Platform Account based on transactions processed by all Sub-Accounts under this Platform Account.
Also, for each entity level added:
Rules settings page:
Sub-Account Settings
Platform Account Settings
Service Provider Settings
Operator Settings
Alerts page:
Sub-Account Alerts
Platform Account Alerts
Service Provider Alerts
Operator Alerts
So, if the Ruleis created with entity typePlatform Account, to manage settings of such Rule for a specific Platform Accountthe Userwill go to the Platform Account Settings page, and to search for triggeredAlerts, will go to the Platform Account Alerts page.