When using the advanced tab to link to a web site, the help link says that these are the user values that can be passed.
USER Full name of the currently logged in user
USERFIRST First name of the currently logged in user
USERID ID of the currently logged in user
USERLAST Last name of the currently logged in user
USERNAME Username of the currently logged in user
USERSPACE Login or domain prefix of the currently logged in user
USERREFERENCE External ID of the currently logged in user
The problem we have is that the logged in USERNAME value is also including the USERSPACE value when we enter $USERNAME$ in the named pair.
How do we pass only the USERNAME without the sub-domain prefix be added to the front of the Username?
For example, for a user logged in under the oneida-media sub-domain, it passes the following for the USERNAME
oneida-media/userxyz
Our receiving web site cannot find the match on username because it can only match for userxyz
Other fields on the User record are not available to pass, for example
Description or Alias Name
Comments (5)
Aileen, could you tell me the course and activity (item) ID where you are experiencing this?
Actually, this is fixed now. Back in the Sept 2014, the username variable was being prefixed with the userspace and we were not able to do a lookup in our SNAP application. Tests yesterday show that only the USERNAME (without the prefix) is being passed. This is good news.
I am happy to know it is not an issue anymore. Thanks, Aileen.
Would it be possible to allow the passing of the logged in user's EMAIL field as a parameter pair in the Advanced tab. We have a system where we want to use the email address as the login for the other system. Currently, the EMAIL field does not appear as one of the user values that can be passed. Or would it be possible to pass the logged in user DESCRIPTION field as a parameter. Why wouldn't any of the fields that are associated with a user record not be available as parameters?
Aileen, currently this is not possible. I will record it as a feature request in our system.
I am not sure why some would not be available. It is possible that some of the variables were created for specific use-cases and they did not have a need for the email address and other fields. I will check with the team.