July 10, 2018

Highlights

  • No More Timing Out When Building Surveys
  • Upgraded Survey Mobile View 
  • New Name, Same Great Survey Builder
  • Scheduled Start Date Column
  • New Notification When Adding Events After Study Start

Platform-Wide Updates

No More Timing Out When Building Surveys
Picture this. You are working long and hard to build a long and complex survey, only to have WTH time out on you after 30 minutes of what it thought was inactivity. (Oh the horror!) We've upgraded our survey builder to recognize activity within the builder itself, so it will no longer time out on you and make you want to punch a unicorn. (Unicorns across America are thanking us)

Upgraded Survey Mobile View
Using WTH's survey builder just got better! The survey view on mobile phones now has bigger buttons, making it easier for users to choose the correct answer.

New Name, Same Great Survey Builder
We made a tiny change to the title of internal study surveys in the drop down. It used to be called "internal survey" but it's becoming our main squeeze in terms of survey builders (sorry Qualtrics), so we are just calling it plain old "survey or form."

Scheduled Start Date Column 
We added the participant's scheduled start date to the Participants view. It used to only show actual start date. This will allow you to see when a participant is scheduled to start at a glance, without having to click into their profile! 
New Notification When Adding Events After Study Start
If you add a new event after participants have started in the study, WTH will automatically send out messaging for all days the participant has passed in the intervention. That means, potential spamming your participants (oh no!). WTH now has a new safeguard that notifies you if you go to add an event on an already started study. Still need to add the new event? No problem, here's a trick of the trade: To avoid "spamming" participants, you can disable messaging on an individual participant or study-wide level when you add an event that will be applied to participants retroactively. 

Internal Updates

  • There was a bug that prevented the creation of proper event windows for participants from different time zones (outside of EST). We fixed that!
  • We also did some developer stuff, like refactoring the filesystem operations on persistent data to use an abstraction library.
  • We accidentally names the "external ID" field "external" on the advanced settings page, we have updated that to be "external ID."