How can I get the list of active and inactive users without using any plugin?
Discussion posts and replies are publicly visible
There's actually an already existing group called "All Users" that does exactly what Stefan said. It uses a rule to gather every user in the system to itself.
I don't know if this still holds true, but in the past users were flagged inactive by being placed in an "Inactive Users" group that you could find, though I can't seem to find it now.
Handy little snippet for finding all of your group IDs:
a!forEach( items: enumerate(300), expression: try( concat(fv!item, " - ", group(fv!item, "groupName")), "That's not a group" ))
You shouldn't try using try() for anything that ever might make it to production, but for your own investigation in /rule that you're going to throw away in minutes, I say knock yourself out.
is there any documentation for try()?
No! It is an internal only function. Do not use it as it could change any time without notice!
interesting.I was not aware that there is a set of "internal only" functions, but it makes sense.Just tried it in my personal sandbox and i think i got the basic idea, but yeah. We should avoid them.
Please bear in mind the part I said about it being "for your own research" and "thrown away in minutes". I'd never SAVE a rule with try() in it. I'd just test one and record the output for my notes. If you create it in /rule and just leave, then it vanishes without an object being created.
That's what I would want after getting this info. Granted, you'd have to recreate the rule every time you want to do this, but you should only want to once. Aside from the internal groups listed the first (and only?) time you run it, you'd just click on the group you wanted to know about (because you created it and it's clickable) and go to the properties.
That's what I read. It's just that there are people who just start doing it and then complain that it doesn't work anymore. That's why I always point out how I did it.
Richard Michaelis said:I was not aware that there is a set of "internal only" functions
in Appian we refer to these as Undocumented Functions - including, among others i'm forgetting, try(), sort(), e**l(), and even "lambda function who shall not be named"... once upon a time, whereContains() was also undocumented, but they eventually added it officially. I understand why they won't add some of these, though I kinda wish they'd officially add try().
"lambda function who shall not be named" is especially alarming since in the same breath you deigned to speak the name of the eval function.
Except that one has actually been mentioned here before so...
To echo what others have said (in case anyone else comes across this thread later as well), there are many functions that are used internally by software developers at Appian that are not intended to be used within Designer expressions by low-code developers. These functions are undocumented, have not been tested within Designer expressions, and their behavior can change at any time, in any release.
I strongly suggest that you do not use them, even if just during an investigation or testing, because the results can be unexpected. If you believe you have a need for one of these functions, please create a support case for a feature request and provide additional context for what your use case is.