June 12-25, 2026 Streamline Release Notes – Streamline

Recently Released Features

Repeating Records in Form Elements — Repeating sections in forms let builders display and collect sets of child records — like invoice line items or patient visit histories — within a single Form step. Each section binds to existing workflow data, supports field validation across every instance, and gives end users add/remove controls without restarting the session. Data entered or modified in repeating sections flows directly into downstream steps, completing the round-trip data lifecycle for parent-child workflows. Top capabilities:
- Render parent-child records as full form sections with multiple field types per record
- Add new child records on the form to capture every item.
- Pre-fill repeating sections from existing workflow data so assignees review and edit instead of re-entering
- Validate fields across every repeating instance before submit so incomplete child records are caught early
Repeating Records in Data Search — The Search Data step retrieves parent records along with their related child records from connected data sources like Salesforce, SQL databases, and Airtable in a single activation. Builders choose which child relationships to include and can limit the number of records returned per relationship, keeping data volume in control. Workflows that require a complete parent-child data set activate all of it in one step, without chaining multiple searches or building custom API calls. Top capabilities:
- Search for a parent record and retrieve its related child records in a single step, without chaining searches or custom API calls
- Choose which child relationships to include so each workflow only pulls the data it needs
- Define parent-child relationships in dataset configuration, including nested relationships up to two levels deep
- Limit child records returned per relationship (e.g., "most recent 10 visits") to control activated data volume
Repeating Records in Deliver Data — The Deliver Data step saves all changes to a related group of child records in a single action. It can create new records, update existing ones, and remove records that are no longer needed. It also automatically links each child record to the correct parent record, so there is no manual setup required. Builders can clearly see what worked and what failed, which makes it easier to troubleshoot problems and manage the full parent-child data process. Top capabilities:
- Write back a complete set of modified child records to the data source in a single operation
- Persist creates, updates, and deletes for child records in one step, so the full set of workflow changes is saved
- Maintain parent-child referential integrity automatically by assigning the correct parent ID to each child record
- See per-record success and failure detail so write-back issues can be resolved without re-running the workflow blind
Repeating Records in Outbound Webhooks — Outbound webhooks transmit complete parent-child payloads, so builders can send a parent record alongside its full set of child collections to an external system in a single call. Builders choose which child relationships to include and control how nested hierarchies are structured, ensuring the receiving system gets a properly shaped JSON payload that matches what it expects. External integrations that depend on complete data sets — not just flat parent records — work end-to-end from Streamline without custom serialization logic. Top capabilities:
- Send a parent record with all its child records to an external system in a single outbound webhook payload
- Preserve the nested JSON structure authored in the webhook body so receiving systems get the hierarchy as designed
- Include multiple independent collections in one payload (e.g., line items and shipping addresses side by side)
- Render empty collections predictably as[]so receiving systems can parse results consistently every time
Hide Default Email Footer — Brand editors now include a toggle to suppress the default Intellistack name and address block from workflow emails. When the footer is hidden, it is completely absent across all outgoing workflow email types - notification steps, task assignments, shares, and quick sends. Organizations that display their own company contact information or want workflow email to read as entirely their own communication can remove the platform footer with a single setting.
Smarty Scripting in Dynamic Documents — Smarty scripting in dynamic document templates gives Builders direct access to conditional logic, inline math, and variable modifiers inside their document templates. Builders will be able to show or hide content, format field values in place, compute derived totals, and iterate over repeating records without adding separate Transform or Logic steps to the workflow. For teams migrating from Formstack Documents, existing Smarty-scripted templates can be brought into Streamline with minimal changes. With Smarty scripting you can:
- Write conditional blocks to show or hide paragraphs, table rows, and list items based on field values
- Apply variable modifiers inline to format output - uppercase, date formatting, number formatting, and more - without a separate Transform step
- Use looping to render repeating sections, like invoice line items, directly from a workflow collection
- Compute and display derived values using inline math expressions and variable assignments within the template
Omni Guided Onboarding (previously known as Role-based first login - personalized onboarding for every user) — When a new user logs in to Streamline for the first time, they receive a guided orientation tailored to their role - Admin, Builder, Manager, or Operator. The experience surfaces their permissions, highlights the actions most relevant to their responsibilities, and walks them through completing their first task. Admins can provide additional context so each user's onboarding reflects their organization's specific setup.
- Who it's for: New Streamline users logging in for the first time, and Admins who want to ensure each team member understands their role and gets productive quickly.
- Requirements: Users must have an assigned role (Admin, Builder, Manager, or Operator) in Streamline.
- Top Capabilities:
  - Show role-tailored guidance the moment a user lands on a Streamline page so they know what to do without searching docs or waiting for an SE
  - Walk new users through key setup tasks conversationally with Omni - data integrations, datasets, webhooks, quick send, adding users - so they can finish independently
  - Pick up where users left off when they return to Streamline mid-setup so progress and context are never lost
  - Send re-engagement emails that take users directly back to the task they were working on if they haven't returned
  - Send invitation reminders to users who haven't accepted yet so they can join without hunting for the original invite
Expanded Status Support in Streamline for Salesforce — Workflow session and signing statuses stay current in Streamline for Salesforce as new ones are added. The managed package now reflects Delete and Cancel session states plus sign progress statuses like Awaiting turn, Sent, In-progress, and Completed. Users can track the full lifecycle of sessions and assignments from within Salesforce with the same accuracy as Streamline.
Email Logo Position — Brands can place the logo in any of six positions - top left, top center, top right, bottom left, bottom center, or bottom right - across all workflow emails. The position is stored per brand and flows through the brand hierarchy the same way other brand settings do, so account-level defaults and workflow-level overrides behave consistently.
Complex Document Logic — Builders control which fields appear on a generated document based on the data flowing through the workflow. In both the PDF (overlay) and DOCX (dynamic) document builders, builders create rules that show or hide fields when conditions are met — grouping conditions with Any/All logic and combining multiple groups with AND/OR. Each document adapts to the situation on its own, so recipients see only the fields relevant to them and teams maintain one intelligent template instead of many one-off versions. Top capabilities:
- Show or hide document fields based on workflow data, in both the PDF (overlay) and DOCX (dynamic) builders
- Group conditions with Any/All, and combine multiple condition groups with AND/OR for precise targeting
- Build conditions from field comparisons — Equals, Does not equal, Contains, Does not contain, Is empty, Is not empty
- Maintain a single adaptive document template instead of separate versions for each scenario
Org-Wide Password Policy Controls — Admins can enforce security standards across the entire organization for any team members utilizing standard login credentials. These advanced policy settings build upon Streamline's existing security foundations, allowing for tailored account protection. Top capabilities:
- Establish a specific character minimum for passwords, with a baseline requirement of at least 12 characters
- Enforce mandatory password rotations by defining a set interval of weeks before a reset is required
- Restrict the reuse of identical credentials by determining the number of unique historical passwords the system must track
Org-Wide Session Inactivity Settings — Admins can secure sensitive data by enabling automated session inactivity detection to terminate idle user connections. When active, Streamline tracks user engagement and programmatically signs out any session that remains dormant past the designated timeout period.
Date, Time, Datetime, & Timezones — Set timezones and date/time formats per account or workflow so every step shows time the way you intend. Use static times when the moment should not shift by viewer, or timezone-aware times when it should follow local time. The same rules apply to across all your steps, reducing timezone mix-ups in critical workflows. Top capabilities:
- Set default timezones at the account, workflow, or field level, with each level overriding the one above
- Mark fields as static so a 4:00 PM Eastern surgery time always displays as 4:00 PM Eastern, regardless of viewer timezone
- Mark fields as timezone-aware so meeting times automatically convert to each viewer's local timezone
- Display a timezone label next to datetime values so end users always know which timezone they're seeing

Defect Fixes

Data Management

Fixed an issue where workflows would fail to continue when proceeding with zero search results on an optional search step.
Fixed an issue where Omni could not save an Outbound Webhook step that was configured without authentication.

Document Generation

Fixed an issue where the search functionality on the 'Assigned to you' page in Workspaces was not displaying correctly.

Forms

Fixed an issue where changes to Dropdown, Radio button, or Checkbox option choices were sometimes not saved when clicking outside the form to deselect the field.
Fixed an issue where renaming an Address or Name field from the form builder's left panel did not save.
Fixed an issue where form fields could not be deleted after being resized to a smaller width.

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

Reminder of Retiring of Original Forms Step

On July 7th, we'll be retiring the original Form step. This will 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. After July 7th, the (new) Form step will be called “Form”.

If you have automations still using the previous Form step, now is the time to migrate ahead of July 7. Learn more here.

Upcoming Defect Fixes

Data Management

Fixing an issue where changing a webhook payload structure would cause duplicate data fields to appear in subsequent workflow steps until the webhook step was recreated.

Document Generation

Fixing an issue where "Document owner" information was displayed in the Repository even when no collaboration step was included in the workflow.

Forms

Fixing an issue where prefilled file download links expire after 3 minutes, preventing recipients from downloading their pre-attached files.
Fixing an issue where resizing form fields in the builder sometimes didn't take effect on the first attempt and required a second try.

Resources

Related to