Forms for Editors

With Forms for Editors you can create reusable forms. With forms, you can collect data from your visitors in a structured manner.

For instance, you could create forms to handle;

  • Brochure orders
  • Price inquiries
  • Questionnaires
  • Contact information
  • Etc.

Forms are created from the Dynamicweb administration backend, and then added to a paragraph on your website using the Forms for Editors app.

To visitors on your website, a form might look like (Figure 1.1).

Figure 1.1 A form

In this document, you will learn to work with, implement, develop and integrate with the Forms for Editors app.

Forms are created and configured in the Dynamicweb administration, and then later added to a paragraph using the Forms for Editors app.

To create a new form:

  • Go to Apps > Forms for Editors
  • Click New form in the toolbar
  • Name the form

You have now created a(n empty) form (Figure 2.1).

Figure 2.1 An empty form

The empty form will appear in the Forms-list in the Forms for Editors app (Figure 2.2).

To add fields to the form simply click on it - or right click and select edit. You can also use the right-click menu to cope, rename or delete a form - and to go to the list of data submitted using the form.

Figure 2.2 Right-clicking a form lets you access a number of actions directly

Once you have opened a form, you can use the ribbon bar buttons (Figure 3.1) to add field to it - these are the fields which the user will fill out and submit.

You can add the following types of fields:

  • Regular fields
  • List fields
  • Buttons
  • Content elements
Figure 3.1 The forms for editor ribbon bar buttons

You can add the following regular fields:



Why you need it



A text field for entering a single line of text

You may need users to submit their name, address, email, etc.



A hidden field

Allows an implementer to pass temporary, or session-based data, from one form to another or to store information that has already been entered in by the user.


Text area

A text-area for entering several lines of text

Describing a problem, adding a comment, or adding a multi-line address



A password field

Used for capturing user input. It disguise each character with an asterisk (*) instead of displaying the entered digits in order to offer an on-screen privacy while entering a password.


Check Box

A checkbox for users to check or leave unchecked

Accepting user agreements, opting in, and so forth

To have it unchecked by default, open the edit view and set the default value to ‘unchecked’


A file selector button, for submitting files

Users can upload files, e.g. a resume or a report.


You can upload several files to the same field by naming the additional input controls “FileFieldSystemName_{N}”.

Files are saved to the /Files/System/FormUploads/Form-Name/ folder. Some file extensions are not allowed, e.g. .cshtml, .aspx and similar, and filenames are automatically cleaned of illegal characters.


These are the list fields at your disposal:


A dropdown list of options for the user to select from

You can set a default option from the edit view

Radio Button

A list of options; users select one

You can set a default option from the edit view

Checkbox list

A list of checkboxes – users may check more than one

You can set a default option from the edit view


You can add the following buttons to your form:


A button for submitting the form content



A button for resetting the form



The following content elements can be created:

Body text

Add a text to the form



Add an image to the form


You can add any combination of these fields to the form to create the forms you need (Figure 3.2).

Figure 3.2 A form with fields

All fields you create are preconfigured and should work out of the box - but in some cases, you may want to change the default configuration.

To do so, right-click a field and click Edit to open the field details view (Figure 4.1).

Figure 4.1 Editing a field

When you edit a field in this way, you can:

  • Change the labelplaceholder and description values
  • Set or remove the field as Required and Active
  • Hide the field in the receipt after submitting
  • Change the field type

The type dropdown allows you to select HTML5 input types - please be aware that not all browsers fully support HTML5.

You can also use the Layout and Values buttons (Figure 4.2) to set up more advanced behaviors.


  • Set values which should be prepended or appended to the field value on submit, e.g. a currency symbol
  • Set a CSS class value or a size in pixels to a
  • Customize the system name of the field


  • Set a default value
  • Map to an existing value in user management (for logged in users) and use that as an automatic value
  • Set a max. length on the field

By default, the field you create are shown in form-mode (Figure 5.1).

Figure 5.1 Form-mode

Form mode is useful because it shows you an approximation of how this form will be rendered in frontend - but in some cases you may need to change the view to list-mode (Figure 5.2).


Figure 5.2 List-mode

The List-mode is useful because it lets you review the structure of large forms without being distracted by the controls used, and because it provides you with more information about each form field.

It is also the only mode where you can specify an email field - this is the field which will be used as the source for email addresses when setting up email notifications on the Forms for Editors app.


To allow website visitors to fill out and submit your form, you must add it to a paragraph on a page on your website. You do so by using the Forms for Editors app.

The forms for Editors app allows you to select and style the form in frontend, and to control what happens when the form is submitted.

The form settings (Figure 7.1) are the fundamental app settings.

Figure 7.1 The form settings

With the form settings you:

  • Select a form to publish
  • Select a template for rendering the form. Choose between the automatic system template or select or create a custom template from the dropdown menu
  • Specify a custom text for the form submit button (e.g. for localization purposes)
  • Export the submitted form data as a .csv file

The when submitting form settings (Figure 8.1) allows you to control what happens when a user submits a form.

Figure 8.1 The 'When submitting form' settings

With the when submitting form settings you can:

  • Specify a page to redirect the user to after they submit the form
  • Select or create a confirmation template to use, and specify a text to publish using that template

To both redirect AND show a receipt, simply set up the forms for editors app with the same form and the confirmation template you want to use on the page you redirect users to. The redirect will contain a submit token that will allow the receipt page to load the result of the form and display the information on the page.

A form can be used to collect consent for a particular GDPR activity and store them in the Data Processing app – read more about the Data Processing app here.

To collect consent using a form:

  • Create a new checkbox field
  • Click the field to edit it
  • Select an appropriate consent activity using the Consent dropdown (Figure 9.1)

When this form is submitted in frontend with the checkbox checked, a new consent is created in the database based on either the user ID, an email field on the form, or (for truly anonymous users) a checksum value.

Figure 9.1 Collecting consents using the Forms for Editors app

The email settings (Figure 10.1) allow you to set up automatic email notifications when a form is submitted.

Figure 10.1 The email settings

With the email settings you can:

  • Specify a subject for the email
  • Specify a sender name and email – or retrieve it from the form using the Email field setting from the list view
  • Specify one or more recipients (CC or BCC)
  • Select a template for rendering the email. Choose between the automatic system template or select or create a custom email template from the dropdown menu
  • Enter a text (if using a custom template)

You can use the receipt settings (Figure 11.1) to email a receipt to the visitor submitting the form.

Figure 11.1 The receipt settings

With the receipt settings you can:

  • Specify a subject for the email
  • Specify a sender name and email
  • Specify one or more recipients (CC or BCC)
  • Select a template for rendering the email - you can choose between the automatic system template or select/create a custom email template from the dropdown menu
  • Enter a text (if using a custom template)

The max submit settings (Figure 12.1) allow you to control if and how the form should limit users from submitting form data.

Figure 12.1 The max submits settings

With the max submit setting you can:

  • Specify how many times a form can be submitted from this page
  • Specify what to do when a max submits limit is reached:
    • Redirect the visitor to a specific page
    • Select or create a template to render

Finally, you can use the upload settings (Figure 13.1) to specify a path to where you want user-submitted files to be stored.

Figure 13.1 The uploads settings

The User Management settings (Figure 14.1) are used to create users on form submit and add them to one or more user groups.

This is particularly useful for signing users up for newsletters - simply add users to a newsletter group and use email marketing to target that group.

Figure 14.1 Creating users on submit

To use this feature:

  • Check the Create user on form submit and select one or more user groups to add new users to
  • Edit your form fields and map them to the corresponding user management field (Figure 14.2) 
Figure 14.2 Mapping field values to user management fields

When using this feature, you should always have a field mapped to the user management Email field.

The following behavior rules apply to this feature:

  • If the email corresponds to an existing user, only the email permission field and group membership is updated. This makes it possible to sign existing users up for newsletters. You cannot update other fields this way - use the Extranet app.
  • If no user with the email is found, a new user is created using the value from the email field as the Username and Email. Email permission will be set to 'true'. If mapped to, the following fields will also be updated on submit:
    • Name
    • FirstName
    • MiddleName
    • LastName
    • Address
    • Address2
    • Zip
    • City
    • Country
    • Phone
    • PhonePrivate
    • PhoneMobile
    • Company
    • Department
    • JobTitle
    • Any custom fields

You can override any setting from a Forms for Editors app by creating a field in the form (hidden or not) with the same name as the setting.

For instance, to override the subject of the mail being sent to the website owner when a form is submitted, create a field (hidden or not hidden) with the name “MailSubject”. Then the form handler will pick up the value from the form and use that instead of the value set on the paragraph app settings.


<form> <!--@Form.SystemFields--> <input type=”hidden” name=”MailSubject” value=”Custom subject…”> <!--@LoopStart(Fields)--> <!--@Field.Control--> <!--@LoopEnd(Fields)--> </form>

Here are some more examples to get you started.

Checkboxes can be set to checked by passing either “True” or the specified value of the checkbox:

<form> <input type=”checkbox” name=”enable” > </form>

By accessing the page with the form with the URL parameter ‘?enable=true’, the field will be checked:

<form> <input type=”checkbox” name=”enable” checked=”checked” > </form>

For checkbox lists, radio buttons and select boxes, by adding the field system name with the desired selected value to the query string the default selected option is bypassed, and the option(s) whose values are in the query string are set to selected.

A comma separated list of values can be used to set several options to selected for checkbox lists.

For instance, consider the following checkbox list:

<input type="checkbox" name="Pleasechoose" value="Extra" /> <input type="checkbox" name="Pleasechoose" value="Additional" /> <input type="checkbox" name="Pleasechoose" value="Even more" checked /> <input type="checkbox" name="Pleasechoose" value="Extra space" />

By accessing the page with the form with URL parameter ‘?Pleasechoose=Extra,Additional’ the specified fields will be checked (selected):

<input type="checkbox" name="Pleasechoose" value="Extra" checked /> <input type="checkbox" name="Pleasechoose" value="Additional" checked /> <input type="checkbox" name="Pleasechoose" value="Even more" /> <input type="checkbox" name="Pleasechoose" value="Extra space" />

You can also use query string parameters to post the form to itself and keep the values of the form.

When the form is submitted, the default action is the URL of the page the form is on.

The form has a hidden element called cmd with the value “save”. 

<input type="hidden" name="cmd" value="save" />

To use this type of post back of the form, set the hidden cmd field value to nothing.

Set the value of the field cmd to save when the content of the form is ready to be saved. When the form is submitted with cmd=save, the form will be saved, mailed and a confirmation sent.

When rendering the form, it is possible to override the value of the form fields by either submitting a value to the form with the same name as the field system name, or by adding a query string parameter with the system name and a value.

For example:

<form> <input type=”text” name=”firstName” > </form>

By accessing the page with the form with the URL parameter ’?firstname=John&20Doe’, the field will be filled with that value automatically.

<form> <input type=”text” name=”firstName” value=”John Doe” > </form>

See below for examples for specific field types.

Once a form has been filled out and submitted, the data is stored in Dynamicweb. It can then be accessed and downloaded from the Dynamicweb backend.

To access submitted form data, you can either right-click the form on the Forms for Editors form list and select Form data, or you can click Form data under the show settings (Figure 1.1) when editing a form.

Figure 1.1 Accessing form data

Either way will take you to the Submits overview (Figure 1.2).

Figure 1.2 The submits overview

From the Submits overview you can see all submits for the current form, including:

  • The submit ID
  • The date and time of submission
  • The page id of the page from which the form was submitted
  • The user name of the submitter (if the user is registered)
  • A summary of the form data (click the date column to see the full data for each submit)
  • The number of fields filled out in the form, and the IP & session key of the visitor

From the toolbar, you can export all the submitted data as either .csv or a .xls file.


These are the database tables associated with the Forms for Editors feature:


Contains setup data for forms created in the Forms for Editors app.

Field name Data type Length
FormId int 4
FormName nvarchar 255
FormEmailFieldId int 4
FormColumnShiftFormFieldId int 4
FormLabelOverField bit 1
FormLabelBold bit 1
FormLabelRequired nvarchar 255
FormAttenoDependencyFieldId int 4
FormAttenoEmailFieldId int 4
FormAttenoSettings nvarchar 255
FormMaxSubmits int 4
FormDefaultTemplate nvarchar 255
FormCssClass nvarchar 255
FormCreatedDate datetime 8
FormUpdatedDate datetime 8
FormCreatedBy int 4
FormUpdatedBy int 4
FormFieldSize int 4


Contains field definitions for forms (FormFieldFormID) in the Forms for Editors app.

Field name Data type Length
FormFieldId int 4
FormFieldFormId int 4
FormFieldName nvarchar 255
FormFieldType nvarchar 50
FormFieldDefaultValue nvarchar 255
FormFieldMaxLength int 4
FormFieldSize int 4
FormFieldRequired bit 1
FormFieldTextareaHeight int 4
FormFieldSort int 4
FormFieldActive bit 1
FormFieldText nvarchar Max
FormFieldImage nvarchar 255
FormFieldColor nvarchar 50
FormFieldAutoValue nvarchar 255
FormFieldSystemName nvarchar 255
FormFieldAttenoFieldName nvarchar 255
FormFieldCreatedDate datetime 8
FormFieldUpdatedDate datetime 8
FormFieldCreatedBy int 4
FormFieldUpdatedBy int 4
FormFieldGroupID int 4
FormFieldCssClass nvarchar 255
FormFieldPlaceholder nvarchar 255
FormFieldDescription nvarchar Max
FormFieldPrepend nvarchar 255
FormFieldAppend nvarchar 255
FormFieldActivityId nvarchar 50
FormFieldHideInReceipt bit 1


Contains option value for Form fields

Field name Data type Length
FormFieldOptionId int 4
FormFieldOptionFieldId int 4
FormFieldOptionText nvarchar 255
FormFieldOptionValue nvarchar 255
FormFieldOptionDefault bit 1
FormFieldOptionActive bit 1
FormFieldOptionSort int 4


Contains option values for multiple value fields (ForFieldOptionFieldId) such as dropdowns or radio button groups.

Field name Data type Length
FormOptionsId int 4
FormOptionsFormFieldId int 4
FormOptionsText nvarchar 255
FormOptionsValue nvarchar 255
FormOptionsDefaultSelected bit 1
FormOptionsSort int 4
FormOptionsActive bit 1


Tracks submits of forms (FormSubmitFormId) by ip (FormSubmitIp), page (FormSubmitPageId) and extranet user (FormSubmitUserId).

Field name Data type Length
FormSubmitID int 4
FormSubmitFormID int 4
FormSubmitDate datetime 8
FormSubmitIp nvarchar 30
FormSubmitSessionId nvarchar 30
FormSubmitPageId int 4
FormSubmitUserId int 4
FormSubmitReferer nvarchar 1000


Contains the data submitted (FormSubmitDataSubmitId) in a form field (FormSubmitDataFieldId)

Field name Data type Length
FormSubmitDataID int 4
FormSubmitDataSubmitID int 4
FormSubmitDataFieldID int 4
FormSubmitDataFieldname nvarchar 255
FormSubmitDataValue nvarchar Max