Skip to main content
Contact Support

June 26 - July 9, 2026 Streamline Release Notes

Kait D.
Updated

Recent Releases

  • Unique Identifier for Session Name — Workflow builders can tag any field as a session identifier, so a recognizable label (like an email or name) shows up next to each session in the project session view. Admins control who can configure and view identifiers, and sensitive values stay masked until a builder deliberately reveals them. No more cross-referencing external records to figure out who a session belongs to.
  • Immediate response mode for incoming webhooks — Provide high-volume webhook callers a faster response once the request is authenticated, validated, and the workflow session is started, without waiting for later workflow steps to complete.
  • Improved bulk processing for Salesforce-triggered workflows:
    • Bulk webhook execution now isolates record-level failures within a chunk, so one failed record no longer causes the entire chunk to fail.
    • Bulk runs now use a dedicated Salesforce object to track processing results, giving admins clearer visibility into records processed through Salesforce-triggered workflows.
    • Automatic retry for failed records. When a record fails during bulk webhook processing, Streamline for Salesforce can automatically retry failed execution.

Sunsets & End of Life

  • Retired original Form Step — On July 7th, we retired the original Form step. This does not affect the “(new) Form” step. Since February 2026, new instances of the original Form step haven't been available to add and the (new) Form step has been ready to take its place. The (new) Form step is more intuitive, more powerful, and better aligned with how you build and automate workflows today. Since July 7th, the (new) Form step is called “Form”. Learn more here. 

Defect Fixes

Data Management

  • Fixed an issue where changing a webhook payload from a collection to a flat record caused duplicate data options to appear in later workflow steps.
  • Fixed an issue where files in a Data Search step did not work correctly when multiple file-supporting entities were configured.
  • Fixed an issue where the result table in a Data Search step was not aligned correctly.

Document Generation

  • Fixed an issue where "Document owner" information was displayed in the Repository even when no collaboration step was included in the workflow.
  • Fixed an issue where document merges would fail when a non-image file (such as a Word document) was provided for an image placeholder. The system now attempts to convert these files to images automatically.
  • Fixed an issue where the label input in the document editor lost focus on each keystroke in Firefox, making it difficult to type labels.

Forms

  • Fixed an issue where prefilled file download links expire after 3 minutes, preventing recipients from downloading their pre-attached files.
  • Fixed an issue where resizing form fields in the builder sometimes didn't take effect on the first attempt and required a second try.
  • Fixed an issue where conditionally required sections sometimes incorrectly made non-input fields required.
  • Fixed an issue where dropdown fields would not allow users to reselect the value that was actively selected.
  • Fixed an issue where file download links expired after 3 minutes.
  • Fixed an issue where workflows would fail with an error when session metadata was used within a Logic condition.
  • Fixed an issue where some Address field states were missing from the option list when configuring a Logic condition.

Streamline for Salesforce

  • Fixed an issue where the session status table pagination behaves incorrectly when sessions have been deleted in Streamline.

Coming Soon

Sunsets & End of Life

SMS in Notification Step

We are making a change to how SMS notifications work in Streamline workflows, effective July 20, 2026.

To stay compliant with messaging requirements, we are removing SMS as a delivery option from the Notification step. Going forward, the Notification step will support email only.

What this means for you:

  • If you are currently using SMS in a Notification step, those existing steps will continue to work. You will not lose functionality on steps you have already built.
  • New Notification steps will offer email as the notification channel.
  • If you want to send SMS in new workflows, use the Twilio step instead. It provides SMS delivery within your defined, compliant message templates.

This change is limited to the Notification step. It does not affect:

  • Assignment (Form and Sign) SMS
  • Share SMS
  • Account Notification SMS

Upcoming Defect Fixes

Administration

  • Fixing an issue where deleting a user account could fail with an error if multiple delete requests were made at the same time.

Data Management

  • Fixing an issue where data from nested repeating form sections was not being saved to linked child tables during form submission, resulting in incomplete records.

Document Generation

  • Fixing an issue where locale settings (such as language, date, and number formats) were not displaying correctly in repeating form sections when converting forms to signature documents.
  • Fixing an issue where changes made to documents in the document builder step would sometimes not save if the document was reopened too quickly.

Resources

Related to

Comments

0 comments

Article is closed for comments.