Do you want to have a new form created or convert an existing form from iProx to Drupal? Then first think about how the form should be set up, in consultation with the content expert. Think about:

Context

• What is the context in which the form is shown to the user? How will the form be made part of the customer journey(s)? 
  • Will the form be linked to a service, or should the form be in the menu? If the latter, where in the menu?

Content

What is the context in which the form is shown to the user? How will the form be made part of the customer journey(s)? Will the form be linked to a service, or should the form be in the menu? If the latter, where in the menu?

Submission

• By what date should the form be online? By what date should the form be taken offline again, or should it remain online permanently?
• What should happen after submission of the form?
  • Who should receive the completed form and in what way (by e-mail and/or by logging into Drupal)?
  • What is the text that should be shown on the confirmation page after the form is sent?
  • Should the user receive a confirmation by e-mail and if so, what is the text that should be in the e-mail?
  • Should the sending of the form be measured via our web statistics? If yes, a confirmation page with unique url should be shown after submission.

Provide all required information in both Dutch and English.

Other

When an existing form needs to be converted from iProx, it is important to look critically at the old set-up and not copy it without reason. Could different forms perhaps be combined into one form? Is it really necessary to ask for all this information? Is the design and layout of the form customer-friendly?

Also advise the content expert on possible improvements to the internal process. Think about requiring a so-called 'wet signature': is this really necessary, or can the form also be signed digitally (or is signature not actually necessary at all)? Can the user be more clearly told how follow-up will take place after the form is sent? Etc. It is not up to us to improve internal processes, nor should we wait for this until we create a form, but we do have a signalling and advisory role in this.

Send the proposal for the concrete layout of the form and the detailed requirements you cannot put in the form to the CMS team ([email protected]). Do you work at a faculty? Then you can send your request for a form to these faculty key users:

• Philosophy, Theology and Religious Studies: Denise Brijan, [email protected]
• Arts: Lara Severens, [email protected]
• Law: Dennis Arns, [email protected]
• Management: Merel Riechelman, [email protected] and Malou Remmerde, [email protected]
• Science: Sebastiaan Kuiper-Schutijser, [email protected]
• Social Sciences: Demi Hendriks, [email protected]

Preferably make an outline of the layout of the form and, if relevant, a flowchart for forms with interdependencies. Please use the template below so that all information is delivered complete. Submit the document below at least 3 days before you want to use it.

The CMS team or the key user of your faculty will create the form for you in Drupal. They will notify you when the form is ready in Drupal for a final check. After approval, your form is ready to use! 

You can now embed the form in a content type via the 'form' content block.

Note: always embed a form in a content type; do not link to the form page itself. The url of a form is not based on where it is located on the website, so the visitor would not understand where they are in the website. In addition, it creates problems in measuring the use of the form.