Summary:
I am running into an error in a lower environment when trying to use validateemailaddress from People Functions plug-in and getcontentbyattribute from Content Tools plug-in. Both functions were working a few days ago and are currently working in the higher environment.
Input: a!validateEmailAddress("test@email.com") validateEmailAddress("test@email.com")
Output: "Expression evaluation error at function a!validateEmailAddress: The function a!validateEmailAddress is unavailable." ***Same error for getcontentbyattribute "Expression evaluation error at function 'validateEmailAddress': The function 'validateemailaddress' is unavailable."
Steps Already Taken
1. Update People Functions plug-in in the lower environment
2. Update Content Tools plug-in in the lower environment
3. Use different casing on the function: validateEmailAddress() & validateemailaddress()
4. ADDED: Use prefix on the function: a!validatemailaddress()
Any ideas?
Discussion posts and replies are publicly visible
Unknown said:a!validateEmailAddress(
this isn't actually the plug-in function name. it's just "validateEmailAddress()", no "a!". I get the same error when I try to run it with the (incorrect) "a!" prefix; but when I remove this, it works fine.
Generally (and maybe always, but don't quote me), plug-in functions don't have the "a!" prefix.
My mistake, was just trying out different inputs. It also does not work for me without the a! as pictured below:
Can you confirm that the environment in question definitely has the most recent version of the People Functions plug-in installed? This function is relatively new to People Functions, so if the version is out-of-date even by a little, it might not actually have it.
Note that I'm not sure why/how that would explain an apparent regression in your case, but i'd at least double check that first. I have 1.10 (which itself is slightly out-of-date) but is recent enough to have the function - i'm not sure exactly which version it was added in, without checking.
Yes, currently on version 1.15, updated by me today
Oof, that's a puzzle then. I wonder if something behind-the-scenes in your environment has gone wrong with respect to the plugin's deployment?
If you're already to the point of "scorched-earth" troubleshooting, there's one final thing I'd try before opening a support case with Appian to check out more complicated potential errors in the server: remove the plug-in completely, then reinstall it. If the error persists, then I'm officially out of ideas.
No luck :(
Appreciate your responses!
No prob - at this point I'd try a support case. They might try restarting your environment, though they may have faster things to try first, I'm not altogether sure.