Hi All,
I am using Interface as site page & That interface had "Assigned to" rule input, Based on loggedinuser i need to fetch data and show it in grid. So from site in Default Values i'm Passing Loggedinuser(),
But it seems to me we can't use loggedinuser in anyway while constructing a site url. Can we have another way ?
Discussion posts and replies are publicly visible
Instead of passing the 'logged-in user' from site, you can use that function on the interface itself
I am Using Same Interface to do another work , i can achieve my scenario in another way by using boolean rule input.(it's done )
BUT, I just want to know why we can't use LOGGEDINUSER in default value
We can use it check the below link and screenshot.
https://docs.appian.com/suite/help/23.4/url-parameters.html#set-up-url-parameters
We can Use loggedinuser when we constructing a URL site from another page , In my case i want loggedinuser as (DEFAULT VALUE) that we set in site object. I can call it , but in runtime output is different .
Yes, the same happened when I tried to do that not sure what is the root cause.
Why would you need it in the URL when you can just initialize a local variable that points to loggedinuser() and use that for anything relied upon by the page?
Hi, I'm a product manager at Appian. We are aware of the issue and it's not expected behavior that loggedInUser() has a different output at runtime. We are working on a releasing a fix for this soon, thanks!
sahithi.mankala Good to know .
Mike Schmitt Yeah we can do that & I did it that way. But Just curious why we can't use loggedinuser function . Sahithi clarified it
AFAIK the "loggedInUser()" function is only guaranteed to work in the way we expect it to work in the context of an interface specifically. In your case you're using it in the site configuration, which while it would be nice if it also works there, i don't believe is something we should expect. Similarly some people try to use it in a process model and it shouldn't be used there either.