Upcoming Depreciation of condition_parser and use of Conditional Objects

[fscholes]

With the upcoming removal of the condition_parser parameter in GX 2.0, and the move to conditional objects for row exceptions - are there plans to add support for using functions such as length, like as if writing for spark sql parser, or will we be locked to whatever the final version before 2.0 is in order to keep that functionality?

This is probably a very niche use case but we have a field that contains an identifier that has a check digit whose algorithm changed for certain populations of data points, and the only way to identify the algorithm that should have been used is the length of the identifier (assuming it is of one of two correct lengths). The length of the field was therefore used to 'split' the checks using the row exception. Being able to have a conditional object like this in v2+ would be helpful.