2020.2

12. Close the dialog. Now you can start adding elements to the Form (see "Using Form
elements" on page540, "Form Elements" on page702, and "COTG Elements" on
page689).
Changing a Form's properties and validation method
Once a Form has been added, you can of course edit its HTML code directly in the Source view
of the workspace. Apart from that, there are a number of dialogs to change a Form's properties
and validation settings.
Changing a Form's properties
1. Select the form (see "Selecting an element" on page616).
2.
On the Attributes pane you can change:
l
The ID and/or class. ID's and classes are particularly useful with regard to variable
data (see "Personalizing content" on page770) and styling (see "Styling templates
with CSS files" on page727).
l
An Action: the URL where the form data should be sent. The URL should be a
server-side script that can accept form data (a Workflow process that starts with a
Server Input task, for example).
l
A Method: this defines whether the form should be sent using the GET or POST
method.
l
An Encryption Type (enctype):
l
application/x-www-form-urlencoded: Default. All characters are encoded
before they are sent. Spaces are converted to "+" symbols, and special
characters are converted to ASCII HEX values.
l
multipart/form-data: No characters are encoded. This value is required when
you are using forms that have a file upload control.
l
text/plain: Spaces are converted to "+" symbols, but no special characters are
encoded.
Changing a Form's validation method
In Connect PlanetPress Connect, there are two ways in which a Form's input can be validated:
l
The Browser validation method leaves it up to the browser to validate the user input.
When adding fields to the Form (see the next step) you can only make fields required and
Page 700