Release 5.168 

Changes & Bug Fixes

• NEW FEATURES & ENHANCEMENTS

  • New Form Collaboration with User Groups:
    • FormAssembly Classic users will see an updated form collaboration experience with the added ability to share forms with user groups. 
      
      
  • Customize Your Workflow URLs: Custom, branded URLs for workflows can now be set in workflow properties settings.
    
    
  • Export Workflow Responses: Export a CSV of a workflow’s responses to see all associated response metadata and submitted form fields.
    
    
  • Change Form Settings: Customers can now update form settings, IP Anonymization, Spam Filter, and Review before Submit from their workflows — all without changing how it behaves in other workflows or at the form level.

• BUG FIXES

  • Fixed an issue where HTML tags were displayed on repeatable links in some form builds
  • Resolved an issue where Training Templates forms were no longer working in some account setups
  • Fixed an issue where a "Something went wrong" error could appear when attempting to report access the report page of a form
  • Fixed an issue where the All Forms page in the Admin Dashboard could fail to load after searching with accented characters
  • Resolved an issue where the PayPal connector was not available for FormAssembly Atlas users
  • Fixed an issue where lang query parameters could cause a redirect to a 404
  • Resolved a character spacing issue when viewing Validation Rules
    
    

• ADDITIONAL NOTE: Form Security Enhancement — Updated Sanitation Library
  • As of this release we’ve upgraded our form content sanitization system to improve security and performance.
    1. What’s changing: Our system that validates and sanitizes CUSTOM CODE in forms is being updated to a newer version. This upgrade provides better protection against malicious code while maintaining compatibility with properly formatted custom code.
       
       
    2. What you need to know:
       1. Based on extensive testing, FormAssembly has determined that over 98% of forms in our database will experience no changes as a result of this update
       2. For the small percentage of forms affected, changes are typically minor (cosmetic adjustments like attribute quoting or whitespace)
       3. Custom code that is well-structured and non-malicious will not be affected
          
          
  • IF YOU NOTICE CUSTOM CODE HAS BEEN REMOVED FROM A FORM ON YOUR ACCOUNT:
    1. Check your form’s Revision History - Your previous custom code is preserved in earlier versions
    2. Review the removed code - The new sanitization system only removes code that is:
       1. Malformed or improperly structured
       2. Classified as potentially malicious
    3. Reformat and reapply - Correct any structural issues in your code and save it again
    4. Contact FormAssembly Support if needed - If you believe your code was incorrectly flagged, reach out to our Support team with:
       1. Your form ID
       2. The specific custom code that was removed
       3. A description of what the code was intended to do