Commands for managing dynamic templated forms.
* indicates required
Public Methods:
Determine whether a form exists by checking for its data structures.
|
Generates hidden input tags for all values in a form submission. Typically used to create a confirmation page following an initial submission.
|
Initialize the data structures for a form.
|
Return a list which represents the result of getting combined values from multiple form elements
|
Return the number of elements in a form
|
Return true if a submission in progress. The submission may or may not be valid.
|
Return true if preparing a form for an initial request (as opposed to repreparing a form that is returned to the user due to validation problems). This command is used to conditionally set default values for form elements.
|
Return true if submission in progress and submission was valid. Typically used to conditionally execute DML and redirect to the next page, as opposed to returning the form back to the user to report validation errors.
|
Set local variables for form variables (assume they are all single values). Typically used when processing the form submission to prepare for DML or other type of transaction.
|
Set the name of the current section of the form. A form may be divided into any number of sections for layout purposes. Elements are tagged with the current section name as they are added to the form. A form style template may insert a divider in the form whenever the section name changes.
|
Private Methods:
Auto-generate the template for a form
|
Helper procedure used to access the basic data structures of a form object. Called by several of the form commands. |
Iterates over all declared elements, checking for hidden widgets and rendering those that have not been rendered yet. Called after rendering a custom form template as a debugging aid.
|
Render the HTML FORM tag along with a hidden element that identifies the form object.
|
Render the finished HTML output for a dynamic form.
|
* indicates required