AskiaDesign 5.6.1 (Not yet released)
Table of contents:
-
5.6.1
- Added a new tab in the internet settings for v6 screens - screen generation for the default controls
- Bridge between AskiaDesign desktop and Design Online for surveys using v6 screens
- Rotation of questions on merged screens now works when using chapter rotation options or Change order routing using v6 screens
- Array of Responses to support property Tags
- Added a new check box Live caption
- Added a new file type for the ADX parameter
- Added the possibility to use CultureInfo for the SetLanguage() method
- Added new AskiaScript keywords
- Changed the naming of the semi-open
- Added UserData for responses
- Added FilterByTag for responses object
- Added Publish to live survey
- Added a new setting Allow multiple debug window
- 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()
- Create a survey to provide the wizard for interactive surveys
- Trim entry codes by default
- Added search for EntryCodes and UserData in the Find dialog
- Add Collected in field and Exclude from speed detection in the right click Set questions of the treeview
- Filter the available list of surveys to only the ones not having Python scripts as routings
- Added a new settings in DOF to freeze the entrycodes automatically when saving the survey
5.6.1
Added a new tab in the internet settings for v6 screens - screen generation for the default controls
We added a new tab in the Internet settings for the survey using v6 screens named Screen generation. You can specify/select which ADC to use for each type of questions and customize their parameters.
Note: for the controls when in loop (second column), it's used for the question inside the loop when only one question is in the loop. If two or more questions are present in the loop, the not in loop column is used, assuming you would like one iteration at a time.
These new settings are also saved in your library so you can create templates with already pre-defined ADCs selected here.
Bridge between AskiaDesign Desktop and Design Online for surveys using v6 screens
Since 5.6.1, you can now import a survey QEX file created in AskiaDesign desktop (using v6 screens) in Design Online. You can also update a survey present in design online using a QEX file modified in Design desktop. And you can download a survey present in Design Online to modify it in Design desktop. And vice versa.
This tasks can be accomplished from Design desktop or Design Online.
In AskiaDesign Desktop:
Import or Update a survey from a QEX file open in design desktop to design online, File menu, Publish to Portal. If the name specified in Surveys doesn't exist in Design Online then the system will import the QEX file as new survey in Design Online. If the survey name already exist then you will be prompt to replace the existing survey.
Open a survey present in Design online in Design desktop to save as local QEX file, File menu, Open portal survey. The field needed are the same then you can do a save as to save it locally.
In Design Online:
To import a survey QEX file in design online use the Import button and select your QEX file.
To update an existing survey using a survey QEX file present locally, use the right button present in the list of surveys.
To download an existing survey present in design online use the left button (just before the update button) in the list of surveys.
Rotation of questions on merged screens now works when using chapter rotation options or Change order routing using v6 screens
Since 5.6.1, if you use v6 screens for your surveys, the rotations options present on the chapter or the routing Change order (for the questions) are now working on merged screens.
The collection of responses now support Tags property.
So you can write something like this:
Brands.Answers.Tags Has {"Luxury"}
The Tags property was only available for the response object but not the collection of responses
Added a new check box Live caption
We added a new check box Live caption on the caption element of the chapter and questions/loops for v6 screens.
This full support for the live captions in v6 screens. The HTML generation has been updated to contain the Askia-livecaption class and the DoLiveRouting recognise the captions that need updated.
Added a new file type for the ADX parameter
We added a new file type parameter for the ADCs and ADPs. In AskiaDesign, it will list all the resources available.
Added the possibility to use CultureInfo for the SetLanguage() method
We added the possibility to use CultureInfo for the SetLanguage() method so for instance:
Interview.SetLanguage("es-ES")
for Spanish - Spain
Added new AskiaScript keywords
Question object:
- .ImportClosed
- .ImportInvisibleWhenImported
- .ImportType
- .IsFirstIteration
- .IsUpperCase
- .LinkSourceQuestion
- .LinkTopLevel
- .LinkType
- .RotationSeed
- .RotationType
- .Scenarios
- .Visibility
Response object:
Language object:
Interview object:
Survey object:
Unary function:
Changed the naming of the semi-open
We changed the naming of the semi-open question to Shortcut_EntryCode instead of Shortcut_ResponseCaption when an entry code is defined
Added UserData for responses
We added a new column UserData for the responses and also the possibility to Paste only in the UserData column.
Added FilterByTag for responses object
We added a new method .FilterByTag() for the responses object in AskiaScript.
Added Publish to live survey
We added a new button in the quota view, "Publish to live survey", so we can send the updated quotas structure to the CCA.
Added a new setting Allow multiple debug window
We added a new setting "Allow multiple debug window".
When set to No (default), the routings inside a loop in debug will be shown only once at the end of the last iteration.
When set to Yes, the routings inside a loop in debug will be shown for each iteration at the end of the last iteration.
Instructions and Comments fields
- On question (GUI)
We have added two new fields - both Instructions and Comments fields are available on questions:
We also added two new options/check boxes 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.
For that we added .ShowInstructions and .ShowComments properties on the Interview object.
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)
- On question object (AskiaScript)
We added two new properties on the Question object:
- Comments - Returns the comments of the question.
- Instructions - Returns the instructions of the question.
- 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:
Exclude from Speed median
We added a new option "Exclude from speed detection" on each variable:
Collected in field
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.
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.
QuotaTreeToDo(“question1:response1;question2:response2”)
- 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()
Create a survey to provide the wizard for interactive surveys
Interactive surveys are one of the most powerful features of Askia but it’s not easy to show the power of them because we do not have a web based way of entering the responses.
This means demoing interactive surveys (usually by copy and pasting portion of a survey in DOF) is a very underwhelming experience.
So we have added a way that you could customise the way you define a wizard by making it an askia survey.
1 - Open an interactive survey (one which has definitions for {{text}} or [[Responses]]) and click “Create Wizard”
2 - You can then edit the survey, merge question on the same screen, add validation messages with routings
3 - The survey will now appear in your resources
You can re-edit-it by right clicking open
4 - If your survey had a wizard, you can now run that wizard from the command line
Design.exe "C:\MyTemplates\ProductTestWizard.qex" /runwizard /saveas:"C:\Qes\NewSurvey.qex"
If the survey does not have a wizard, a default one is created. If the wizard has no activity for 2 minutes, Design offers to abandon the process.
One you have filled all the questions of the wizard, a new survey (in our case called NewSurvey.qex) is created and the system informs you that you can close your browser.
Trim entry codes by default
We now trim the entrycodes by default in design desktop.
We trim them when we paste entry codes.
We make a verification when saving a survey that no space before or after in any entry codes.
And during the verification, we put the focus on the question and response that contains the space.
Added search for EntryCodes and UserData in the Find dialog
We added search for EntryCodes and UserData in the Find dialog.
Add Collected in field and Exclude from speed detection in the right click Set questions of the treeview
We added a new functionality in the right click in the tree view with 2 new options that can be added to several questions.
Filter the available list of surveys to only the ones not having Python scripts as routings
We added now the availability to filter only surveys without Python scrips and routings
Added a new settings in DOF to freeze the entrycodes automatically when saving the survey
We added a new settings in DOF to freeze the entrycodes automatically when saving the survey