Release date: 19 April 2022
New features and / or enhancements
Possibility to set test records limit per study basis
We’re introducing new internal tools to facilitate the testing of not live studies.
Survey field to capture location from the browser API
We added a new field type to surveys with the capability to use the web browser Geolocation API to obtain participant location and populate two separate latitude/longitude fields. To enable this feature for your study, please contact customer support.
Aligning survey questions and response texts in web surveys
We’ve added the functionality to change the alignment of question and response texts in web surveys. You can now choose to align the text to the left (default) or center the text per survey step.
Hiding field numbers in web surveys
We’ve added the functionality to hide field numbers in web surveys. You can now choose to show (default) or hide the field numbers per survey step.
Enable/disable boldfacing question texts in web surveys
We’ve added the functionality to enable and disable boldfacing the question text for required fields in web surveys. You can now choose to bold face the question text if the question is required (default) or use regular font weight for all question texts per survey step.
System defects fixes
FormSync fails on dropping visit/report SDV
We've fixed an issue related to dropping verifications with Form Sync on phases and reports, which caused the entire process of merging changes with Form Sync to fail.
Test record limit is not configurable for all studies
Minor updates to the internal configuration.
When updating a field (question) in a study the step containing the updated field becomes marked as SDV automatically.
We've addressed another defect that rendered steps wrongly marked automatically by the system as source data verified, after a field in a study has been modified.
Error is displayed during SDV removing
We've fixed another defect that was occurring in some studies upon removing the already performed SDV. The cascading SDV dropping effect to all relevant steps and / or phases following this user action resulted in a 500 error being shown to the end user in the interface.
Error is displayed during step/report step copy
We've fixed a defect occurring while copying steps or report steps from the study structure that prompted an error being shown to the user.