Simple Survey Release Notes 5.18 - 5.22

  • May 12, 2025
  • Knowledge

Permalink
https://kb.vicasso.com/?kb=000005405
What's New
  • A new "Bounced" status will be used for survey records when the packaged Flow that sends the survey email fails due to bounced email addresses. Simple Survey will then retry sending the email up to 2 times (24 and 48 hours later), and the number of failed retries will be stored in the new "Send Attempt Failures" field. (5.22)
Improvements
  • Updated the "Automatically Send Survey Emails" settings for Timing & Recipients to be editable without errors showing up, even if the main toggle is disabled. This allows users to fully configure the setting and enable it at a future date when everything is ready to go live. (5.18)
  • The language auto-detection feature on the landing page has been improved to account for additional language codes. (5.19)
  • A "Send From Address" can now be selected for the "Automatically Send Flow Emails" setting for extra personalization when sending survey emails via our packaged Flow. Email addresses defined as org-wide addresses in the org can be selected. (5.22)

  • The "Survey Sent" field is now properly populated on cases when surveys are sent via our packaged Flow. (5.22)

 

Bugs Fixed
  • The "Address "Cannot read properties of undefined (reading 'split')" error that popped up when loading the Survey Builder from the tab in the app has been fixed. (5.18)
  • Fixed the issue where if an email template was created with a blank greeting or closing, it would not be updated on subsequent visits to the "Email Template" tab of the builder. (5.18)
  • Non-duplicate survey records are no longer deleted by the prevent duplicates check. (5.18)
  • Resolved the issue where exporting a survey with two picklist questions using the same Global Value Set would cause it to be added twice to the export file, resulting in failure during the import process. (5.18)
  • The "Argument cannot be null" error when importing programs with duplicate Global Value Sets no longer appears. (5.18)
  • The survey URL in the "Chat, SMS, etc." tab no longer displays the same record ID for Account, Contact, Case, and Record Owner. (5.18)
  • Survey scores are no longer populated with invalid values. (5.19)
  • Fixed the issue where the Record Ownership dropdown was always resetting to "Record Owner" in the builder despite saving the right value in the backend. (5.19)
  • The ownership assignment for objects with Master-Detail relationships now works as expected. (5.19)
  • The "Automatically Create Survey Records" feature now works with custom objects. (5.19)
  • Pop-up errors in the builder with errors similar to "[Failed to execute 'dispatchEvent' on 'EventTarget': parameter 1 is not of type 'Event'.]" when updating logos and questions no longer appear. (5.19)

  • Fixed an issue with the save actions for the "Configure Survey Object" tab of the builder, and now the "Save" button saves everything that isn't saved, and the "Save and Continue" button saves everything that wasn't saved, and directs the user to the next tab. If all tabs have already been completed at some point, the user will be redirected to the "Add Questions & Branding" tab. (5.20)
  • The "IS NOT BLANK" operator can now be used in criteria fields without any issues. (5.20)
  • Merge fields now work as expected for pre-created surveys. (5.20)
  • Enabling the toggle to bypass "Thank You" pages allows users to define a redirect URL if Lightning Web Security (LWS) is not enabled in the org. (5.20)
  • Users should no longer see the "Sorry, an error occurred. unexpected token: 'SELECT FROM'" error when opening surveys from emails or the direct link. (5.21)
  • Survey end screens should no longer be duplicated to cause issues with criteria evaluation for redirecting to different "Thank You" pages. (5.21)
  • RECAPTCHA timeouts have been reworked so that errors are correctly handled. (5.21)
  • The Human Confidence Score is now properly captured in programs that pre-create survey records. (5.21)
  • Fixed an issue where the merge field added to the question text was showing up on the landing page instead of the actual value being grabbed from Salesforce due to the Simple Survey Site Guest User's lack of access to the object and its fields. (5.22)

  • Updated the Skip Logic modal to prevent the dropdown from overflowing with long question texts. (5.22)

 

Title
Simple Survey Release Notes 5.18 - 5.22
URL Name
Simple-Survey-Release-Notes-5-18-5-22