Canvas 2.0 Release and Update Notes: 30th March 2026

Modified on Mon, 30 Mar at 12:34 PM

TABLE OF CONTENTS


Studio


  • [Feature Release]: Survey Wave introduced in Pipeline allowing for time-based 'wave' distribution 
    • Each wave distribution is based on a defined collection period, and can only be active one at a time. Once the wave quotas are full, the survey link for that particular wave will be automatically locked against further use.


  • [Feature Update]: Rich-text editor removed from 'Description' field in Pipeline metadata configuration 
    • The metadata fields does not need any styling options that comes with the rich-text editor pop-up. The latest update removes this option for cleaner interface.


  • [UI Update/ Fix]: '+ Add data pipeline' button now updated to '+ Data pipeline' 
    • Updated the design for '+ Add data pipeline' button in Pipeline page, removing the word 'add'. It now reads '+ Data pipeline'.


  • [UI Update/ Fix]: The UI for the filters in Pipeline has been redesigned
    • Updated the design for the filters under Data Pipelines.
      • Previously, there were two filters: Types of data pipeline and Markets
      • It is now updated to three filters: Wave period, type of data pipeline and markets
      • Previously, to see the number of filters applied, users had to select and expand the filters. The new UI displays the number of selected filters within the filter fields, eliminating the need to click and expand each field.


  • [UI Update/ Fix]: 'Reset all' button is introduced for the filters in Pipeline 
    • The default view in Pipeline list displays all available pipeline distributions on a single page. Once filters are applied, users will see a curated list of pipeline distributions based on their selected wave period, type of data pipeline, or market filter.
    • A 'Reset to All' button is now available for users to click in order to revert the view to its default state: select all.


  • [Feature Release]: Re-Collection Settings introduced in Pipeline panel configuration allowing for automatic re-distribution based on refresh frequency set in Hub
    • A toggle is introduced in a pipeline distribution, under its Settings configuration.
      • This toggle, 'Re-Collection Settings', allows users to enable a particular pipeline distribution to participate in a refresh cycle. 
      • Enabling the toggle will result in respondents being eligible to participate in the survey again after their old answers expire, based on the refresh frequency set in Hub.


  • [Feature Release]: Clear Queue action introduced in Pipeline panel cycle UI, allowing users to reset the queue cycle
    • Added a "Clear Queue" action within the cycle interface, allowing users to reset the current cycle queue without pausing the entire pipeline, thereby enabling faster rescheduling on the same day.


  • [UI Update/ Fix]: Existing distribution cycles disappear when adding a new cycle in Pipeline panel
    • When a distribution cycle exists in the Panel pipeline, adding a new cycle causes an error; upon refresh, existing cycles disappear. This has been identified as an interface bug and does not affect the distribution cycles on the backend.
    • The known issue has since been fixed and is now working as intended.


  • [UI Update/ Fix]: Duplicate schedule lists are generated when creating a new distribution cycle in Pipeline panel
    • When adding a new schedule cycle in Panel pipeline, the system creates duplicate rows in the cycle schedule list instead of a single entry. The known issue has since been fixed and is now working as intended.


  • [UI Update/ Fix]: '3rd Party Data Config' now updated to 'Punch to Unique Link' for Pipeline email distribution
    • When email distribution is selected in Pipeline, users see a button labelled '3rd Party Data Config' on the right-hand side of the browser window. The text has now been changed to 'Punch to Unique Link' for better clarity.


Analyse


  • [Bug Update/ Fix]: Cross nesting a variable underneath a weighted column resulted in crashing tables 
    • When users attempt to cross nest a variable underneath a weighted column, it will cause the last column (right-most) to load indefinitely. The issue was observed to occur when there is a weighted column besides an unweighted column.
    • The known issue has since been fixed and is now working as intended.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article