Advanced guide: Drupal webform settings
- Hayley Stockall (Unlicensed)
- Marcella Marino
This guide walks you through the 7 sections found under a Drupal CMS webform’s “Settings” tab.
Not all of the settings visible in the CMS back-end are configured to work/display on the front-end.
Looking for information on how to create a webform? Read our basic guide or our advanced guide.
On this page
General settings
In this section you can:
update your form’s title (visible within the CMS)
add or edit an administrative description (visible within the CMS)
assign the form to a category (visible within the CMS)
archive a webform that is no longer in use
disable webform submissions from being saved in the CMS
If selecting this option, you will need to set up an email address for submissions to be sent to, otherwise you won’t have access to any form submissions.
change the author of the form to a different CMS user.
Form settings
None of the settings in this section are currently configured.
To “close” your form to the general public, please remove the form embed component from the webpage and republish the page.
Once you have cleared out the form submissions, archive the form by ticking the checkbox in the General settings section.
Submissions settings
In this section you can:
change the “next submission number” that will be assigned to the next submission that comes through
This number starts at 1 for a new webform. You may want to reset this number back to 1 once you have finished testing your webform.
Confirmation settings
In this section you can:
change the confirmation type setting to “Inline (reloads the current page and replaces the webform with the confirmation message”.
It is strongly recommended to choose this setting, as it will prevent users from submitting duplicate submissions and makes the confirmation message stand out more.
add a custom confirmation message, that can include standard basic text formatting such as headings, lists and hyperlinks.
If left blank, the default confirmation message is “Thank you! Your response has been submitted.”
Note: Webform tokens (e.g. displaying the submission ID number) aren’t currently configured to work on the front-end display.
Emails / Handlers settings
In this section you can:
set up emails to be sent to yourself or your team
set up emails to be sent to the person who submitted the form
set up emails to be sent to Customer Relationship Management Software, such as Salesforce.
For this option, you will need assistance from the SDP team. Log a general support request to discuss this further.
Note: The From email address should never be changed – this must remain as the default [site: mail] option, otherwise the emails may not send or may land in a spam folder.
It’s possible to set up multiple email options. For each email option you can:
give it a title in the back-end – this isn’t visible in the emails, so can be just left as the default text. It can be useful to give a specific title if you’re setting up multiple options though.
add any administrative notes – also just visible in the back-end.
add the email address you want to send the submissions to
For internal emails, choose the Custom option and add the email address in the field below.
To send a confirmation email/receipt to the person who filled in the form, choose the relevant email element option in the dropdown menu.
add a custom email to CC or BCC in each email.
add a custom “from” name to appear on the email
You can’t change the “from email”. This will appear on emails as “noreply@dpc.vic.gov.au”.
add a custom reply-to email address
add a custom email subject line
add custom email body text, formatting and tokens – the default options include the date of submission and all of the information supplied in the form
choose whether to exclude any elements left empty and/or any checkboxes left unticked
apply conditional logic, to enable or disable the emails based on whether particular conditions are met.