WSC 12.00 Release Notes

In most cases randomization is a simple matter of randomizing every choice or row in a question. However, sometimes there are interesting combinations required. We've always had the ability to Block a series of choices or rows in a question, keeping them together as part of the randomization. However, many clients have asked for these blocks to be internally randomized. That is, have the general choices/rows randomized and then the items within the block randomized themselves.

Prior to this release, the choices in the block would keep their natural positions while the remainder of the choices or rows would be randomized according to their chose scheme. For example, having a series of choices and rows as follows: -

This will display as follows (highlighted for effect): -

However, you can now have the groups of choices or rows in the group randomized according to their own particular randomization scheme. To do this ensure you have a Question Access Code attached to your question: -

You can then attach Randomization Block Codes to any items you want to group within choices...

... and rows...

... and ensure you have randomization schemes set for your choices ...

... and rows.

Once these elements are in place you will have access to Choice/Row Sub-Randomization Options

Here you can enter the codes you used in the groups for choices and rows along with a code for the randomization scheme to associate with the group. The list of available randomization schemes is shown on the screen. No group code can appear more than once. If you use the same block code in both choices and rows, they will have to use the same pattern. Alternatively, ensure you have unique codes.

Once set your randomization for the blocks will be shown, allowing you to have randomization for the choices and rows and different randomization for withing the blocks.

To assist in building these structures, RANDOMCODE can now be included, as an attribute, in both CHOICES and ROWS on their text field based creation.

There are now new quick access buttons when editing a question and wanting to adjust the status of individual choices. You can now adjust the visibility, exclusivity and pegging of choices and the visibility and pegging of rows.

Simply select the choice or row and then you can toggle the feature using one of the quick access buttons.

It is now possible to apply an Email Theme to the content of an Event API Email Message. This will allow your emails from Events to be branded according to your needs. Simply select the theme you want to include.

The theme will then be displayed and used in all emails for that event.

Creating a new email theme can be done by going to Email Templates and choosing Email Themes.

In some surveys you may have a significant number of distributions. We see this regularly with clients hosting tracker studies, where they have a different phase every month, and will include participants in a new distribution. To accomodate these situations, some areas will now automatically hide closed distributions. Others will have the option to hide distributions that are closed.

In Create Email a similar link will be available. Note: Distributions that are open from a specific date are deemed as open.

You can now create filters of responses based on the percentage complete of a response that has been converted from draft. This is particularly useful if you convert a lot of draft responses and only want those that are, for example, 75% complete, rather than those that are 50% complete.

To use the option, simply choose the condition and set a percentage value to compare the response to.

You can use the condition like any condition and combine it with other conditions to create complex filters.

The "Text Grid, Single Range, Dropdown" question consists of ROWS and two ranges of CHOICES. The first range represents the standard columns for each cell in the grid. The second range represents the Dropdown List that is shown for every instance of these cells.

The ROWS and CHOICES will be structured as follows:-

and will display similar to:-

From this release onward the data in the Event API will be formatted as follows:-

ROW: Row Ordinal or Row CODE tag value
GRID: 1 referring to the GRID number if there were dual range grids

CHOICE: Primary Choice CODE tag value if it exists
VALUE: Weighting value of the Primary Choice
TEXT: Choice Text of the Primary Choice

CHOICE2: Secondary Choice CODE tag value if it exists
VALUE2: Weighting value of the Secondary Choice
TEXT2: Choice Text of the Secondary Choice

For example:-

In the preceeding example, each row has a TAG that is shown and each choice (both primary and secondary) has a CODE TAG that is shown. The secondary choice, used for the drop down list, is shown as CHOICE2, VALUE2 and TEXT2, when applicable. The example shown only requested to show the value of the choices.

Whether the TEXT, VALUES or both TEXT and VALUES are included depends on the "Event sends Response as" setting in the EVENT.

This data structure is different to the previous releases and could be considered a breaking change. You will need to review any process that accepts Event API data with this question type.

Sometimes portals are created for specific stakeholders, where the data in quotas might be for specific segments. For example, you have obtained sample from multiple panel providers, and want to only show a specific stakeholder the numbers related to a single panel provider. It is now possible to provide quota numbers that are filtered and shown in a portal.

You can choose if Filters (when used) will affect the display of Quotas in the Portal:-

Once selected, filters will be available for Quotas shown in the Portal. Only limited columns can be shown in these circumstances. Only In-Quota and Draft numbers are displayed. You cannot use editing of quota numbers. If you choose "Only Allow Filtered Charts to be Shown" then quotas will be locked to the list of filters available and, by default, the first filter will be selected.

Fixes and Enhancements 12.00

1. [ENH] Change for Event API data and "Text Grid, Single Range, Dropdown" question (#2731)
   Breaking change for the data output from this type
2. [ENH] Sub-Randomization of grouped choices and rows (#2749)
   If you have groups of choices in a randomized choices or rows question, those can be sub-randomized
3. [ENH] Allow Event API Email Events to use Email Themes (#2857)
   Event API Email Events can now use Email Themes to wrap the content.
4. [ENH] Toggle Choices & Rows (#2880)
   You can now toggle choices and rows for hidden, exclusive and pegged
5. [BUG] Flip Consistent Order (#2881)
   Not correctly showing additional randomization options
6. [BUG] [WHITELABEL] Add new users and 2FA (#2882)
   Adding a new person correctly assigns two-factor authentication
7. [BUG] Default and Matrix Slider (#2883)
   If using a matrix slider and you have a default value, that will be correctly selected and will override any click to select state
8. [ENH] Distribution list and closed distributions (#2885)
   Allow closed distributions to be hidden when they are closed and inactive.
9. [ENH] Allow Filtering on Converted Draft Percentage complete values (#2886)
   You can now filter on the range of completeness in addition to whether it has been converted
10. [ENH] Allow some scripting for Hierarchical questions (#2887)
    You can now perform some scripting with Hierarchical questions.
11. [ENH] [WHITELABEL] Allow translation suggestions to be hidden when processing bulk translations (#2888)
    Some white label clients would prefer no suggestions be available for translations.
12. [ENH] Speed enhancements for Choice Links browse for large numbers of links (#2892)
    When significant choice link counts exist the browse can slow down
13. [ENH] Allow RANDOMCODE to be entered in text for ROWS and CHOICES (#2893)
    Allows easier creation of choices and rows when wanting to flag particular rows or choices for randomization blocking
14. [BUG] Export of Surveys, for cross platform import, not correctly exporting images when there are images to be included (#2894)
    Export of images from filestorage not working correctly.
15. [ENH] Quotas in Portals may now be Filtered (#2895)
    You can now filter quota numbers in portals, subject to a limited selection of displayable columns
16. [BUG] Heading in response exports for File Upload questions doesnt correctly span rows (#2896)
    Multiline titles are not working as expected
17. [ENH] New log message for surveys with large numbers of questions with rows and multiple selections that may not export (#2897)
    Surveys with large number of rows and choices may fail to export due to the number of columns in Excel required. A new log will explain this technology issue caused by a limit in Excel.
18. [ENH] Changes for filtering in portals (#2898)
    Changes to control selection of filters in portals
19. [BUG] Missing image referenced for toolbar button in analysis overview (#2899)
    Incorrect image referenced so that the image does not show correctly.
20. [ENH] [CATI] [WHITELABEL] Distributions with CATI email settings and domain name limits (#2900)
    CATI Distributions now have control over the domain name selection for CATI emails.
21. [BUG] Issue with respondent tags and report headings (#2901)
    Report would not generate in some circumstances due to report headings configuration.
22. [ENH] JavaScript description in designer formatting (#2902)
    The JavaScript description text in the designer can now be formatted with wrapping, bolding, underlining, etc, for easier use.
23. [BUG] Tooltip content tags and accessible tooltips not removing some formatting(#2903)
    Tooltips need to remove formatting when shown in accessible mode.
24. [ENH] Adjust sorting order of Event API (#2904)
    Adjust sorting so titles and status are also sorted by date
25. [BUG] Choices & Comments report heading (#2905)
    Heading text font turns to black once you get past approx. 30 characters so it was not visible
26. [BUG] Missing Resource for BI Report (#2906)
    Missing resource showed for some messages
27. [BUG] Demographic Address search style issues (#2907)
    Google search styles affecting search input fields
28. [BUG] Time zones calculation error with API2 (#2908)
    Passing of time zone not working correctly in API2
29. [BUG] View response from Event Api when the response status is changed (#2909)
    Cannot view non complete responses from Event Api