Detailed release notes Dub Quest 6.5.0

To create a better structure, some of the classes that determine the look and feel of the questionnaires have been changed, and some classes are added. Some of the already existing classes remain the same.
To convert your style sheet to the new 6.5 version, Nebu will provide a Style Converter for this purpose. With this tool, existing style sheets can be easily converted to the new format. This is necessary because the old style sheets may cause layout problems when they are not converted.

The style converter can be opened by clicking 'Convert current style' in the 'Design' menu. The following window will popup:

In the text box below 'Old CSS style' you select the CSS file you want to convert, by clicking on the folder icon and browsing to the CSS file. In the box below 'The Resulted CSS file' you can either select an already existing file (by browsing to it with the folder icon), or type in the name of a file you want to create for this purpose. When the file doesn't exist yet, the Style Converter will create it.
There are 3 options how to include the old CSS file:

After clicking the button 'Convert', the Style Converter will start converting the CSS. The progress will be shown in the progress box. 'Save to File' will save a log file of all the actions done to a file called 'StyleConversion.log'. This file is saved in the Dub Images folder of the project.

Click here to see an overview of all the changed/added style classes (PDF).

A log will be kept of all actions done on a project, this can be seen in Dub Planner. To see the logs in Dub Planner, click on 'Quest. log overview' in the left menu, below 'Questionnaires'. In the pull down menu that shows in the right side of the screen, select the project code of which you want to see the project log and click 'Refresh'.

The list is automatically sorted on LogID number. The log list can easily be sorted on other features, by clicking on the corresponding column head.

It is possible to define a different title for each language in a project. This survey title can be defined in the 'edit language' window in the project preferences.

It is possible to export/import the format of export definitions to/from Excel. This can make it easier to edit an export definition or for example use the same export definition for multiple projects. To use this functionality, open the export definition and click on the export/import button as highlighted in the screen shot below.

Here you can choose either to export or import the export definition. When importing into an already filled export definition, the system will empty this export definition and replace it with the imported definition.

In the languages menu of Dub Quest, a checkbox is added where you can activate the ‘right to left’ mode for languages that need this setting. This gives the possibility to start at the right hand side of the page, show radio buttons/checkboxes first, then the labels etc…

For certain languages this is automatically switched on when adding this language in the ‘edit language’ window (in project preferences), for example with Arabic:

The classes needed for this option, are already defined in the (new) standard style sheet of Dub Interviewer, so no extra adjustments are needed.

When setting up a question with 'Read value from Dub Knowledge', it is now possible to use relative dates, besides absolute dates. A question with a connection to Dub Knowledge can only be used when you have selected this option in the project settings. See the image below.

When this option is selected in the project settings, an extra tab will appear in the forms, called 'Knowledge'.

In this tab you can set the parameters for using points or read data from/write data to Dub Knowledge. In the 'Read data' section you will see that the option to use relative dates is added. When you select this option, you can enter the required number of days.

Each form type now has its own unique icon, this makes it easier to distinguish them from one another.
The icons show in the form overview in the left side of the questionnaire design screen.

Instead of the standard radiobuttons or checkboxes, self-defined images can be used. To achieve this, open the project preferences and in the ‘layout’ tab, choose ‘controls’. Below is a screen shot of the window that opens and here images can be included for checkboxes or radiobuttons, or for both. The used images should be placed in the DubImages folder of the concerning project first.

It is now also possible to import Confirmit questionnaires. This option is available when choosing 'Import Design' form the 'Design' menu in Dub Quest. When the Import Wizard opens and you click 'Next', you see the option 'Confirmit (*.xml)' at the bottom of the list. When you click this option, a window will open where you can browse to the Confirmit file (in .xml format) you want to import.

In Dub Questionmaker 6.4 the swap items/labels was already possible for items popup, now this option is also available for multiple items popup.

In the Sample Management, when clicking the 'Import' button, you can choose where you want the sample to be imported from. At the top of the list, the option to import sample from Dub Knowledge is added.

When you click 'Next' a screen will open where you can select which sample/dynamic list you want to import.

Clicking 'Next' again, opens the screen where you have to match the features to sample properties.

It is also possible to load or save presets.
Features can be added by clicking the 'Feature' button and selecting the features from the tree.

The manual blocking of records is made more flexible. In the former versions of DubQuest, the only option in manually blocking was to have the InActive field of the record set to ‘0’ (not blocked) or ‘1’ (user blocked). There was one exception: the InActive field was set to ‘17’ when the record was blocked by ‘quota full’ AND ‘user blocked’.

Now users are able to define multiple reasons why a sample can be ‘user blocked’, and they can be separately be switched on and off.
When manually blocking records (with the curved arrow in Sample Management) a window will pop-up with a list of the existing blocking reasons. In this window, blocking reasons can also be switched on and off, edited and created.

A blocking reason can be switched on or off by simply clicking the checkbox in front of the blocking reason.
When creating a new blocking reason, the following window will pop-up:

Here you can define the blocking reason by giving it a description and set the condition (filter) on which sample records the blocking should apply. In other words, when the blocking reason is switched ON, then the sample records will be blocked that are in this filter.

It is now possible to define a 'name' for quota, however this name has some character limitations. Only the following characters can be used: 0..9, a..z, ' '.
This name will be used within the questionnaire, for example in expressions or quota check forms. Additionally it is possible to define a description in the quota management screen. In this screen all characters can be used. This description will be displayed in the quota overview.

When creating a new mail schedule, in the dialog a drop down for the character set is added. This drop down has the latest choice as a default.