April 3-16, 2026 Streamline Release Notes – Streamline

Recently Released Features

Delete Session — Workflow admins now have the ability to delete sessions that are no longer needed. Whether a session was created in error, contains test data, or is stuck in a failed state, admins remove it directly from the session management interface. This keeps the session list clean and makes it easier to focus on active, valid sessions.
Cancel Session — Workflow admins need to intervene in real time when sessions go wrong. The cancel session action stops an in-progress session, notifies affected users, and records the cancellation reason. This gives teams a clear recovery path when workflows encounter unexpected errors, replacing silent failures with deliberate, visible action.
Repeating Records in Inbound Webhooks — Streamline's Inbound Webhooks now handle repeating data natively. When an external system sends a JSON payload containing arrays of records - like an invoice with its line items, or a patient record with visit history - the webhook step detects the collections, preserves their structure, and makes them available to every downstream step in the workflow. This eliminates the need for custom integrations to pre-process complex data before it enters Streamline.
Repeating Records in Document Generation — Document Generation now handles parent-child data structures, so workflows that receive collections of records - like order line items or patient visit notes - produce fully formatted documents with dynamic tables, lists, and nested sections. Builders configure the layout once, and each generated document scales to fit the actual data, including support for multiple independent collections in a single template.
Embedding Workflows — Keep users fully immersed in your brand experience. This feature lets you embed eligible Streamline workflows in an iframe on your own website or portal using a simple code snippet. Instead of redirecting users to a Streamline page, they can complete intake forms, registrations, and multi-step processes without ever leaving your site. It's a simple, secure code snippet that delivers the full power of Streamline inside your own branded environment.
HMAC Authentication for Incoming Webhooks — You can authenticate incoming webhook calls with HMAC so only callers that know your shared secret can successfully trigger the step. That gives you stronger confidence that traffic really comes from systems you trust, and it helps reduce the risk of unwanted or fraudulent attempts to kick off a workflow.

Defect Fixes

Fixed an issue where the system would display '0 users added' instead of showing no message when no users were successfully added.
Fixed an issue where users could not select data from search results when the system was still initializing, causing selection attempts to fail with an error.
Fixed an issue where webhook security guidance was inconsistent across different areas of the interface and some help links were not working properly.
Fixed an issue where editing a form with logic rules referencing deleted fields sometimes caused an error.
Fixed an issue where clicking the 'Start new chat' button would sometimes reopen a previous conversation instead of creating a new one.
Fixed an issue where navigating from workflow suggestions was not working properly in the user interface.
Fixed an issue where email and SMS notifications could be permanently lost or get stuck in endless retry loops when delivery failed.
Fixed issues where several minor user interface and system improvements were implemented, including button text corrections, error handling enhancements, and role-based access adjustments.
Fixed an issue where users could experience blocking or delays when certain backend services were temporarily unavailable by implementing an automatic backup system.

Coming Soon

Upcoming Defect Fixes

Fixing an issue where CSV files containing 200 users could not be imported completely.
Fixing an issue where certain date formats were not handled properly on the signing page.
Fixing an issue where the signing reassignment option was not appearing in the user interface when it should be available based on the schema configuration.

Resources

Related to