Jump to content

Custom Expressions - have they always been case sensitive?!


Paul Alexander
 Share

Recommended Posts

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?

 

image.png.d2611ddf1e5c217484cd3af2771575a7.png

 

Link to comment
Share on other sites

@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

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...