f1refly wrote:
The survey designer won't be able to access token variables during the interview to ensure that no token related information find the way into the results.
There were many threads over the years. I've seen to sign so far that LimeSurvey developers have changed their mind about this code-design decision. The typical workaround is to use the URL to get some variables into the interview. But that's not suitable for the token data since it would be saved into the survey results. Which would make no difference than using a non-anonymous survey in the first place.
It works except for the {TOKEN}. I'm guessing this is because the survey is anonymous.
Yes, that's the current situation.Expression Manager provides read-only access to whichever variables we might need. For backwards compatibility, it provides access to the following:
TOKEN:xxx - the value of a TOKEN (e.g. TOKEN:FIRSTNAME, TOKEN:ATTRIBUTE_5) (Only for NOT anonymous survey).
manual.limesurvey.org/Expression_Manager#Access_to_VariablesTOKEN:xxx - the value of a TOKEN (e.g. TOKEN:FIRSTNAME, TOKEN:ATTRIBUTE_5) (Only for NOT anonymous survey).
The survey designer won't be able to access token variables during the interview to ensure that no token related information find the way into the results.
There were many threads over the years. I've seen to sign so far that LimeSurvey developers have changed their mind about this code-design decision. The typical workaround is to use the URL to get some variables into the interview. But that's not suitable for the token data since it would be saved into the survey results. Which would make no difference than using a non-anonymous survey in the first place.