Custom Expressions - have they always been case sensitive?!

[Guest Paul Alexander]

This is just a 'yes/no' question really, but have the custom expressions in a BPM decision node always been case sensitive?! I've got one BPM which kept failing while looking to see if a previous node had expired or not, and the fix was to change it from 'Stage Expired == True' to 'Stage Expired =='true' (lower case)

I'm pretty sure this BPM was working for ages, but I may be wrong......so I was wondering if there's been a change?

 

 

[NeilWJ]

@Paul Alexander,

No change to the way conditions are handled but i suspect that flowcode "wait for status update" used to return Stage Expired as a string ["True"]. In which case the condition tests using lowercase. Now i have a sneaky feeling the flowcode is now returning it as a boolean [true] and the condition tests it as a boolean, not as a string.

I will ask SM team to confirm.

Cheers

[NeilWJ]

@Paul Alexander,

just checked with SM team. The param has always been a boolean type. So test value should always be either true or false ... not True or False

Cheers

[NeilWJ]

what i will do is at design time check if the selected var is a boolean and if it is only allow you to set true/false. Should save any future issues.

[Guest Paul Alexander]

Thank @NeilWJ

Thanks for that...I reckon I just inadvertently got it right by accident all the other times, and lucked out on this one BPM!