The following proposals to the Expressions spec are useful to support validation of data in exit tests, and do meaningful operations with array data within the Context (e.g. within a Contact):
Add ISNUMBER(), ISBOOL(), and ISSTRING() to support validation of data received in block exit tests
Add NULL type, and the ability to test against NULL
Add BETWEEN() function to simplify comparisons within a range
Add CONTAINS() function to enable keyword matching within strings
Array handling: ARRAY() generator function, and IN() function for testing membership within arrays. This is necessary because the context (including Contacts) has objects with array data types. A common use-case is to check if a contact is a member of a group.
Add COUNT() function for number of items in arrays.
Note: In the course of developing the open-source Flow Runner and Flow Builder implementations, the initial dev team proposed a list of cleanups and clarifications to the spec. This is one of a set of changes proposed to improve consistency, usability, and functionality of the spec based on the first complete build-outs.
The following proposals to the Expressions spec are useful to support validation of data in exit tests, and do meaningful operations with array data within the Context (e.g. within a Contact):
Note: In the course of developing the open-source Flow Runner and Flow Builder implementations, the initial dev team proposed a list of cleanups and clarifications to the spec. This is one of a set of changes proposed to improve consistency, usability, and functionality of the spec based on the first complete build-outs.