Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
8 replies
Subscribers
7 subscribers
Views
3237 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
AI and Rules
Unexpected behavior of fn!displayvalue() in combination with fn!error()
chetany
A Score Level 1
over 7 years ago
I observed that if you use fn!error() in the defaultValue of the fn!displayvalue() function, the fn!displayvalue() behaves different.
It always returns the error message, even if we have a match in the array and replacementarray
Eg:
with(
local!num: 1,
fn!displayvalue(
local!num,
{2,1,3,4},
{"Num2", "Num1", "Num3", "Num4"},
fn!error("default value should not be evaluated")
)
)
In the code snippet, as per the usual behavior of displayvalue(), the expected output is "Num1". But, instead it returns the error message - it means the default value gets evaluated even if we have a match - and it is returned. I believe the fn!error() functions behaves like a Java Exception or Error.
But, lets take another example of using fn!if() with fn!error()
if(3>2, "Correct", fn!error("Not Correct"))
This returns "Co...
OriginalPostID-236519
Discussion posts and replies are publicly visible
Parents
0
Josh
Certified Lead Developer
over 7 years ago
I think what is happening is Appian is trying to cast your default value to whatever type "inArray" is ahead of time. I'm guessing that trying to cast "error("some error")" just triggers the error
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Josh
Certified Lead Developer
over 7 years ago
I think what is happening is Appian is trying to cast your default value to whatever type "inArray" is ahead of time. I'm guessing that trying to cast "error("some error")" just triggers the error
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data