Table of contents:
- Added Instructions and Comments fields for questions
- New AskiaScript properties on the Question object
- Added Instructions and Comments fields in Translator
- Added Exclude from Speed median calculation options on questions
- Added Collected in field on questions
- Added new askiascript keyword QuotaTreeToDo()
Added Instructions and Comments fields for questions
We have added two new fields - both Instructions and Comments fields are available on questions:
We also added two new options/checkboxes in the Internet Settings, to control the visibility of the Instructions and Comments on the page, globally for the survey:
We also made sure that AskiaScript cannot override the settings - i.e. to show or hide the instructions or the comments.
In order to do that you can use the following commands when running an AskiaScript routing:
Interview.ShowInstructions = (ShowCI Has 1)
Interview.ShowComments = (ShowCI Has 2)
New AskiaScript properties on the Question object
We added two new properties on the Question object:
- Comments - Returns the comments of the question.
- Instructions - Returns the instructions of the question.
Added Instructions and Comments fields in Translator
We added two new rows for each question, Instructions and Comments on the data grid of Translator:
We also added two new options in the export string - Exclude instructions and Exclude comments:
Added Exclude from Speed median calculation options on questions
We added a new option "Exclude from speed detection" on each variable:
Added Collected in field on questions
We added a new option "Collected in field" on each questions. We need sometimes to add data to the survey after field. This data could be very big and would hamper collection. So it’s useful to indicate that a number of questions are collected outside of Webprod / Interviewer. All sub question are also considered as stored outside.
Added new askiascript keyword QuotaTreeToDo()
We added a new askiascript keyword QuotaTreeToDo(). Sometimes you might want to query a response in the quota tree. Rather than using the algorithm which will find the matching responses and pick the max, you might want to pinpoint the exact value in the tree.
- If the hierarchy of questions and responses does not exist, the return value is DK.
- If you do not specify the response QuotaTreeToDo(“question1”), the current response for that question is used.
- If you do not specify the response QuotaTreeToDo(“question3”), and there is no current response for that question, then it returns DK.
- For multiple closed question, you should always target a specific row.
- It works also with numeric question.
- For numeric, we don’t target the range but the value so if a range between 1 (included) and 10 (not included) We can write QuotaTreeToDo(“question:1“) or QuotaTreeToDo(“question:1.55“) or QuotaTreeToDo(“question:9.99“) to retrieve the number of to do for that range.
- For single or multiple closed question, we use the index value for the response and not the entrycodes in the string of the QuotaTreeToDo()