...
Consider the following select statement:
Code Block | ||||
---|---|---|---|---|
| ||||
select when repeat(5, withdrawal where amount.match(#$(\d+\.\d\d)#) && amount > 100) max(m) |
Expressed in KRL, this This concept would be more verbose and difficult to understand had it been expressed any other way.
Rule conditions have the advantage of being able to take other data, aside from the events and attributes, into consideration when determining whether a rule should fire. KRL makes it easy to access data from cloud-based APIs. In addition, a number of intrinsic functions and libraries offer additional data to a KRL rule set. Consequently, conditions are important for making decisions based on user context because there's more of it available to conditions than there is in an eventex, regardless of sophistication.