|Summary||Sometimes it's required to leave an Askia survey to take part in an external exercise and return to Askia to complete the original survey. In such cases, it may be required to take parameters from the Askia survey to the external software or page. This article will show an example of these requirements using AskiaDesign.|
|Written for||Survey programmers, Scripters.|
Download the example .qex files in the links below:
Have a test of this example survey link below. You just need a new BrokerPanelId for each new test.
You'll notice your parameters are read from the link:
After answering Q1, you come to the Redirection page.
Here you will automatically be transferred out of the askia survey to an .asp page which can contain any respondent ids or responses:
After the allotted time you will be sent back to the next question in the askia survey:
What are the key points to note in setting this up?
- Variables required in the importation chapter
- The standby.asp file stored in the .qex's resources (just used to create an example external page, can be any external site, survey etc.)
- Then change the code in the footer of the redirection page, by editing the screen properties or on a label on the screen if using an ADP:
Initially, the ImportBackToQes variable is empty. When you leave the .asp page there is a parameter sent to the survey on reentry: &BackToQes=1 which sets the variable to be 1. The difference in value of this variable is used in the syntax of the footer for the question Redirection. If it's 1 you continue in FormAskia (the askia survey), else you go to FormRedirection (the .asp page).