October 2025 Intellistack Streamline Release Notes

• End User Signature Reassignment — With our new signature reassignment feature, workflows keep moving even if the wrong person is initially sent a signature request, or if someone is out on PTO. Signers can now enter an email address or phone number of the new recipient, and the request will be sent out.

• Multiple In-Person Signers — For instances such as a minor accompanied by a legal guardian during a visit to the ER, it's common for multiple parties needing to sign a document in-person. This feature extends our in-person signing capabilities to accommodate multiple in-person signers.

• CLM Document Repository User Access Modal — This feature establishes the beginnings of more granular permissions for viewing documents. Admins have access to all documents, and any user who has document access can download and delete documents. Admins and Managers are also able to add or remove user access to specific documents in the repository.

• Manually Initiate Workflow in Salesforce — The Manually Initiate Workflow feature in Intellistack Streamline allows Salesforce Admins to add configurable buttons to appear directly within Salesforce record pages, giving users a native, seamless experience. With these buttons, users can launch workflows within Streamline without leaving Salesforce.

• Streamline CLM Status in Salesforce - Salesforce users can now see the progress of Streamline CLM sessions on the Salesforce record. This eliminates the need to chase down contract updates across multiple tools, providing teams with greater clarity and faster follow-up.

• New Data Classes added to sensitive data tags:

  • Filename

  • Username

  • Plaintext Password

  • Password Hash

  • Middle Initial

  • GeoCoordinates – previously Salesforce-only, now also supported in databases

Defect Fixes

• Email Notifications

  • Fixed comma handling in subject lines: Email notification subject lines now properly support commas without throwing validation errors

• Form Fields & Workflow Mapping

  • Resolved form field mapping errors: Fixed an issue where setting a field's minimum character length to blank or 0 caused errors when fetching fields for workflow mapping

  • Fixed character limit validation: Resolved validation issues that occurred when configuring form field character limits

• Workflows

  • Corrected webhook step validation: Webhook steps now properly validate example values regardless of data type (numbers, strings, etc.)

  • Fixed workflow completion display: Resolved an issue where "Unsupported Step type" messages incorrectly appeared at the end of workflows

  • Sequential signature confirmation: Users now receive proper confirmation messages after signing documents that require multiple signers

• Integrations

  • Google Sheets header row handling: Fixed an error that occurred when attempting to append rows to a Google Sheet with empty header rows

• Address Management

  • Added missing US territories: American Samoa (AS) and Northern Mariana Islands (MP) are now properly listed as US territories rather than separate countries in address fields

• Data Classification

  • Improved model accuracy: Fixed an issue where negative heading weight values could interfere with data classification certainty in edge cases

• Roles and Permissions

  • Manager role data set creation: Fixed an issue where users with the Manager role were unable to create new data sets.

• Manually Initiate Workflow in Salesforce

  • Fixed an issue where the Streamline for Salesforce managed package LWC failed to load when the **“**Use Lightning Web Security for Lightning Web Components and Aura Components” setting was disabled.

  • Resolved an issue where triggering a Streamline session from Salesforce occasionally failed to open a new session.

• Incoming Webhook

  • Fixed an issue where editing a mappable field’s data type (e.g., changing from string → number/boolean) did not persist after saving and reloading.

  • Fixed an issue where sending a test request caused the UI to exit the “listening” state and show an incorrect “No payload received” error.

  • Fixed an issue where triggering the same workflow multiple times in a short period on the same network could open the same sessions.