FormAssembly Enterprise Form Builder API

Known Gotchas

• ⚠ SALESFORCE CONNECTOR APEX TRIGGER CONFLICTS: FormAssembly Salesforce connector may conflict with existing Salesforce Apex triggers on the target object; automated form-to-Salesforce workflows must test for Apex trigger conflicts before production deployment; Apex validation rule failures in Salesforce create form submission errors that surface as generic failure without Salesforce error detail
• ⚠ HIPAA PLAN REQUIRED FOR PHI IN FORM FIELDS: FormAssembly's standard plan is not HIPAA compliant; automated healthcare intake must use FormAssembly HIPAA plan with BAA; form submissions containing PHI on non-HIPAA plan create HIPAA compliance violation even if the data is immediately encrypted by the integrating system
• ⚠ FORM VERSIONING IMPACT ON AUTOMATED REPORTING: FormAssembly form versions create separate response datasets; automated reporting that aggregates form responses across form versions must handle schema differences between versions; field addition or removal in form update creates reporting schema mismatch for longitudinal automated analysis
• ⚠ CONDITIONAL LOGIC EVALUATION FOR REQUIRED FIELD BYPASS: FormAssembly conditional logic can make fields required based on other answers; automated form submission generation must satisfy conditional required fields; automated test submission with incomplete conditional fields fails validation without clear error about which conditional field triggered the requirement
• ⚠ WORKFLOW ROUTING APPROVAL DELAY FOR AUTOMATED INTAKE: FormAssembly workflow routing for multi-approver review creates processing delay before data reaches final destination; automated intake that requires immediate data availability in downstream system must account for approval workflow cycle time; time-sensitive automated intake (emergency healthcare intake) may require bypass route for immediate data access