rule input naming restrictions

RE: rule input naming restrictions

Mike Schmitt — Sun, 28 Mar 2021 13:13:19 GMT

Wow, just think this has been sitting there all this time (and it seems strange to me that it hasn't gotten fixed eventually...)

RE: rule input naming restrictions

Stefan Helzle — Sat, 27 Mar 2021 16:29:43 GMT

Checked knowledge base

community.appian.com/.../kb-1098-input-variables-named-after-sail-keywords-don-t-take-the-value-that-is-assigned-to-them

RE: rule input naming restrictions

Stefan Helzle — Sat, 27 Mar 2021 16:11:40 GMT

Agreed :-)

RE: rule input naming restrictions

Mike Schmitt — Sat, 27 Mar 2021 16:10:34 GMT

[quote userid="59361" url="~/discussions/f/user-interface/20669/rule-input-naming-restrictions/80550#80550"]In my daily work I do not save into rule inputs with keyword names[/quote]

I agree - I avoid it for standard practice, however I assume there are valid use cases (and of course a programming language shouldn't *actively punish* sloppy coding, especially when it's technically correct to boot).

RE: rule input naming restrictions

Stefan Helzle — Sat, 27 Mar 2021 16:05:09 GMT

I missed the saveInto action. I had that before and I believe this is a "known behavior". And it was discussed here some time(years) ago.

In my daily work I do not save into rule inputs with keyword names. Let's say, besides "saveInto".

RE: rule input naming restrictions

Mike Schmitt — Sat, 27 Mar 2021 16:00:16 GMT

It was very simple for me to reproduce. Create a new/unsaved interface, add a text rule input called "label", set the parameters up like in any of my screenshots, then type a value into the component. Immediately upon execution of the saveInto, the text is replaced with the literal value that had been defined under the component parameter with the matching name, just like in the initial video.

RE: rule input naming restrictions

Stefan Helzle — Sat, 27 Mar 2021 15:56:24 GMT

Hm ... do you have a full example including the rule inputs for me?

I remember that there was an issue with similar named rule inputs in the past. But only in very specific situations which I cannot remember:

RE: rule input naming restrictions

Mike Schmitt — Sat, 27 Mar 2021 15:52:58 GMT

what steps did you follow when trying to reproduce? Others here seem to confirm that it affects all versions back to at least 20.3...

RE: rule input naming restrictions

fernandogonzalez — Sat, 27 Mar 2021 15:50:45 GMT

Appian 20.4

RE: rule input naming restrictions

Chris — Sat, 27 Mar 2021 15:44:42 GMT

Interesting, this issue IS present in my 20.3 environment as well..

RE: rule input naming restrictions

Mike Schmitt — Sat, 27 Mar 2021 15:02:53 GMT

As an aside, I've also just confirmed that this issue follows for the "instructions", "placeholder", "labelPosition", and "inputPurpose" parameters. And, I assume, other text-based parameters.

RE: rule input naming restrictions

Mike Schmitt — Sat, 27 Mar 2021 14:50:35 GMT

I of course can't confirm what Appian version , who posted this, is on... but i'd be curious to confirm.

RE: rule input naming restrictions

Stefan Helzle — Sat, 27 Mar 2021 09:28:59 GMT

With 20.4 it works as expected. Seems to be specific to 21.1. Did you open a support case to report this behavior?

RE: rule input naming restrictions

Mike Schmitt — Fri, 26 Mar 2021 23:28:50 GMT

I can reproduce this behavior in both a!textField() and a!paragraphField(), Appian 21.1 -- a very interesting bug. I assume it's not expected behavior.