Forms documentation

Owned by Peter Roper (Unlicensed)
Last updated: 01 Oct, 2024 by Jo Tayler
3 min read

Single Digital Presence (SDP) has created a webform product that makes it easy to collect information from a website user.

On this page:

Status

This is an SDP Core feature and is, therefore, available on all SDP websites without requiring any custom development work.

Features

  • Free and embeddable in SDP CMSs

  • All standard form elements are available

  • Conditional logic can be applied to show or hide fields, and/or make them required or optional

  • You can create templates to reuse and save time when building forms

  • When building, you can drag and drop to adjust the order of fields in your form

  • The outputted forms and the administrative interface (i.e. form builder) are accessible using keyboard navigation and screen readers. The Webform module complies with WCAG 2.0 and ATAG 2.0 guidelines.

Use cases

Webforms are most appropriate for:

  • services or transactions that, to be completed, need to collect the same specific information from everyone

  • providing an alternative option for phoning, emailing or visiting in person

  • when the transaction being conducted via the form can be completed completely online (there is no additional requirement to phone, fax, post, email or visit in person in order to complete the form)

  • allowing anonymous feedback to be provided

  • providing an interactive decision tree.

Examples

Current implementation

Specifications

Learn about how the CMS webform works and when to use it in your design at the Ripple Design System Form page.

Third-party integrations and submissions

Data submitted through an SDP webform does not have to be stored in the SDP CMS. The webform can send data directly to an existing database or platform. This is typically managed on a case-by-case basis, so if you’re interested, talk to us about how it might work.

SDP webforms have been successfully integrated with Salesforce CRM, ServiceNow and other third-party systems.

CMS editor access

CMS editors will be able to create online forms. However, for non-independent SDP websites, new forms must be sent through to the SDP content team for final approval. 

Once an online form is created, the CMS editor can access the form to create updates or download reports. The CMS editor currently doesn’t allow edits or download reports on other online forms that other CMS editors have created. 

Collecting customer data

The platform is only classified to collect data up to the level unclassified, and doesn’t support data lifecycle management (DLM). This means no 'sensitive personal information' can be captured in any forms.

Sensitive information includes:

  • health (including predictive genetic information)

  • racial or ethnic origin

  • political opinions

  • membership of a political association, professional or trade association or trade union

  • religious beliefs or affiliations

  • philosophical beliefs

  • sexual orientation or practices

  • criminal record

  • biometric information that is to be used for certain purposes

  • biometric templates.

Read more at the Federal Government’s https://www.oaic.gov.au/privacy-law/privacy-act/australian-privacy-principles page.

Each webform must include a collection notice, which you can read about on our Privacy requirements for webforms page.

Collection statement and privacy impact assessment

For surveys and forms that collect user data, you must consult your department’s privacy officer, information strategy team, or equivalent.

Each webform must include a collection statement and a privacy impact assessment (PIA). This is usually placed at the end of the webform just before the ‘submit’ button. SDP must have a copy of these.