Forms
Purpose: Create, manage, and publish data collection forms with built-in workflow automation.
What You Can Do Here
- View all forms: See every form in the system with its type, status, and submission count.
- Create a new form: Click “Create Form” to start from scratch, or select a template (Contact, Newsletter, Quote Request, Product Inquiry) for pre-configured fields and workflows.
- Edit a form: Click any form to open the Form Editor where you can modify fields, settings, and workflow rules.
- Publish / Unpublish: Only published form versions are shown on the storefront. Draft versions let you make changes without affecting live forms.
- Filter by type: Use the type badges (Contact, Newsletter, Custom, etc.) to quickly find forms.
System Forms
Some forms are marked with a lock icon — these are system forms (Contact, Newsletter, Quote Request, Product Inquiry, Document Request) that are pre-configured for core business workflows. They cannot be deleted but can be customized.
Tips
- Each form has a unique key (e.g. “contact”) used to embed it on the storefront.
- Submission counts update in real time — use them to gauge form engagement.
Form Confirmation Messages
- Open a form and select Translations. Edit Confirmation message and choose Save confirmation message to update the default-language text shown after successful submission. This is a form setting, not a draft schema change; saving does not create or publish a version.
- The message accepts up to 500 plain-text characters. Clearing it restores the standard confirmation. Other settings and existing language values are preserved.
- After saving, the resource inventory refreshes. Select a language and edit successMessage; translation edits save on blur. The same field is available in Translation Center under Form or by its cms.form resource key.
- Failed saves or discovery retain the entered text. A discovery failure can occur after the source message was saved; retry to finish refreshing translations. Unified translation delivery follows the existing Resources.ReadFrom.Form setting; this editor does not enable it.
Forms Directory Navigation
- Find a form: Search its title or unique key and select a type. Filters are stored in the page URL. Clear filters resets the directory.
- Create: Create Form opens the new form directly in the editor after a successful request. The same action is available in the command palette. Keys use lowercase letters, numbers, and hyphens.
- Return to your results: Open a title or Edit, then use Back to forms or the Forms breadcrumb to return with the directory filters intact.
- Review submissions: Use Submissions for the inbox or a submission count for one form. The inbox links back to Forms and the selected form editor.
- Recover failed actions: Failed creation or deletion leaves its dialog open for correction and retry. System forms cannot be deleted.
Published Page Protection
- Check before deleting: Delete opens a published-page usage check. The final Delete action stays disabled while the check runs or if the check fails.
- Resolve published usage: Forms used by published pages cannot be deleted. The dialog lists the blocking pages with editor links, including references in nested page blocks and form actions.
- Publish the removal: Remove the form references and publish each page, or unpublish the pages. Saving a page draft alone does not remove its live reference.
- Recheck: Return to the dialog and choose Recheck usage. If the check failed, choose Retry usage check. Deletion becomes available only after a successful check finds no published references.
- Server protection: The server checks again when deleting, even after an earlier unused result. System forms remain protected regardless of page usage.
Authentication System Forms
- Open Login or Registration: CMS provisions these published system forms automatically. System forms cannot be deleted.
- Extend the page: Add fields after the locked system fields, save a draft, and publish it. The existing login and registration page layouts remain unchanged.
- Review submissions: Successful sign-in and accepted registration-verification requests submit non-credential values to the managed workflow. A registration request is not a verified account.
Protected Definition Validation
- Review a definition: Open a form and choose Validate definition. Validation reports current server requirements without saving a version or running a workflow.
- Keep changes: Correct reported issues before saving or publishing. An unavailable validation service leaves the draft intact; retry validation when the service is available.
Durable Workflow Context
- Workflow execution retains the original registered submitter and explicit step outputs. Form answers and marketing attribution remain separate.
- The Contact Us context upgrade publishes a new version while retaining previous definitions and submissions. It connects a confirmed Salesforce result to the original internal contact. Customized graphs with ambiguous paths are left unchanged for review.
- Existing submissions continue with their accepted definition. A successful HTTP submit or queued email does not alone prove Salesforce synchronization; inspect workflow completion and the contact Salesforce ID.