I don't need them in the token table, nor stored in the data...
You know how, when you're creating/editing the invitation letter, there are certain fields that can be inserted into the template (fields like firstname, lastname, email address, surveyurl, etc.). I need to be able to create some user-defined substitutable values which would be created in, and fetched from the survey's base table (not the question group or individual question tables).
I realize this is a difficult issue, because the survey's base table is used by ALL surveys, which might not need the same user-customizable variables.
The more I talk, the more this sounds like a new feature request. Perhaps I'll start another thread there, or give some thought to how I might be able to modify the existing product to fit my needs.
A bit off topic... in an earlier version of LimeSurvey, I provided code to create SHORTSURVEYURL's and modified my version of LimeSurvey to support that functionality. It was submitted through the proper channels, but I now notice it is not part of LimeSurvey 2.0+. I guess that capability was not deemed worthy of inclusion in the base product.
Oh well, more work to do...
You know how, when you're creating/editing the invitation letter, there are certain fields that can be inserted into the template (fields like firstname, lastname, email address, surveyurl, etc.). I need to be able to create some user-defined substitutable values which would be created in, and fetched from the survey's base table (not the question group or individual question tables).
I realize this is a difficult issue, because the survey's base table is used by ALL surveys, which might not need the same user-customizable variables.
The more I talk, the more this sounds like a new feature request. Perhaps I'll start another thread there, or give some thought to how I might be able to modify the existing product to fit my needs.
A bit off topic... in an earlier version of LimeSurvey, I provided code to create SHORTSURVEYURL's and modified my version of LimeSurvey to support that functionality. It was submitted through the proper channels, but I now notice it is not part of LimeSurvey 2.0+. I guess that capability was not deemed worthy of inclusion in the base product.
Oh well, more work to do...