 One feature that I want to mention, but I'm not going to really demo is that calculated values in proven rules is now saved with a type. This is useful, the calculated values used to be stored as text always. But to be able to validate the expressions properly, some of this validation in the Android app, and the same validation will happen on the maintenance app when you enter the proven rules. It will also be possible to trigger from the data administration app. And these validations are relying on the fact that we know what type each of the variables are. As you know, when you link a variable to a field or to either a data element or attract it to the attribute, the value type will be inferred from this linked element. If you use a calculated value, however, then this would be where you can now add a type. Explicitly say that this calculated value is a number, for example. There is a difference at both the validation level and also on how these are evaluated at runtime when you run the proven rule. If you end up adding two and two together, and those are both numbers, then this would result in the number four. If you add the string two to the string two, then that would instead end up as 22, which might or might not be what you wanted. So make sure in your existing instances to have a look at the value type for your proven variables, there might be some proven rule variables in your setups that now have been defaulted to text, but you want to change the number.