In expression rules, I have detected that you can write rule input ignoring case (ignoring whether a string is uppercase or lowercase).
But, you can define rule inputs case-sensitive.
For example: ri!code, ri!CODE
Is it correct?
Discussion posts and replies are publicly visible
Are you referring to the rule input's name or its value? If you mean the name, then yes I believe that Appian ignores case for references to the name, i.e. if your input is defined as "ri!code", then "ri!CODE" will work when calling it later, likewise with "ri!cOdE", etc. This is easy enough to demonstrate within a blank Expression Rule editor.
Yes!!
And Appian allows you to create the two rule inputs ("ri!code" and "ri!CODE").
I think, Appian should limit this type of behavior to avoid that situation.
Thanks
Indeed - interesting, I hadn't noticed that before. It seems that the second RI definition simply overrides the first one, in this case. But I'm curious, is this actually causing you some sort of issue? I can't imagine many real-world scenarios in which this would be a problem, despite it being seemingly inconsistent behavior.
To add on to this conversation, I would be hesitant to experiment too much with capitalizations while designing an application - decide on a naming convention upfront and stick to it. The one that always gets me is that case is enforced in a!queryColumn (e.g., if your field is "caseID" you can't query "caseid").
No, I detected it the other day and changed it immediately to avoid problems.