FormAssembly’s October 2026 update pairs report performance and save-and-resume fixes with guidance on Salesforce connection limits and duplicate prevention. A University of North Texas deployment shows how form-driven workflows can replace an aging point system at lower cost.
What is Covered in this Article
- FormAssembly’s October 2026 update, including faster report loading, a save-and-resume lockout fix, and fixes for webhooks, file uploads, and a SAML/CAS connector.
- Support guidance on the five-connection-per-user Salesforce limit and a pattern for preventing duplicate Salesforce records.
- A University of North Texas deployment that replaced a card-swipe event check-in system with a FormAssembly workflow, reporting more than 2,200 events and over $50,000 in savings.
- Futurum survey data on buyers’ top budget confidence drivers, and what to watch as forms become triggers for Salesforce automation.
The News: On October 13, 2026, FormAssembly published its monthly Beyond the Form update, detailing product fixes, support guidance, and a customer deployment centered on FormAssembly Salesforce workflows. Report pages now load faster for forms with high response volumes, and the company fixed an issue in which automated link-checkers could trigger a form’s workflow and lock out respondents trying to resume a saved form. Other fixes address webhook handling of special characters, failed file uploads that previously appeared successful to respondents, and a SAML/CAS connector error.
The update also highlights a limit of five active FormAssembly connections to Salesforce per user; exceeding it causes Salesforce to drop the oldest active connection, which can break a working form. FormAssembly outlined a duplicate-prevention pattern that captures a campaign member ID in a hidden field, looks it up with a connector step, and routes existing registrants to a confirmation page instead of creating a new record. The company also scheduled an October 22 session on triggering Salesforce Flow from form submissions.
In a customer spotlight, the University of North Texas (UNT) replaced its aging card-swipe check-in system with a FormAssembly workflow. Any staff member can create an event in about 30 seconds without a Salesforce or FormAssembly license, and students check in in about five seconds by card swipe, QR code, or SSO login. UNT reports more than 2,200 events in just over a year and more than $50,000 in savings compared with the next-best alternative, according to the October update blog post on the company website.
FormAssembly Salesforce Workflows Win on Fixes, Not Features
Analyst Take: FormAssembly’s October release contains no headline feature, and that is what makes it worth examining. Forms are the front door to systems of record, and when FormAssembly Salesforce workflows fail, the failure rarely shows up in the form itself. It shows up downstream as missing records, duplicate contacts, or respondents locked out of an application they started.
Most of this month’s fixes target exactly those silent failure modes. That is the right priority for a vendor whose value depends on what happens after a respondent clicks submit.
Reliability Is the Product for FormAssembly Salesforce Workflows
The save-and-resume fix is instructive. Automated link-checkers, typically email security tools that open links before a person does, were triggering workflows and locking out real users. Form platforms now operate in environments full of automated traffic, and vendors must design for it rather than assume every click is human.
The file-upload change matters for a similar reason. An upload that appears to succeed but does not is a data-integrity problem, and it is far more costly to discover during case review than at the moment of submission.
The Salesforce connection guidance is the most revealing item. A five-connection limit per user, combined with silent eviction of the oldest connection, means a routine reauthorization by one administrator can break a production form. Publishing best practices helps, but I would rather see FormAssembly surface connection counts and warnings in the product. Asking customers to coordinate shared Salesforce logins manually is a governance gap, not a training issue.
Futurum’s buyer data underscores the point. In the 2H 2026 Enterprise Applications Decision Maker Survey (N=833), integration and time-to-value tied at 47.9% as the top factors that would make buyers more confident allocating budget to enterprise applications. Yet breadth of integrations ranked last as a first-rank purchase criterion, at 5.6%. Buyers assume integrations will simply work, so a connector that silently drops is the kind of failure that erodes confidence fastest.
Extension, Not Replacement, Drives the Value
The UNT deployment illustrates a view I laid out in my June 2026 report, The Hidden Moat: Why Operational Depth Defeats the ‘Build It Yourself’ Narrative, that extension rather than replacement is the winning enterprise software strategy. UNT did not buy a new event platform; it extended an existing Salesforce environment with a workflow that staff can use without a license.
That licensing detail deserves attention. When participation does not require a seat, value scales with usage rather than headcount, which is the direction buyers are pushing enterprise software pricing.
The outcome metrics are also the right kind: events created, time per check-in, and avoided cost. Buyers should still read them carefully. The $50,000 savings figure is measured against commercial alternatives that started at $50,000, so it largely reflects avoided purchase cost.
Forms as Automation Triggers
The Salesforce Flow training and the Time Technology session, which uses Salesforce data on each student’s reading level to generate personalized ESL stories in real time, point to where this category is heading. The form is becoming an event trigger for downstream automation, not only a data-collection screen.
That raises the stakes on everything this update fixes. If a form submission kicks off Flow automation or generated content, a duplicate record or a dropped connection propagates further and faster. FormAssembly’s emphasis on operational hygiene is the necessary foundation for that role, and the company will need to keep pace as its customers wire forms into more of their Salesforce automation.
See the complete October update blog post from the company for full details.
What to Watch
- Whether FormAssembly moves Salesforce connection management into the product, with visible connection counts and pre-eviction warnings, rather than relying on support documentation as customers scale multi-user form estates.
- How Salesforce’s own native data-capture and automation tooling evolves, since tighter native options could pressure third-party form vendors in Salesforce-centric deals.
- Whether more customers publish quantified outcomes like UNT’s, and whether the license-free participation model holds as event volume and administrative overhead grow.
Sources
1. Beyond the Form: October Updates from FormAssembly, FormAssembly
Declaration of generative AI and AI-assisted technologies in the writing process: This content has been generated with the support of artificial intelligence technologies. Due to the fast pace of content creation and the continuous evolution of data and information, The Futurum Group and its analysts strive to ensure the accuracy and factual integrity of the information presented. However, the opinions and interpretations expressed in this content reflect those of the individual author/analyst. The Futurum Group makes no guarantees regarding the completeness, accuracy, or reliability of any information contained herein. Readers are encouraged to verify facts independently and consult relevant sources for further clarification.
Disclosure: Futurum is a research and advisory firm that engages or has engaged in research, analysis, and advisory services with many technology companies, including those mentioned in this article. The author does not hold any equity positions with any company mentioned in this article.
Analysis and opinions expressed herein are specific to the analyst individually and data and other information that might have been provided for validation, not those of Futurum as a whole.
Read the full Futurum Group Disclosure.
Author Information
Keith Kirkpatrick is VP & Research Director, Enterprise Software & Digital Workflows for The Futurum Group. Keith has over 25 years of experience in research, marketing, and consulting-based fields.
He has authored in-depth reports and market forecast studies covering artificial intelligence, biometrics, data analytics, robotics, high performance computing, and quantum computing, with a specific focus on the use of these technologies within large enterprise organizations and SMBs. He has also established strong working relationships with the international technology vendor community and is a frequent speaker at industry conferences and events.
In his career as a financial and technology journalist he has written for national and trade publications, including BusinessWeek, CNBC.com, Investment Dealers’ Digest, The Red Herring, The Communications of the ACM, and Mobile Computing & Communications, among others.
He is a member of the Association of Independent Information Professionals (AIIP).
Keith holds dual Bachelor of Arts degrees in Magazine Journalism and Sociology from Syracuse University.
