I'm using an a!match function in an interface. I have set the 'value:' parameter of the match function to the output of an expression which outputs a list of CDTs. Subsequently, I'm using this value parameter as 'fv!value' in other parameters. However, I'm receiving the 'improperly scoped variable' warning on multiple occasions when using fv!value (not in all cases). This warning is resolved when calling the same function that is called in the 'value:' parameter over and over again. However, I would prefer to refrain from doing this because of the performance implications of calling the same function multiple times.
A code snippet is attached which shows the following: the times when fv!value is called in the 'whenTrue:' parameter (lines 6 & 14), no warning is given. When fv!value is called in the 'then:' parameter (lines 10, 20 & 23), however, a warning is issued. This does not rhyme with the expected behaviour as described in the documentation. I was hoping someone could shed a light on this!
Thank you for reading.
/* code redacted for readability */
length(fv!value) <= cons!ACE_RADIOBUTTON_DROPDOWN_DIVISION_VALUE,
Discussion posts and replies are publicly visible
I can reproduce this. It appears to be a bug.
default: a!textField(value: "def")
Can you open a support case with Appian? You could drop them a link to this thread as well, at least as a starting point.
FWIW in the future it'd be helpful to post an interface snippet (like the one i have here) that someone could simply copy/paste into a blank interface designer window, i.e. one that doesn't need environment-specific constants, rules etc, along with a screenshot of what they're expecting to see - i wasn't sure what i was looking for at first (though luckily i didn't have to go far before I saw what you mean, in this case).
Mike, thank you for your response!
I will indeed open a support case and see if Appian can help with this.
Also, thank you for your advice on the interface snippet, yours works too and is easier to copy.
Hi all! Thank you for reporting this issue. Appian is tracking this behavior in AN-204631. If your organization has any questions or concerns please open a support ticket to discuss.
This issue has been resolved in 22.4; it is specified in the release notes.
yep i'd noticed that too - i was too distracted to come back here and post it though, so thanks!
Thank you for posting Laurens!
© 2023 Appian. All rights reserved.