Aggregate Operations AwareIM Documentation

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

[<10>]
====== Aggregate Operations ======

In the [[2000_concepts:0800_data_processing:0100_rule_evaluation:0100_context|Context]] section we have mentioned that there is one exception to the fact that //**AwareIM**// looks for instances of the business objects to work with in the Context. This exception applies to //aggregate operations//. Aggregate operations are those rule expressions that start with keywords ''EXISTS'', ''COUNT'', ''SUM'', ''MIN'', ''MAX'', ''AVG'' (see [[EXISTS Expression]] and [[3000_rule_language:0400_rule_language#aggregate_expression|Aggregate Calculations]]). When such an expression is encountered //**AwareIM**// always looks at all data available in the database and considers all instances in the database that match the conditions of the aggregate operation, not only instances in the Context. For example, 

<code aim>IF EXISTS Policy WHERE Policy.Excess > 1000 Then DoSomething </code>

Here //**AwareIM**// looks at all existing policies in the database to find out if there is any policy with excess greater than one thousand dollars.

Let us now have a look at what happens when the conditions of a rule have been met and the corresponding action(s) are triggered. See [[2000_concepts:0800_data_processing:0100_rule_evaluation:0300_action_execution|Action Execution]].