Access
To insert a Form object, you must either:
Choose the Adelia Web Studio Objects/Form option from the Insert menu in the Macromedia Dreamweaver window.
Click on the corresponding button
in the Adelia object insertion bar in Dreamweaver.
This dialog box lets you define the different attributes of the Form object.
Important: The Form object is required in order for a Web page to function correctly as part of an Adelia Web Studio application. All the elements in the insertion bar must be placed on the form.
General
Data entry
Name
Form name.
Styles
Upload form
Checked |
When an ::ADELIA_EVT_UPL event is processed, any Adelia Upload objects in the form are processed by uploading the selected files. |
Not checked |
Any Adelia Upload objects in the form are ignored (i.e. the selected files are not uploaded). |
Maximum upload size
Maximum total size of the files in the form that are uploaded when an ::ADELIA_EVT_UPL Adelia event is processed. You can restrict the size of the files processed by setting a size limit in kilobytes (1024 for 1 Mb, etc.). Alternatively, you can use an ::MY_VAR Adelia variable to set a size limit per program.
If this field is left blank, no size limit is enforced.
Note: This size is defined as the total size of the query submitted by the browser when the form is submitted. As such, it includes not only the size(s) of the uploaded file(s), but also the size of the data for any other controls created (input fields, check boxes, etc.) and the size (approx. 1 kb) of the hidden data used by the Adelia Web program.
Therefore, any value set for this parameter should be treated as an approximate value.
The uploaded data volume is checked not by the browser, but by the Web application server once the data has been sent. Therefore, you should test the value of each Upload object's ERROR_CODE property in the 4GL code before retrieving the object's value.
Browser-side syntax validation error message
Determines the display mode for error messages resulting from the syntax checking of the field values placed in the form before an Adelia event is triggered by the browser.
The fields concerned by the syntax checking are Entry field, Autosuggest and Upload objects.
This checking is carried out by the browser before triggering the following type of Adelia event: Event, Upload event, Back pagination or Forward pagination (Event without validation-type events do not trigger syntax checking).
In both modes, error detection aborts the triggering of the associated Adelia event. The chosen mode applies to all events with validation associated with Adelia objects placed in the form.
| In the alert box | When the first value syntax error is detected in a zone, a system box containing the error message is displayed and the focus is set to the field with the error. Default display mode. |
In the error tag |
All the field values are checked. When an error is detected, an error message is displayed in the error tag associated with the field (if this tag exists) or in the standard error tag if applicable. The focus is set to the first field with an error. The detection of an error adds a specific empty CSS class for each type of field:
|
By redefining these classes in a CSS style sheet, the field with an error can be highlighted.
Example: redefining the AWSVerificationErrMonolineEntryfieldclass as follows makes it possible to add a 3-pixel-wide red outline at a 2-pixel distance around the monoline entry fields with an error:
. AWSVerificationErrMonolineEntryfield {
outline: 3px solid red;
outline-offset: 2px;
}
In this mode, messages sent (in the standard error tag or in the error tags associated with the form fields) concerning application errors are deleted so as to only highlight error messages produced by syntax checking.
Buttons
OK
This button validates the information entered and closes the dialog box.
Cancel
This button closes the dialog box without validating the modifications made.
Keyboard shortcut: Esc.