Canvas 2.0 Release and Update Notes: 21st July 2025

TABLE OF CONTENTS

• Studio - Study Editor
• Analyse

Studio - Study Editor

• [Feature Update]: 'Primary Language' To Be Fixed Once Survey Is Published
  • The primary language of a survey will be fixed once the survey is published in Studio. (*Note: all content for related fields of the primary language must be filled before publishing the study, regardless of whether it has been tagged to a market).
  • Once the survey is published, the ability to change the primary language will be disabled accordingly. This is to prevent excess and unnecessary generation of variables that could impact reporting of the study dataset.

• [Feature Update]: Ability To Adjust End Date And Time For Schedules In Pipelines
  • Users can now adjust the end date and time of the fieldwork/ data collection schedule for their pipeline(s), which was previously not adjustable.
  • Note: By default, the period between 'start date and time' and 'end date and time' would be 14 days. Users can adjust this period but the minimum period between the two must be no less than 3 days.

• [Bug Update/ Fix]: Respondents From A Particular Segment (Set to '0') Not Being Screened Out As Expected  
  • When a respondent selects an option marked for screen out (due to the target quota of that option being set to '0' in Studio accordingly), they are still able to continue for the rest of the survey. The known issue has since been fixed and is now working as expected. 

Analyse

• [Bug Update/ Fix]: Option Variables Toggled Off In Fixed OE/ Aided OE Appearing Still In Tables
  • For fixed open-ended/ aided open-ended question types, option variables that are excluded from the filter still appear in the data table. The known issue has since been fixed and is now working as designed. 

• [Bug Update/ Fix]: Unable To Take Further Action On Custom Variables After Searching For Them On Side Panel
  •  After searching for a custom variable in the side panel, the user is unable to take further action on the custom variable (e.g. edit/ remove). The known issue has since been fixed and is now working as expected.

• [UI/UX Update/ Fix]: Text/ Prompt Box For Removal Of Custom Variable Hidden By Main Text/ Prompt Box
  • Upon triggering the removal of a custom variable, the subsequent text/ prompt box that asks the user for reconfirmation of the deletion appears behind the main text/ prompt box, preventing the user from seeing it when still on the main text/ prompt box and taking further action. The known issue has since been fixed and is now working as expected.