Frequently Asked Questions

QuikForms builds public-facing forms that write straight into Salesforce, with no code. Every submission is saved as a record in your own org, and your form data never leaves it. You drag fields onto a canvas, style the form, translate it if you need to, and publish it to a URL. Fields live in a shared library, so a field you define once can be reused on every form that needs it.

Key capabilities include:

• Visual form builder with drag-and-drop layout, multi-page forms, and an optional review page
• Reusable field library shared across forms
• Record creation forms, surveys, and chat forms that start a Messaging for In-App and Web conversation
• Multi-language forms with a visitor language picker and AI translation
• Styling with 8 built-in themes, gradients, and 30 included fonts
• Dependent fields and value messages that react to what a visitor picks
• Cloudflare Turnstile CAPTCHA and honeypot bot protection
• File uploads (up to 9 MB per file on a Salesforce Site, up to 2 GB on Experience Cloud) and drawn signatures
• Built-in analytics stored in your org (the full dashboard is on Professional)
• A Setup Assistant that creates your site and grants the access your forms need

Two things do leave your org, and neither carries a submitted value: the CAPTCHA token is checked with Cloudflare, and QuikForms AI requests go to Anthropic.

For more details, see the Overview section.

QuikForms requires Salesforce Developer Edition or higher (Professional, Enterprise, or Unlimited). It uses Lightning Web Components, Visualforce pages, and Apex that are available in these editions.

No. Building and managing forms needs no code. The visual interface lets you:

• Create forms using drag-and-drop
• Configure fields with point-and-click
• Apply themes and customize colors
• Add validation patterns, from the common patterns listed in the field editor or with Generate with AI

Optional coding may be useful for:

• Custom HTML content in forms
• Advanced regex validation patterns
• Flows that act on the records your forms create
• Plugins that integrate with external systems (Professional)

QuikForms supports three form types, chosen with Form Type on the form's Settings tab:

Form Type	Purpose	Creates
Record Creation	Contact forms, support requests, inquiries, and anything that should become a record	A record on the object you choose, for example Case or Contact
Survey	Feedback forms and customer satisfaction surveys, sent as a link	The response, saved on a QuikForms Survey record
Chat	Collect a visitor's details, then connect them to an agent	Starts a Messaging for In-App and Web conversation, optionally creating a record first

Learn more about form types in the Creating Forms section.

Yes. QuikForms works on Experience Cloud and on Salesforce Sites, including a site you already run under any name and URL path.

To create a new Experience Cloud site for your forms, open the QuikForms Setup Assistant, click Salesforce Site Setup, and on the Experience Cloud Site tab follow the steps under Create a new Experience Cloud site. You create a Build Your Own (LWR) site in Setup (Open All Sites opens the page), put the QuikForms Renderer on its Home page, open it to the public, and publish it in Experience Builder. Then click Check Again, and click Grant access next to the site in Guest User Permissions. Digital Experiences must be turned on in your org.

To use an Experience Cloud site you already have:

1. Make sure the site uses an LWR template. The QuikForms Renderer does not load on Aura templates.
2. In Experience Builder, drag the QuikForms Renderer component onto the page that will show forms, and leave its Form ID blank.
3. In Setup Assistant → Guest User Permissions, click Grant access next to the site.
4. Publish the site. Forms are live on that page with ?fc=[form-id] added.

The full steps for both options are in Publish Your Forms.

Both show the same forms. Experience Cloud is recommended:

	Experience Cloud site	Salesforce Site
API calls per completed form	None	About 3 (2 with analytics turned off), counted against your org's daily API allocation
File uploads	4 MB per file, or up to 2 GB for a $CONTENTDOCUMENT field with Enable 2GB Uploads once the site is set up for it (Large File Uploads)	Up to 9 MB per file
Chat forms	Yes, with one line added to the site's head markup and Relaxed CSP	Yes
Rate limit and Valid Referrers	Applied	Applied
Embedding in your website	Yes, once allowed in Experience Builder	Yes, once allowed in the site's settings
After you upgrade QuikForms	Publish the site again	Nothing to do

Both plans include unlimited forms and submissions and QuikForms AI. Professional adds unlimited languages, the analytics dashboard, multi-object forms, and the plugin framework.

Feature	Standard	Professional
Form builder, field library, and all 8 field types	Yes	Yes
Record creation, survey, and chat forms	Yes	Yes
Experience Cloud and Salesforce Sites	Yes	Yes
Setup Assistant	Yes	Yes
Multi-page forms, dependent fields, and value messages	Yes	Yes
Drafts, publishing, version history, and rollback	Yes	Yes
Languages per form, with the visitor language picker	Up to 5	Unlimited
QuikForms AI: building, translation, validation patterns, error log help	Yes	Yes
Analytics	Total views and submissions per form	Full dashboard, field-level detail, and AI insights
Multi-object forms (Related Objects tab)	No	Yes
Plugins, custom field types, Flow hooks, and platform events	No	Yes

The 14-day free trial includes every Professional feature. Prices are on the pricing section of the home page.

QuikForms stays installed and nothing is deleted. Your forms, fields, translations, and submissions stay in your Salesforce org.

• Public forms go offline, and visitors see a message that the form is not currently available.
• QuikForms AI turns off.
• Every QuikForms page shows a banner saying the subscription has ended. Until your license expires, you can still open and export everything.

Renewing brings your forms and QuikForms AI back. See When a Subscription Ends and the Refund & Cancellation Policy.

Yes, on Professional. A plugin can add a custom field type (such as a range slider), validate values on the server, act on a submission, or call an external system through a Named Credential. Plugins run on Experience Cloud and on Salesforce Sites.

1. Download a plugin's zip from the Plugin Library, or build your own.
2. Someone with deployment access to your org deploys every folder in the zip, with the tool you already use for Apex.
3. For a custom field type, open a field in the field editor, go to the Options & Structure tab, and choose it under Plugin Field Type. Plugin Configuration (JSON) starts from the plugin's default settings and is checked for valid JSON before you can save.

Developers can find the interfaces, hooks, and examples in the Plugin Framework Overview.

Install the package from its link, then finish setup in the QuikForms Setup Assistant, where each step is a button and a checklist shows what is left:

1. Install the package. The installer asks you to approve two trusted sites: challenges.cloudflare.com for the CAPTCHA and www.sfquikforms.com for the documentation shown inside the app.
2. Open the Setup Assistant. Open the QuikForms app from the App Launcher and click QuikForms Setup Assistant in the utility bar at the bottom of the window.
3. Click Grant Me Access.
4. Work down the Setup Checklist: Salesforce Site Setup, Guest User Permissions, Bot Protection Setup, Platform Cache Setup, Form Links Setup, and QuikForms AI Setup.
5. Add your form objects. Under Form Objects, click Add Object for each object your forms will create records on, and create the five fields the panel lists in Object Manager, or click Do It For Me if Setup Automation is on.

Where a step is a change in Salesforce Setup, such as creating a site or adding fields to an object, the panel lists it with the exact values, a button that opens the right Setup page, and Check Again to confirm it is done. With the optional Setup Automation turned on, Do It For Me makes some of those changes for you after you confirm each one (see Setup Automation). The step-by-step guide is in Install the Package.

It is where QuikForms is set up and configured. Open the QuikForms app and click QuikForms Setup Assistant in the utility bar. It has three tabs:

• Setup Tasks
  • Grant Me Access adds you to the QuikForms Admins permission set group, which holds the QuikForms Admin permission set and the credential access QuikForms AI needs.
  • Setup Automation (optional) lets QuikForms create its fields on your objects, create sites, and publish Experience Cloud sites for you, through the QuikForms Setup app, after you confirm each change. Set Up Automation lists the steps to turn it on.
  • The Setup Checklist shows how many steps are done, with Refresh, and a button and live status for each step: Salesforce Site Setup (the steps to create an Experience Cloud site or a Salesforce Site in Setup, or to add QuikForms to one you already run), Guest User Permissions, Bot Protection Setup, Platform Cache Setup, Form Links Setup, and QuikForms AI Setup.
  • Form Objects lists the objects your forms can create records on. Add Object lists the steps to create the five QuikForms fields on an object in Object Manager, with Check Again to confirm them, or creates them with Do It For Me when Setup Automation is on. Each object shows Ready, how many of the five fields it has (with Add Missing Fields), or Hidden from you (with Show Fields to Me).
• Settings holds the org-wide settings in four sections (Public Forms, Security, Features, and Data & Logging), with Save, Discard, and Reload. A save is confirmed only once the new values read back. The Settings button in QuikForms Manager opens the same panel.
• Documentation shows this documentation inside Salesforce.

The Setup Tasks tab needs the Customize Application permission.

Yes, for rate limiting. QuikForms keeps short-lived data in a Platform Cache partition called QuikFormsCache, which is installed with the package. Until the partition has cache allocated to it:

• Rate limiting is off, on Experience Cloud and Salesforce Sites forms alike
• Abandoned file uploads on Salesforce Sites forms are cleaned up less often

Forms, file and signature uploads, and draft preview links keep working either way.

To allocate it, open Setup Assistant → Platform Cache Setup, which checks the cache live. If it has no capacity:

1. Click Open Setup.
2. Open the QuikFormsCache partition. There is nothing to create.
3. Click Edit.
4. Allocate 1 MB of Org Cache. Session Cache can stay at 0.
5. Click Save, then return to the Setup Assistant and click Check again.

QuikForms uses two layers of bot protection:

1. Cloudflare Turnstile (CAPTCHA)

Turnstile is a free, privacy-friendly replacement for the "I'm not a robot" checkbox. In the default Managed mode the widget is shown and usually completes on its own; the form's CAPTCHA Mode on the Styling tab can instead show it only when Cloudflare needs an interaction (Non-Interactive) or keep it hidden (Invisible). Salesforce checks every token with Cloudflare before it accepts a submission.

2. Honeypot Protection

A honeypot is a hidden field that bots fill in and people never see. It is checked on the server for Experience Cloud and Salesforce Site forms, and it is a separate control from CAPTCHA, so turning CAPTCHA off for a form leaves honeypot detection running. It is on by default and can be switched off org-wide with Honeypot Bot Detection in Setup Assistant → Settings → Security.

Turnstile Setup Steps:

1. Go to the Cloudflare Turnstile Dashboard.
2. Create a Turnstile widget and add your site's domain to its hostnames.
3. In QuikForms, open Setup Assistant → Bot Protection Setup, paste the Site key and Secret key, and click Save.
4. QuikForms checks the secret with Cloudflare and shows the result under Setup Status. Test secret key repeats the check at any time.

QuikForms grants them for you. In QuikForms, open Setup Assistant → Guest User Permissions:

1. Click Grant access next to each site that serves forms. That assigns the QuikForms Guest permission set: the form page, the CAPTCHA page, the classes that load and submit forms, CAPTCHA verification, and linking uploaded files. It gives no access to any of your existing records.
2. Under Your objects and fields, click Review access, then Grant this access. That gives visitors Create on whatever your published and draft forms write to, such as Case or Lead, and access to the fields they fill, in a permission set QuikForms creates called QuikForms Guest Form Access. Anything that cannot be granted is listed under Not granted with the reason.

Come back to step 2 after you publish a form that writes to a new object or field. Survey forms need no object access: the survey link itself authorizes the response.

You do not need to build anything. The package ships a QuikForms Lightning app with four tabs:

• QuikForms Manager is where you create and manage forms. The form builder opens from here.
• QuikField Manager holds the reusable field definitions shared across forms.
• QuikForms Analytics Manager shows performance across every form.
• QuikForms Error Manager shows the exception log.

Open the App Launcher and search for QuikForms. The QuikForms Setup Assistant is in the app's utility bar.

To give yourself access, click Grant Me Access in the Setup Assistant. That adds you to the QuikForms Admins permission set group, which holds the QuikForms Admin permission set: everything in QuikForms, AI features included. Give other administrators access by assigning them the same group in Setup.

A form can only create records on an object that has the QuikForms fields. The Form Object list on the form's Settings tab shows an object only when:

• The object has the QuikForms fields. Open Setup Assistant, and under Form Objects click Add Object and choose the object. The panel lists the five fields to create on it in Object Manager, with an Open Object Manager button: the form that created the record, answers with no field of their own (as text and as JSON), and the visitor's IP address and browser. Then click Check Again.
• You can see those fields. An object marked Hidden from you has the fields but you have no access to them. Click Show Fields to Me.
• You can create and read records of that object.

An object showing a count such as 3 of 5 fields is missing some; click Add Missing Fields for the steps to create the ones still missing.

Follow this workflow to create a basic contact form that creates a Case:

Before you start: open the QuikForms Setup Assistant and, under Form Objects, click Add Object and choose Case. Create the five fields the panel lists on Case in Object Manager, then click Check Again until Case shows Ready. Forms can only create records on an object prepared there.

Step 1: Create Fields

1. Navigate to the QuikField Manager tab.
2. Click New.
3. Pick one of the Quick Start Templates, such as Email Field, Subject Field, or Message Field, or fill in Field Name, Field ID, Field Type, and Label yourself.
4. On the Field Mapping tab, choose the Salesforce field the value is saved to.
5. Click Save, and repeat for each field.

Step 2: Create the Form

1. Navigate to the QuikForms Manager tab.
2. Click New. QuikForms creates a draft called "Untitled Form" and opens it in the form builder.
3. Click Rename in the builder header and name it, for example "Contact Us".
4. On the Settings tab, set Form Object to Case with Select Object if it is not already, and check that Form Type is Record Creation.

Step 3: Add Fields to the Form

1. On the Form Editor tab, drag fields from Available Fields onto the form.
2. Reorder them by dragging.
3. Click Save Form. Layout changes are not saved automatically.

Step 4: Style and Publish

1. On the Styling tab, apply one of the Quik Themes, for example Azure Horizon, and click Save Form.
2. Click Preview in the builder header to open the draft in a new tab and try a submission.
3. Click Publish. The form is now live.

Step 5: Open It on Your Site

The form is at your site address followed by ?fc= and the form's ID, for example https://[your-site-address]/?fc=contact-us. The Form ID is in the QuikForms Manager list and in Form ID (URL Parameter) on the Settings tab.

See the Quick Start section for detailed guidance.

Every form has versions, and visitors always see the one that is published:

• Draft: the version you edit. The builder shows it as Editable, and Save Form saves it without changing what visitors see.
• Publish: makes the draft live and archives the version that was live before. You choose a Major or Minor version number and can add a Version Tag. Publishing also puts an offline form back online.
• Published and Archived versions are Read-Only. To change a live form, click Draft in the builder header (or Create Draft in QuikForms Manager), make your changes, and publish.
• History in the builder header opens Version History, listing every version with Load, Rollback (creates a new draft from that version), Delete (drafts only), and Export. Version history and rollback are on every plan.

Yes, if you switch on Show Reset Button on the form's Settings tab. That adds a Reset Form button to the confirmation screen: the visitor clicks it, the form clears, and they can fill it in again without reloading the page.

It is off by default. Turn it on where repeat entry is expected:

• A kiosk or tablet at a reception desk, trade stand, or event
• Someone entering a stack of paper forms in one sitting
• A shared workstation where several people submit in turn

Resetting clears the saved draft as well as the visible fields, so the next person does not see the previous one's answers restored. The button's wording is translatable on the Labels tab, like any other form label.

This is about one browser session, not about preventing duplicates. QuikForms does not deduplicate submissions; if you need that, add a validation rule or a duplicate rule on the target object in Salesforce. Survey links are different: each link accepts one response unless the form has Allow Multiple Completions turned on.

Yes. Fields created in the QuikField Manager are reusable across all forms.

Benefits:

• Consistency: Same field configuration across forms
• Efficiency: Create once, use many times
• Maintainability: Update a field once and every form using it changes immediately, published forms included
• Standards: Enforce organizational field standards

Example: Create an "Email Address" field once with a validation pattern, then use it in contact forms, feedback forms, registration forms, etc.

To start a new field from an existing one, use the Clone row action in the QuikField Manager. There is no action that clones a whole form.

Yes. Click Delete in the form builder header, or use the Delete row action in QuikForms Manager, and confirm.

What Gets Deleted: the whole form is deleted, including every version (draft, published, and archived) and its saved QuikForms AI conversations.

What Is Kept:

• Fields: they stay in the QuikField Manager for other forms
• Records your form created, such as Cases and Leads
• Uploaded files linked to those records
• Analytics history, which is kept but is no longer attached to a form

Take it offline. This takes effect immediately, with no draft or publish needed:

• In the form builder: the header shows Live or Offline. Click Take Offline and confirm. Go Live puts it back.
• In QuikForms Manager: use the Take Offline or Go Live row action. The Status column reads Live, Offline, or Not published, and the Status filter lists forms by state.

Result: visitors who open an offline form see a page-not-found page, and its survey links stop working. Submissions you have already received are not affected, and the form's configuration is kept. Publishing a new version always puts the form back online.

Use Cases:

• Close a form during maintenance or a holiday period
• Stop a form that is receiving spam while you investigate
• Retire an old form without losing its configuration

A survey is a form with Form Type set to Survey, sent to each person as a link of its own:

1. Create the form, set Form Type to Survey on the Settings tab, and publish it. Under Survey Configuration, Survey Validity Days sets how long each link works and Allow Multiple Completions lets one link be used more than once.
2. Make sure Public Site URL is set (Setup Assistant → Form Links Setup), because survey links are built from it.
3. Create a link in one of these ways:
   • Use a Create Survey quick action. QuikForms includes one for Account, Case, Contact, Lead, and Opportunity: add it to the object's page layout, then use it from a record to create a survey linked to that record.
   • Use the Create QuikForms Survey action in Flow, for example to send a survey when a Case closes.
4. Send the Survey URL to the person, for example by email.

The response is saved on a QuikForms Survey record. The messages a visitor sees for an expired or already completed survey are on the Labels tab under Survey Labels.

A chat form collects a visitor's details and then starts a Salesforce Messaging for In-App and Web conversation with an agent. It works on both Experience Cloud and Salesforce Sites. You need Messaging for In-App and Web set up in your org first, with Omni-Channel routing and agents.

1. In Setup, create an Embedded Service Deployment for Messaging for In-App and Web (Web). In Domain, enter the domain of the site that shows the form, such as acme.my.site.com or acme.my.salesforce-sites.com. The chat only opens on that domain, and the domain cannot be changed later.
2. When Salesforce has finished creating it, click Publish on the deployment's page. No chat starts from an unpublished deployment.
3. On the form's Settings tab, set Form Type to Chat.
4. Under Chat Configuration, choose your Messaging deployment. If none is listed, paste the deployment's code snippet into Embedded Messaging Code Snippet instead.
5. Under Sites that can start chats, click Show Me How next to the site that shows the form. A chat can only start from an address in your org's CORS allowlist, and you add it there yourself: click Open CORS in Setup, click New, enter the site's address as the Origin URL Pattern exactly as shown, and save. Check Again then says the site can now start chats.
6. Choose a No Agents Fallback: Show Message Only, or Switch to Create Record so the form still creates a record.
7. Optionally choose Agent statuses, the Omni-Channel statuses in which an agent counts as available. Left empty, any status that is not an Away status counts.
8. Optionally turn on Create Record Before Chat, which saves a record from the form and passes its ID to the agent, and click Open Field Mapper to pass form answers to the conversation as hidden pre-chat fields.
9. Save the form and publish it.

On an Experience Cloud site, also set the site's security level to Relaxed CSP, add the deployment's SCRT URL under Trusted Sites for Scripts, add the QuikForms chat line to the site's head markup, and publish the site. The Chat Forms guide has each step, the head markup line, and a troubleshooting table.

QuikForms provides eight field types, chosen with Field Type in the field editor:

Field Type	Use For	Examples
Text Input	Single-line text entry	Name, Email, Phone, Subject
Text Area	Multi-line text entry	Message, Description, Comments
Select List	A choice from a list of options	Priority, Category, Country
Checkbox	Yes or no	Newsletter opt-in, Terms acceptance
Date	A date	Date of birth, Preferred delivery date
Date Time	A date and a time	Appointment slot, Event start
Signature	A drawn signature, saved as an image	Consent, Waivers, Delivery sign-off
Custom HTML	Rich HTML content	Instructions, Disclaimers, Formatting

A field with options is shaped on the field editor's Options & Structure tab:

• Custom Structure Type sets how the options are chosen: Select List (Dropdown), Radio Buttons, or Checkboxes for several at once
• Decorator Style changes how they look: Stars Rating, Little Boxes, or Toggle
• Include 'Other' Option adds an Other choice with a text box

On Professional, plugins can add custom field types, chosen under Plugin Field Type on the same tab.

Learn more in the Field Types section.

Dropdowns and radio buttons are both a Select List field with options of its own:

1. In the field editor's Basic Info tab, set Field Type to Select List
2. On the Options & Structure tab, set Custom Structure Type:
   • Select List (Dropdown) for a dropdown
   • Radio Buttons for radio buttons
   • Checkboxes to allow several choices
3. Click Edit Options
4. In the editor:
   • Click Add Option for each choice
   • Enter the option text
   • Use the up and down arrows to reorder
   • Click Save Options
5. Click Save

To offer the options in several languages, pick a language under Show option labels in in the same editor and enter the options in it. The list holds the languages the form offers (when you edit the options from the form) and the ones the field's label uses. Translate with AI on the Labels tab translates options too.

A Select List mapped to a picklist field on the target object can show that picklist's values instead of options of its own. The Priority Dropdown and Star Rating Quick Start Templates are ready-made examples.

See the Custom Structures section for detailed steps.

QuikForms shows and hides fields with rules on the Dynamic Fields tab:

1. Open your form from the QuikForms Manager tab.
2. Click the Dynamic Fields tab.
3. Click Add Trigger Field and choose a field. It must be a Select List, a Checkbox, or a field with options of its own.
4. For each trigger field, click Add Dependent Rule:
   • Choose the Dependent Field to show or hide
   • Under Show when values selected, move the values that show it to Selected
   • Add more rules as needed
5. Click Save Form.

Example Use Case:

Show a "Reason for Dissatisfaction" text area only when a visitor picks "Dissatisfied" for their satisfaction rating:

• Trigger Field: Satisfaction Rating (Select List)
• Dependent Field: Reason for Dissatisfaction (Text Area)
• Show when values selected: "Dissatisfied"

Use Value Messages, the second section of the Dynamic Fields tab:

1. Click Add Message Field and pick a Select List, a Checkbox, or a field with options of its own.
2. Click Add Message, choose the triggering option(s) under Show when values selected, and write the Message.
3. Under Display, choose Inline, next to the field (above or below it) or Modal, must be dismissed.
4. Tick Disable submit button when selected to block submission until they choose differently. The server enforces it as well.
5. Use Translate to write the message in every language the form offers.
6. Click Save Form.

You can also ask the AI assistant, for example "when someone picks Other under Plan, tell them we will call to discuss pricing".

Yes. On the Form Editor canvas, hover over the field that should start a new page and click the scissors icon (Start a new page at this field), or click Add page and drag fields into it. The Display drawer offers the same actions, Start a new page at this field included. Each page gets a title and an optional description, both translatable.

Visitors move through the pages with Back and Next and see a progress indicator. Each page is checked when they press Next. In the Multi-page section of the Settings tab you can choose the Progress indicator, turn on Review page before submit (a page that lists every answer with an Edit link), and keep Resume within the session on, so answers survive a page reload. They do not survive closing the tab.

You can also ask the AI assistant: "split this form into three pages with a review page".

Both. A field is checked when the visitor leaves it: a value that fails the field's pattern is flagged right there, and the error clears as soon as it is fixed. A required field is flagged on leaving it only after the visitor typed something and cleared it, so reading through the form does not paint it red. Submitting checks everything.

The server then checks every submission again, whatever the browser did, so the rules cannot be bypassed:

• Required fields, including any the submission left out
• Validation Regex patterns, matched the same way as in the browser
• Value messages set to Disable submit button when selected
• Validator plugins and Flow validation hooks (Professional)

Fields hidden by a dependent rule are skipped. Each problem comes back attached to its field and is shown there, in the visitor's language, using the messages on the Labels tab under Error Messages. This applies to record creation forms (single- and multi-object) and surveys alike.

Translation happens in two places: the form's own text, and the text on each field.

1. Choose the form's languages

On the form's Labels tab, the Languages panel lists the languages the form offers:

• Add language adds one. Standard allows up to 5 languages per form; Professional is unlimited.
• Drag the rows to set the order visitors see in the language picker, and set each language's name as it appears there.
• Make default sets the language shown when a visitor has not chosen one.
• Each row shows how complete that language is. Click it to edit its translations, or click the AI icon to translate it with AI.

Form text such as the title, submit button, and error messages is edited in the sections below the panel, such as Form Text Labels and Error Messages.

2. Translate field text

1. Open the field in the field editor
2. On the Basic Info tab, click Edit next to Label (or Description / Help Text, or Tooltip)
3. Enter a code in New Language Code, for example de_DE, and click Add Language
4. Type the translated Text, repeat for each language, and click Save & Close

Translate a field's options in Edit Options under Show option labels in (see the dropdown question above).

3. Let visitors choose

Tick Show Language Picker under Language Settings at the bottom of the Labels tab. You can also link straight to a language by adding &locale=de_DE to the form address.

The Multi-Language Support section covers this in full.

They turn a field into a file upload. On the field editor's Field Mapping tab, choose one of them instead of a Salesforce field. Files are uploaded when the form is submitted and linked to the record it creates.

$ATTACHMENT (Single File Upload)

• On a Salesforce Site: the file is saved as a Salesforce Attachment, up to 9 MB. Attachments are a legacy feature that only some objects support (such as Account, Case, Contact, Lead, Opportunity, and custom objects), so the field editor offers $ATTACHMENT only for those.
• On Experience Cloud: the file is saved as a Salesforce File, up to 4 MB.
• Accepted Types: jpg, jpeg, png, gif, bmp, tif, tiff, pdf, doc, docx, txt, log.

$CONTENTDOCUMENT (Multiple File Upload, recommended)

• Storage: files are saved as Salesforce Files, each linked to the record, on any object.
• Behavior: the visitor can pick several files and remove any before submitting.
• On a Salesforce Site: each file can be up to 9 MB.
• On Experience Cloud: each file can be up to 4 MB, or up to 2 GB with Enable 2GB Uploads (Experience Cloud only) on the field editor's Options & Structure tab, once you have turned on the site's settings for it in Setup (Large File Uploads; Show Me How in the Setup Assistant lists the steps). One of those settings, Allow guest users to access public APIs, lets anyone who is not logged in call the site's Salesforce APIs as the site's guest user, so a visitor could create a record on an object your forms write to without the form, its CAPTCHA, or its checks. Turn it on only if you need uploads over 4 MB.
• Accepted Types: the $ATTACHMENT list plus xls, xlsx, ppt, pptx, and csv, and on a Salesforce Site also zip and rar.

Example Single File Upload ($ATTACHMENT):

Field Name: Resume Upload
                                    Field ID: resume_file
                                    Field Type: Text Input
                                    Label: Attach Resume
                                    Object Field: $ATTACHMENT
                                    Description / Help Text: Upload a PDF or Word document
                                    Required Field: Yes

Example Multiple File Upload ($CONTENTDOCUMENT):

Field Name: Supporting Documents
                                    Field ID: support_docs
                                    Field Type: Text Input
                                    Label: Upload Documents
                                    Object Field: $CONTENTDOCUMENT
                                    Description / Help Text: Upload images, PDFs or Office documents
                                    Required Field: No

QuikForms AI does six things, each triggered by an explicit click:

• Build a form by describing it in plain language, with Create with AI in QuikForms Manager or the AI assistant in the form builder
• Translate every label, tooltip, and option into your chosen languages
• Generate validation patterns from a description, with worked examples
• Explain your analytics, including which field people abandon (Professional)
• Summarize error logs into the few things actually going wrong
• Explain a single exception in plain language

AI buttons appear only for people with access to QuikForms AI. See the QuikForms AI section of the admin guide for detail.

There are two ways to power it:

• QuikForms AI, included in your plan: click Grant Me Access in the QuikForms Setup Assistant, then open QuikForms AI Setup and click Activate AI. There is no key to copy.
• Your own Anthropic key: open Setup Assistant → QuikForms AI Setup, choose Your own Anthropic key, paste it into Anthropic API Key, and click Connect. Anthropic is the only provider. The key is stored encrypted in Salesforce and never shown again.

QuikForms AI Setup shows a Setup Status for the credential, access (the QuikForms Admin permission set), and the active provider, and a button to test the connection.

QuikForms AI Setup also says what happens to data when AI is used: a request and the information it needs leave Salesforce for the AI provider, and form submissions are never sent. Other administrators get AI with the QuikForms Admins permission set group.

No. The AI works on form configuration (field names, labels, layout, validation rules), aggregate counts (how many sessions started a form, which field they stopped at), and what an administrator types to it.

These are never transmitted:

• Values submitted through your forms
• The Salesforce records your forms create
• File uploads and signatures
• Visitor IP addresses and user agents

No AI request happens during form rendering or submission, so a visitor completing a form never causes data to be sent anywhere. There is one exception: when an administrator asks the AI to explain an exception log, or to summarize a set of logs, the log messages are sent, and an error message can quote a value that failed validation. Full detail is in the Data Processing Agreement.

The included allowance covers several hundred forms a month on Standard and over a thousand on Professional. Your first 45 days come with double the allowance, automatically.

During the 14-day free trial the allowance is much smaller, sized for evaluating the assistant rather than building a production form set. It covers creating and refining a few forms. The assistant shows what you have left as you go, and your allowance becomes your plan's full amount when you subscribe.

What consumes the allowance is conversation length, not form count. Creating a form from one description is inexpensive; each follow-up message in the same conversation costs progressively more, because the assistant re-reads everything said so far. Starting a fresh conversation for an unrelated change is cheaper than continuing a long one.

Translation, validation patterns, analytics insights, and log digests use a smaller model and use very little of the allowance.

The allowance is per company, not per org. A sandbox created or refreshed from your production org shares production's allowance. A sandbox where you install QuikForms directly gets a small allowance of its own. Build forms in a sandbox and move them to production with Export and Import on the Forms Dashboard: importing uses no AI allowance.

With your own Anthropic key there is no QuikForms allowance: Anthropic bills you directly.

This applies to the AI allowance included in every plan, not to your own Anthropic key. You are emailed at 80%, and the assistant shows how much is left. At 100%, QuikForms AI pauses until the allowance resets at the start of your next billing period.

Nothing else is affected. Published forms keep serving traffic, submissions keep landing in Salesforce, analytics keeps recording, and every non-AI feature works normally.

If you reach the limit sooner than you expected, email info@sfquikforms.com and we will help you find what is using it.

No. The AI can only edit a Draft version, and it re-checks that on every change rather than once at the start. A published form serving live traffic cannot be modified until you publish a new version yourself.

There is also a one-click Undo that restores the draft and removes any fields the AI created. It survives a page refresh, and it keeps any field another form has since adopted rather than deleting it out from under them.

• Org-wide off switch: untick AI Features Enabled in Setup Assistant → Settings → Features. Every AI feature disappears and no AI request is made by anyone. It is on by default.
• Who has it: AI comes with QuikForms access. Everyone with the QuikForms Admin permission set, directly or through the QuikForms Admins permission set group, sees AI features, and nobody else does. To pilot, give QuikForms access to a few administrators before rolling out. AI cannot be withheld from one QuikForms administrator while others keep it.

With AI off, every other QuikForms feature works exactly as normal.

Yes, you can use your own Anthropic account. Anthropic is the only provider QuikForms supports. In Setup Assistant → QuikForms AI Setup, choose Your own Anthropic key, paste the key, and click Connect. QuikForms does not meter your usage; Anthropic bills you directly. This suits orgs whose security team requires a direct contractual relationship with the AI vendor, and orgs with an existing Anthropic agreement they would rather use.

The included allowance needs no second vendor to approve and no separate invoice.

QuikForms includes built-in analytics that track the following metrics for each form:

Plans: every plan counts total views and total submissions per form, shown in the QuikForms Manager list. The dashboard below, with the daily breakdown, engagement, devices, browsers, referrers, and per-field detail, requires the Professional plan.

Metric	Description
Total Views	Number of times the form has been loaded
Unique Visitors	Distinct visitors that day, counted once each however many times they view the form. Identified by a one-way hash of the IP address salted with the date, so no IP is stored and the same person is not recognized across days. A multi-day total is the sum of each day's uniques.
Submissions	Number of successful form submissions
Conversion Rate	Percentage of views that result in a submission
Avg. Time to Complete	Average duration from form load to submission
Started, Abandoned, and Completion Rate	How many sessions touched at least one field, how many of those left without submitting, and the share that finished. Completion rate judges the form itself, apart from visitors who never began
Where people stop	Per field: how many visitors reached it, left it blank, hit an error, or quit there. Only when Include field-level detail is on for the form
Device Breakdown	Desktop, mobile, and tablet view counts
Browser Breakdown	Submissions by browser (Chrome, Safari, Firefox, Edge, Other)
Top Referrers	Domains driving traffic to your forms
Daily Trends	Day-by-day view, unique visitor, and submission charts
Trend Indicators	Percentage change compared to previous period

All analytics data is stored in your Salesforce org, and no third-party analytics service or external script is involved.

On every plan, the QuikForms Manager list shows each form's Views, Submissions, and Conv. Rate. On Professional there are two more views:

1. Analytics Manager (All Forms)

• Navigate to the QuikForms Analytics Manager tab
• View aggregate metrics across all forms
• Use the per-form breakdown table to compare form performance
• Click any form name to see its detailed analytics

2. Per-Form Analytics (Individual Form)

• Open any form in the form builder
• Click the Analytics tab
• View detailed metrics, engagement, daily trends chart, device/browser breakdown, and top referrers
• Click Analyze with AI for a plain-language reading of the numbers

Both views support date range filtering (Last 7 days, Last 30 days, Last 90 days, or All time).

Yes. On Professional, analytics can be turned off per form:

1. Open a draft of the form in the form builder.
2. Navigate to the Analytics tab.
3. Click the Analytics Enabled toggle at the top so it reads Analytics Disabled.
4. Click Save Form, then publish. The setting belongs to the version, so it takes effect when that version goes live.

When disabled, no analytics data is collected for that form. Existing analytics data is preserved and can still be viewed.

To turn analytics off for every form, untick Analytics Enabled in Setup Assistant → Settings → Features. On a Salesforce Site that also saves one API call per completed form.

No. QuikForms analytics are built in. There is no need for Google Analytics, Adobe Analytics, or any other third-party analytics service.

What that means for you:

• Privacy: analytics data stays in your Salesforce org, and form submissions are never sent to an external server.
• No additional cost: no third-party subscription is required.
• No setup: analytics work out of the box, with nothing external to configure.
• No tracking scripts: QuikForms sets no cookies of its own and loads no analytics scripts. Unique visitors are counted from a daily hash of the IP address, and no IP address is stored for analytics.

Whether your site needs a cookie or consent notice depends on your site as a whole and on your own legal advice.

Yes, when properly configured. QuikForms implements multiple security layers:

Security Feature	Protection Against
Cloudflare Turnstile	Bot submissions, spam, automated abuse
Honeypot Protection	Automated bot submissions (on by default, org-wide setting)
Guest User Permissions	Unauthorized data access, privilege escalation
Server-side Validation	Required fields, patterns, and blocking rules bypassed in the browser
HTTPS Enforcement	Man-in-the-middle attacks, data interception
Output Escaping and HTML Sanitizing	Cross-site scripting (XSS)
Rate Limiting	Submission flooding from one IP address
Valid Referrers	Submissions sent from pages outside the domains your forms are served from

See the Security section for detailed configuration guidance.

Guest users (unauthenticated public visitors) get only what the Setup Assistant grants:

The QuikForms Guest permission set (Grant access next to a site):

• The form page and the CAPTCHA page
• Loading and submitting forms
• CAPTCHA verification through the Turnstile credential
• Linking uploaded files to the record a submission creates

The QuikForms Guest Form Access permission set (Grant this access under Your objects and fields):

• Create on the objects your published forms write to, such as Case or Lead
• Access to the fields those forms fill

What Guest Users Cannot Access:

• Any of your existing records, including earlier submissions
• QuikForms' own objects: QuikForms reads form definitions itself
• The QuikForms admin app and its settings
• Salesforce Setup or configuration

What Visitors See:

• Only the published version of a form that is live
• A draft only through a preview link, which lasts 8 hours
• A page-not-found page for an offline, unpublished, or unknown form

Yes, QuikForms includes multiple spam prevention measures:

1. Cloudflare Turnstile Protection

• Turnstile is a privacy-friendly CAPTCHA that validates human users non-intrusively.
• Server-side verification prevents bypass attempts.
• It can be turned off per form with Disable CAPTCHA on the Settings tab, which is not recommended for public forms.

2. Honeypot Protection

• A hidden field catches automated bots and is checked on the server.
• It keeps running when CAPTCHA is turned off for a form.
• It is on by default; Honeypot Bot Detection in Setup Assistant → Settings → Security turns it off org-wide.

3. Rate Limit

• The default is 20 per minute from one IP address, on Experience Cloud and Salesforce Sites forms alike. Only form submissions, survey submissions, and plugin callouts count; page views, file uploads, and analytics do not.
• Set it with Rate Limit (per minute) in Setup Assistant → Settings → Security. Visitors behind one office network share the limit.
• The rate limit needs Platform Cache. Without it, nothing is throttled.
• A visitor over the limit sees "Too many requests. Please try again later."

4. Valid Referrers

• Valid Referrers in the same Security section is a comma-separated list of the domains your form pages are served from, such as your site's own domain or custom domain. A request sent from a page on any other domain is refused. Left blank, it allows any domain.
• It does not decide which websites may embed your forms; the site's clickjack settings do that (see Embedding Forms).
• A wrong entry blocks legitimate submissions, so test after changing it.

5. Field Validation

• Required fields and validation patterns are enforced again on the server.
• File size and file type are restricted.
• Together, these checks prevent malformed submissions.

Additional Measures You Can Implement:

• Browser information: Log User Browser Info on the Settings tab records the visitor's browser and IP address on each record
• Analytics Monitoring: use built-in analytics to detect unusual spikes in form activity
• Flow: create flows to flag suspicious submissions

Implement these best practices to minimize spam:

Essential Protections:

1. Keep Turnstile CAPTCHA Enabled: this is the most effective spam prevention
   • In form Settings, ensure Disable CAPTCHA is unticked
   • Check that Setup Assistant → Bot Protection Setup shows all three Setup Status items ticked
   • Honeypot detection is a separate control, so it keeps running when CAPTCHA is off for a form
2. Keep the Rate Limit on: allocate Platform Cache so the rate limit applies
3. Use Required Fields: more required fields mean more effort for spammers
   • Tick Required Field on key fields in the field editor
   • Balance user experience against spam prevention

Advanced Protections:

1. Log Browser Info: Track submission sources
   • Tick Log User Browser Info on the form's Settings tab
   • Review the IP address and browser recorded on each record
2. Validation Rules: Add Salesforce validation rules
   • Detect spam keywords in Case fields
   • Flag suspicious patterns (all caps, excessive URLs)
3. Flow: Automate spam detection
   • Auto-close Cases with spam characteristics
   • Send alerts for suspicious patterns
   • Quarantine submissions for review

Monitoring and Response:

• Regularly review submitted Cases for spam
• Create Reports for spam pattern detection
• Update validation rules based on new spam tactics
• Take the form offline while it is under heavy attack

Yes. QuikForms runs inside your org, and submissions are stored as ordinary Salesforce records, so they are covered by the security controls your org already has:

Encryption in Transit (HTTPS/TLS):

• All Salesforce communications use HTTPS with TLS 1.2 or higher.
• Form submissions are encrypted during transmission.
• Turnstile CAPTCHA verification calls are encrypted.
• File uploads are encrypted during transfer.

Encryption at Rest:

• Standard Salesforce security: data is stored in Salesforce's infrastructure under Salesforce's physical security and access controls.
• Salesforce Shield Platform Encryption: if your org has it, you can use it to encrypt fields on the records your forms create. It requires a Shield Platform Encryption license.

Additional Security Measures:

• Field-Level Security: Control who can see sensitive data
• Object Permissions: Restrict access to Case and Survey records
• Audit Trail: Field History Tracking is available for compliance
• Backup and Recovery: Salesforce's own backup and recovery options apply

Recommendations for Sensitive Data:

• Consider Salesforce Shield for regulated industries
• Enable Field History Tracking for audit requirements
• Implement data retention policies
• Review and minimize data collection to what's necessary
• Train staff on data handling procedures

Visitors see the same page-not-found page ("Error 404. The requested resource could not be found.") whenever a form cannot be shown, so that nobody can discover form IDs by guessing. Check these causes in order:

1. Form Not Published

• Symptom: QuikForms Manager's Status column reads Not published.
• Solution: open the form and click Publish.

2. Form Offline

• Symptom: the Status column, and the builder header, read Offline.
• Solution: click Go Live in the builder header, or the Go Live row action in QuikForms Manager.

3. Incorrect Form ID in URL

• Symptom: the address has a typo or the wrong form ID.
• Solution:
  1. Check the URL parameter: ?fc=your-form-id.
  2. Compare it with the Form ID column in QuikForms Manager, or Form ID (URL Parameter) on the form's Settings tab.
  3. Form IDs are not case-sensitive. If the Form ID was changed, links using the old one stop working.

4. Survey Link Expired or Used

• Symptom: a survey link that worked before no longer opens.
• Cause: the link is older than the form's Survey Validity Days, or it was already completed and Allow Multiple Completions is off. Links also stop working while the form is offline.

5. Form Deleted

• Symptom: the form worked before but no longer appears in QuikForms Manager.
• Solution: deletion is permanent. Recreate the form, or import it again if you exported it earlier.

Missing fields can be caused by several configuration issues:

1. Field Not Added to the Form

• Most Common Cause
• Solution:
  1. Open the form from QuikForms Manager. If the version is Read-Only, click Draft in the header first.
  2. On the Form Editor tab, open the Display drawer to see the fields on the form.
  3. Drag missing fields from Available Fields onto the form.
  4. Click Save Form, then Publish.

2. Field Missing from Available Fields

• Cause: Available Fields lists only fields that target the form's object (or an object on the Related Objects tab) and that are not already on the form, including in its Hidden or Populated drawer.
• Solution: check the field's Target Object on the field editor's Field Mapping tab, and check the Hidden and Populated drawers.

3. Changes Not Published

• Symptom: the field shows in Preview but not on the live form.
• Solution: the live form is the published version. Publish your draft.

4. Field on Another Page

• Symptom: on a multi-page form, the field is missing from the page you expected.
• Solution: check which page it is on in the Display drawer or on the canvas.

5. Field Deleted

• Symptom: the field no longer exists in QuikField Manager.
• Solution: recreate the field and add it to the form again on the Form Editor tab.

6. Conditional Field Hidden

• Symptom: the field appears sometimes but not always.
• Cause: a dependent rule shows it only for certain values.
• Solution:
  1. Open the form from QuikForms Manager
  2. Navigate to the Dynamic Fields tab
  3. Check the dependent rules and their Show when values selected values
  4. Test by selecting a trigger value in Preview

Start with what the form itself says, then check the QuikForms Error Manager:

1. Errors Shown on the Form

• The server re-checks every submission and returns each problem attached to its field, so an error appears next to the field it concerns. Problems that belong to no field appear at the top of the form.
• Required fields: "is required" means a required field was empty.
• Patterns: "is not a valid value" means the value failed the field's Validation Regex.
• Blocked: a value message with Disable submit button when selected matched the visitor's choice.
• Files: a file was over the size limit (9 MB per file on a Salesforce Site, 4 MB on Experience Cloud unless 2 GB uploads are on) or of a type the field does not accept.

The wording of these messages is on the form's Labels tab under Error Messages.

2. CAPTCHA Verification Failed

• Symptom: the form says "Please complete the verification." or "Verification failed. Please try again."
• Solution:
  • Wait for the Turnstile challenge to complete (usually automatic)
  • Refresh the page if the Turnstile widget doesn't load
  • Check that your site's domain is in the Turnstile widget's hostnames in Cloudflare
  • In Setup Assistant → Bot Protection Setup, click Test secret key

3. Guest User Permissions

• Symptom: the form shows its generic error ("An error occurred. Please try again." unless you changed it), and a FORM-4012 entry appears in the QuikForms Error Manager.
• Solution: open Setup Assistant → Guest User Permissions, click Review access under Your objects and fields, then Grant this access. Anything listed under Not granted shows why. QuikForms refuses a submission it cannot store in full, rather than saving a record with missing answers.

4. Field Mapping Errors

• Symptom: the form shows the generic error, and a FORM-4012 or FORM-4013 entry appears in the Error Manager.
• Solution:
  • Check each field's object field on the field editor's Field Mapping tab
  • Make sure the mapped fields exist on the target object and accept that kind of value
  • Check the form's Form Object on the Settings tab
  • A field with no object field of its own is saved in the record's QuikForms extra-answers field (Quik_Extra_Fields__c)

5. Salesforce Validation Rules and Automation

• Symptom: the form shows an error from Salesforce and no record is created.
• Solution:
  • Check validation rules, required fields, triggers, and flows on the target object
  • Ensure the form provides every value the object requires
  • Supply fixed values with fields in the form's Hidden drawer
  • Read the full error in the QuikForms Error Manager

6. Rate Limit and Valid Referrers

• "Too many requests. Please try again later.": the visitor's IP address passed the Rate Limit (per minute).
• "Unauthorized Origin": the page that sent the submission is not in Valid Referrers.

Styling issues are usually caused by unsaved or unpublished changes, or by caching:

1. Styling Not Saved or Not Published

• Symptom: Changes don't appear in preview or on the live form.
• Solution:
  1. Make sure you are editing a draft. A published version is Read-Only, and the Styling tab offers Create draft.
  2. Make styling changes on the Styling tab.
  3. Click Save Form and wait for the success message.
  4. Click Preview to check, then Publish so the live form changes.

2. Browser Cache

• Common Issue
• Solution:
  • Hard refresh: Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac)
  • Clear browser cache and cookies
  • Test in private/incognito window
  • Try a different browser

3. Custom HTML Overriding Styles

• Symptom: Some styling works but specific elements don't change.
• Solution:
  1. Check Custom HTML Head under Advanced Settings on the form's Settings tab
  2. Review Custom Header HTML and Custom Footer HTML
  3. Look for inline styles or <style> tags
  4. Remove or adjust conflicting CSS

4. Invalid Color Values

• Symptom: Some colors don't apply.
• Solution:
  • Ensure hex colors start with # (e.g., #0070D2)
  • Choose colors with the color picker rather than typing them
  • Apply a Quik Theme again to reset

5. Container Width Issues

• Symptom: the form is too wide or too narrow.
• Solution:
  1. Check Content Container Width on the Styling tab
  2. The default is 575px
  3. Use valid CSS units: px, %, rem, vw
  4. Test on different screen sizes

6. Preview Not Refreshing

• Symptom: the preview shows an old version.
• Solution:
  • Save your changes first. Preview renders the saved draft, not unsaved edits.
  • Click Preview again: each click opens a fresh tab with a new preview link.
  • Close the old preview tab so you are not reading a stale one.
  • Test the live form URL directly.

Translation problems usually come down to which languages the form offers and which one the visitor gets:

1. Language Not Offered by the Form

• Symptom: the language is missing from the picker.
• Solution: on the form's Labels tab, add it with Add language in the Languages panel, then save and publish.

2. Language Picker Not Shown

• Symptom: visitors cannot switch language.
• Solution: tick Show Language Picker under Language Settings at the bottom of the Labels tab, or link straight to a language with ?fc=contact-us&locale=de_DE.

3. Form Opens in the Wrong Language

• Behavior: without a locale in the address or a choice in the picker, the form shows its default language, marked Default in the Languages panel. A form with no default set uses English (en_US).
• Solution: click Make default next to the language you want.

4. Some Text Not Translated

• Symptom: Some fields show translation, others don't.
• Behavior: a string with no translation in the visitor's language falls back to the form's default language, then to English.
• Solution: each row in the Languages panel shows how complete that language is. Click it to fill the gaps, or use the AI icon to translate what is missing.

5. Language Codes Don't Match

• Symptom: a field has a translation, but the form does not use it.
• Cause: language codes are free-form, so de and de_DE are different languages to QuikForms.
• Solution: use the same code on the form and on its fields.

6. Options Not Translated

• Symptom: Field labels translate but dropdown options don't.
• Solution:
  1. In the form builder, click the field's options on the canvas to open Edit Options & Structure
  2. Under Show option labels in, pick each language the form offers and enter its options
  3. Click Save
  4. Or translate them with Translate with AI on the Labels tab

Start with the QuikForms Error Manager tab. QuikForms records what goes wrong there, including failed submissions, with an error code, the form, and the full error message.

Using the Error Manager:

1. Open the QuikForms Error Manager tab.
2. Filter by severity, source, or date to find the entry.
3. Open it to read the detail.
4. Click Explain with AI for a plain-language explanation and likely fix. Summarize in the list header digests every log that matches your filters.

What gets recorded: by default the Exception Log Level is Error, which records Critical and High entries. Warning adds Medium, Info adds Info, and Debug records everything. Logs are kept for 30 days by default. Both settings are in Setup Assistant → Settings → Data & Logging.

Salesforce debug logs: QuikForms is a managed package, so its own code does not appear in your org's debug logs. They are still useful for your own automation on the target object, such as validation rules, triggers, and flows that run when a form creates a record. To capture them, add a trace flag in Setup → Debug Logs for the site's guest user, submit a test form, and open the new log.

Common Salesforce Errors:

Validation Rule Errors:

FIELD_CUSTOM_VALIDATION_EXCEPTION, [Validation Rule Name]:
                                    [Error Message]

• Solution: Adjust the form to satisfy the validation rule, or change the rule

Required Field Errors:

REQUIRED_FIELD_MISSING, Required fields are missing: [Field_Name]

• Solution: Add the field to the form, or supply a fixed value with a field in the Hidden drawer