Form Editor | IMI Life Science

Form Editor

Purpose: Design form fields, configure form behaviour, and build visual submission workflows.

Tabs

  • Fields: Drag fields from the palette (Text, Email, Phone, Select, Textarea, Checkbox, Hidden) onto the canvas. Configure labels, placeholders, validation rules, and grid layout (full width or half width).
  • Workflow: Build a visual automation pipeline that runs when someone submits the form. Drag nodes from the palette, connect them with edges, and configure each step.
  • Settings: Configure the form key, success message, redirect URL, and other options.
  • Preview: See how the form will look to visitors.

Workflow Editor

The workflow editor lets you create multi-step automations triggered by form submissions:

  • Trigger: Every workflow starts with a trigger node (added automatically).
  • Conditions: Branch the workflow based on field values (e.g. if email contains @corp.com).
  • Filters: Stop the workflow if a condition is not met (e.g. spam detection).
  • Transformers: Modify submission data (extract domain, uppercase, trim).
  • Email: Send an email to the submitter or a specific address using a mail template.
  • Notify Admins: Send a notification to all admin users.
  • Salesforce: Push the submission as a lead to Salesforce CRM (uses global credentials from Settings).
  • Webhook: Send the submission data to an external URL via HTTP POST.
  • AI Advocate: Analyse the submission using AI (e.g. lead scoring, spam detection).
  • Tag: Add tags to the submission for organisation.
  • Update Status: Change the submission status.

Tips

  • Always validate the workflow before publishing — the editor highlights missing configurations and orphan nodes.
  • Action failures do not block other actions. If Salesforce is down, emails still send.
  • Use the Debug tab to replay past submissions through the workflow and see the execution path.

Concurrent Editing

  • Automatic Locking: A lock is acquired when you start editing.
  • Read-Only Mode: If another user is editing, the page becomes read-only, and you will see their name in a banner.
  • Lock Expiry: Locks expire after 1 hour of inactivity.
  • Force Release: Administrators can unlock a page if needed.

Storefront Layout

  • Columns: Choose one to four desktop columns. The storefront progressively reduces the column count in narrow page areas, popovers, side panels, and mobile screens.
  • Field labels: Display labels above controls, beside controls when the field has enough room, or visually hide them while keeping accessible names for assistive technology.
  • Field spacing: Choose Compact, Standard, or Spacious spacing for the complete form.
  • Desktop width: Select a field and choose a span of one, two, or three columns, or a full row. Spans are safely limited to the currently available column count.
  • Live preview: The form canvas reflects the selected desktop grid and field widths before publishing.
  • Form variants: Anonymous and registered-user variants keep independent layout settings.

Country and Subdivision Fields

  • Add a country field: Choose Country Input under Input Fields to give storefront visitors a complete country selector.
  • Collect subdivisions: The storefront automatically shows a second selector when the chosen country has configured states, provinces, cantons, or regions.
  • Set required values: Country and subdivision requiredness are configured independently. Subdivision validation applies only while its selector is visible.
  • Adjust field text: Customize the country placeholder and the subdivision label or placeholder for the form audience.
  • Use submitted values: Submissions retain standard country and subdivision codes for workflows and exports.

Draft Safety and Navigation

  • Save Draft: Save fields, layouts, variants, and workflow changes without changing the published form. Unsaved changes remain in the editor after a failed save or a background data refresh.
  • Leave the editor: Back to forms, Forms breadcrumbs, and Submissions offer Keep editing, Discard changes, or Save and leave when changes exist. Save and leave stays open if saving fails. Refreshing or closing a dirty browser tab uses the browser warning. Save before using unrelated sidebar links or browser-history navigation.
  • Publish: Save all changes first, then confirm Publish version. Publication replaces the visitor-facing version. An unsaved screen is never published as an older saved draft.
  • Tabs: Visual Editor, Workflow, and Translations have bookmarkable tab state. Browser history restores the selected tab without resetting the draft.
  • Registered-user variant: Anonymous and registered-user fields and layouts remain independent. Disabling the variant returns to the anonymous canvas. Saving field changes preserves an existing separate authenticated workflow.
  • History: Save or discard pending edits before opening history. The builder is disabled while history is open. A failed version load blocks editing; retry before changing the form.

Guided Salesforce Lead Mappings

  • Choose a destination: Add Salesforce field lists common Lead fields. For a custom field, enter its Salesforce API name, such as Product_Interest__c. Duplicate destinations are rejected.
  • Choose a value: Form or workflow value selects a labelled source. Fixed text sends a constant. Combined value joins editable text and source parts without JSON editing.
  • Suggest matches: Adds unambiguous form-field matches only after you select the action. Existing mappings, custom fields, and fixed values are preserved.
  • Review warnings: Missing sources stay visible and must be replaced or removed. Parallel-branch outputs may not be available when this step runs. Last name and Company are standard required Lead fields; the Salesforce organization may require additional fields.
  • Automatic fields: Unmapped destinations retain the existing automatic name, email, company, description, lead source, and status values. A custom mapping overrides that destination. Removing an override restores its automatic behavior.
  • Connection: Credentials and endpoint remain in Global Salesforce settings. This editor does not verify live connection status or load the organization schema.
  • Save and publish: Save Draft preserves the mappings with the workflow. Publish the saved form version to apply draft changes to visitor submissions. Invalid mappings stop the Salesforce step before a request is sent.

Salesforce Prospect Delivery

  • One connection: Salesforce in Connected services is the Account Engagement connection formerly named Pardot. Existing API hostnames and business-unit identifiers stay unchanged.
  • Configure delivery: Use the Salesforce Prospect API Endpoint, Business Unit ID and OAuth credentials. The old Lead API key is not required for prospect delivery. Replace the test.salesforce.com placeholder with your authorized prospect endpoint.
  • Check the result: Inspect the Salesforce step in submission details. Confirmed delivery includes a prospect ID. Missing credentials, rejected requests and unconfirmed responses fail the step; the form receipt alone does not prove Salesforce delivery.
  • Find the record: Search prospects in the configured Salesforce sandbox and Business Unit. CRM Contact or Lead synchronization is managed by Salesforce.
  • Replay carefully: Prospect synchronization upserts by email, but replaying the complete workflow can also repeat email notifications and other actions.

Switch Branches

  • Add a Switch: Choose Switch from Flow Control in a form workflow or the global workflow designer, then select the field to compare.
  • Configure cases: Give each case a clear name, select its comparison, and enter a value. Missing/null or empty-field comparisons do not need a value. A switch supports up to 20 cases.
  • Set priority: Use the arrow controls to reorder cases. The first matching case wins; later cases do not run even if they also match.
  • Connect outputs: Connect each named output and Default. Default runs when no case matches. Global switches accept one connection per output; connect subsequent actions in that branch.
  • Edit safely: Renaming and reordering preserve connections. Removing a case removes its connections. Save the draft and validate before publishing; published versions remain unchanged until publication.

Reliable Form Submissions

  • Publish before use: Visitors submit only the current published version. Required fields, consent, options and bounds are checked on the server.
  • Wizard steps: Required fields in every step are validated before submission. Invalid steps are shown for correction.
  • Files: File fields retain private attachment bytes. Configure accepted types and size limits. Each submission allows up to five files and 5 MiB combined content.
  • Automation: Submission processing is queued and checkpointed independently of the visitor request. Email actions send only their configured emails.

Form Graph and Identity Safety

  • Connections: Use acyclic connections between existing nodes. Joined actions wait for their active predecessor paths. Unselected branches do not run.
  • Filters: A normal rejected condition stops the workflow successfully. Successors are not executed or replayed.
  • Identity: Generated email field IDs populate submitter identity. If several different email values are present, select the intended Recipient field explicitly. Original submitted field IDs remain unchanged.
  • Wizard correction: A failed submission reveals an invalid step once. Visitors can use Back to correct earlier values without being forced onto the later error again.

Workflow Authoring Safety

  • Review issues: Open the workflow issue count and select a node issue to inspect it. Resolve missing or duplicate connections, cycles, disconnected nodes and switch configuration before publishing. Empty workflows remain allowed.
  • Connections: The canvas prevents self-connections, duplicate branch edges, connections into the trigger and cycles. Different branches may still connect to the same downstream node.
  • Undo and redo: Restore node settings, positions, deletions and connections together. Native text undo remains available in inputs. History is limited to the currently mounted editor.
  • Quick Setup and Clear: Replacing or clearing a graph requires confirmation. Templates replace the current graph rather than adding another trigger. Confirmed changes can be undone.
  • Compact screens: The minimap is hidden so it does not cover workflow nodes.

Form Data and Automation Handoff Steps

  • Map Fields: Assign typed variables and defaults without renaming submitted UUID field IDs.
  • Validate Data: Connect one valid and one invalid destination. Invalid business data selects a branch rather than retrying an external action.
  • Calculate, Date Operation and Collection: Configure guided operations and a non-reserved output field. Earlier outputs appear as downstream sources.
  • Publish Event: Choose an event name and explicitly mapped fields. The dedicated workflow-event-published topic carries a stable event ID and saved attribution context. Global automation can filter eventName and use data fields.
  • Long-running work: Keep durable waits, loops and parallel child workflows in global automation. Do not hold a form submission worker while waiting for an operator or event.

Locked Authentication Fields

  • Keep core fields: Login and Registration system fields cannot be edited, moved, or removed. Add your own fields after them and publish the saved draft.
  • Configure additions: Added fields share the page validation. Layout settings affect additions only. Authentication forms do not support registered-user schema variants or additional submit buttons.
  • Protect credentials: Identity handles passwords and verification. Managed submissions never contain passwords, confirmation, or tokens. Public form submissions are not an authentication or account-verification signal.
  • Handle failures: A CMS outage does not undo successful authentication. Do not retry account creation solely because a managed submission failed.

Validate Protected Definitions

  • Validate: Use the shield action to check the current fields, variants, and workflow against server policy. System forms show their owning service, operation, and contract revision.
  • Correct issues: Validation errors remain visible for the checked draft. Editing invalidates that result. Locked fields and protected operations cannot be replaced by workflow actions.
  • Save and publish: Both actions validate again. Publishing still requires a saved version and explicit confirmation. A changed draft, a replaced saved version, or leaving the editor during validation prevents a later automatic write.
  • Handle outages: Keep the current draft and retry. Validation does not create an account, submit visitor data, execute a workflow, or prove email delivery.

Edit Rich Text as HTML

  • Edit HTML: Use the code icon in an editable rich-text toolbar to open its current HTML. Visual editing remains the default, including compact fields and labels.
  • Apply: Return supported HTML to the visual editor, then use the parent record's normal Save or Publish action. Applying source alone does not save the record.
  • Supported markup: Source uses the same rich-text format as the field. Unsupported tags or attributes may be removed or normalized. Scripts, unsafe links, and event handlers are removed; existing server validation and design rules still apply.
  • Cancel: Cancel, close, or press Escape to discard the source draft. Opening source or applying unchanged source does not change the record. If content changes elsewhere while the dialog is open, cancel and reopen it before editing.
  • Mail variables: Keep placeholders such as {{firstName}} and {{accountUrl}} intact, including placeholders in link addresses. The source dialog does not expose internal variable-chip markup.
  • Read-only content: HTML editing is unavailable when the field is read-only. Plain-text fields and structured block settings are not HTML editors. A failed Apply retains the source draft for correction.

Durable Workflow Context

  • Select registered-user fields from Variables. The accepted user ID, account email and display name are captured by the server, separately from editable reply-to answers. Guests have no registered identity; older submissions may have an ID without profile details.
  • Action results are available under _context.steps.<node-id>. Salesforce exposes recordId, email, objectType, status and syncedAt after confirmed delivery. Contact actions expose contactId. Only steps that actually executed contribute results; disabled Salesforce has status skipped and no record ID.
  • Place an Add Contact step after Salesforce. Select the earlier contact in Contact target and the Salesforce step in Salesforce result. The action checks the contact and synchronized email before storing the Salesforce ID, status and timestamp.
  • Retry restores completed outputs without repeating successful external calls. Missing legacy outputs, inconsistent identity or interrupted actions require review; never clear journals or replay an uncertain provider write. Outputs are credential-free objects, limited to 64 KiB per step and 256 KiB combined.

Optional Salesforce And Field Coverage

  • Choose meaningful profile, business, consent and attribution destinations in the Salesforce mapping selector. Existing custom names remain supported.
  • Job title maps to JobTitle__c in CRM and jobTitle in Account Engagement. Website source maps to AELeadSource__c / source; CRM LeadSource maps separately to CRM_Lead_Source__c. Form comments use Form_Comments__c in Account Engagement and Description in CRM.
  • Checkbox values are booleans. Application uses an array in Account Engagement and semicolon-separated selections in CRM. Date fields use dates, not fabricated timestamps. Dropdown choices and field limits remain organization-owned.
  • A skipped Salesforce step does not skip a following local Add Contact action. Do not populate double-opt-in, scoring, routing or bounce fields from untrusted form answers.