Jisc banner

Online surveys  (formerly BOS)

Powerful, flexible online surveys

News & blog

New features: Invitation email counter; pre-population parameters

Posted: 21st November 2018

Invitation and reminder email counter

We’ve added two extra columns to the respondent list on the Survey Access Control page that flag whether or not an invitation email has been sent to each respondent and how many reminders have been issued afterwards.

We hope this will make using the integrated email tool easier and provide more clarity on how many reminders can be issued.

Using a single pre-population parameter in multiple questions

We have now made it possible to use a singleĀ pre-population parameter to populate more than just one question in your survey.

This can be a powerful new tool if combined with routing.

Imagine you have two or three different cohorts of respondents and you want each cohort to be taken down a different predetermined route in your survey, perhaps separating and connecting with each other again at multiple points. You can now use a single pre-population parameter to populate multiple hidden questions throughout the survey that can be used to route each respondent to the next appropriate point based on their cohort.

An example

A copy of the below question can be added at various common points in the survey to determine whether the respondent is in COHORT A or COHORT B. The routing function can then be used each time to determine what subsequent page each cohort should be routed to.

These questions can be hidden and a single pre-population parameter (x1 in this instance) can be used to pre-populate all of them. Without noticing, each respondent is routed at multiple points.

A survey map may look like the one below. A hidden, pre-populated question sits on each of the common ‘ALL’ pages, which then determines whether the respondent goes to a section of the survey meant for COHORT A or COHORT B.

Stay up to date

To stay up to date with the development were undertaking and to join our community visit our Development page.