Form Action Parameters

Form action option parameters. Adding these for form actions have various added features to form processing.

PageID Adding this parameter to your form action you can specify a custom landing page for your web form. Take a look at the Customizing Web Forms document for an example of this implementation.
OPTINDefault is False. When a form contains a mailing list registration this option forces the double opt in status. Possible values are "true" or "false".
SAR Default is True. You can disable the auto responder if desired. To do this, you will need to alter the form action URL by adding this parameter. Possible values are "true" or "false", take a look at the Customizing Web Forms document for an example of this implementation.
SWE Default is True. This parameter prevents the securezone email being sent out. Possible values are "true" or "false", take a look at the Customizing Web Forms document for an example of this implementation.
SendInvoice If you have a custom web form taking payment other then the eCommerce module this will trigger an invoice to be sent. Please note that there is no False option available for the eCommerce module. The only possible value is "true", take a look at the Collect payment using a form article for an example of this implementation.
ECRM This parameter attaches the custom information to the CRM entity rather than creating a case that data contained in the custom fields. To use this feature add ECRM=1 to the form's action as described in the Customizing Web Forms document for an example of this implementation.
JSON This parameter allows you to submit webforms using AJAX. Do note this is only limited to standard web forms, other types of forms (like webapp submission forms for example) do not support this method. For a step-by-step tutorial on how to create an AJAX-powered web form take a look at this tutorial: Submitting standard web forms with Ajax and JSON
ExcludeBoolFalse

Default is True. Used when adding a web app search forms.
True – if the user doesn’t check the boolean field in the web app search form or it does not exists in the web app search form, then the system returns all the web app items from the database, regardless of the actual fields value (true or false) stored in the database. When the boolean field is checked (true) in the web app search form, the system will return only the web app items whose boolean field have the value true saved in the database. This check is applied for every boolean field included in a web app item.
False – if the user doesn’t check the boolean field in the web app search form or it does not exists in the web app search form, then the system returns only the web app items whose boolean field is false in the database. When field is checked, the system will search for items having the boolean field with value=true while items with boolean field value=false will be ignored.