Sandy Mollema
posted this on June 09, 2011 10:17

With a custom form, you provide the complete HTML for the form — the ‹form›‹/form› tags and everything in between. (You may also include non-editable content outside the ‹form›‹/form› tags.)
By default, ‹input› and ‹select› tags will be saved with the names of their IDs, although you can override those and assign them to Data Collection fields if you prefer when editing fields from the next page.
The choices for checkboxes, radio buttons, drop-downs and list boxes should be included in your custom HTML. However, you can optionally substitute the choices in ‹select› drop-downs and list boxes by assigning them a choice set when editing fields from the next page. Note that currently all ‹option› tags in your HTML must have closing ‹/option› tags.
The data collected on your custom HTML form will be saved into the LiveBall database upon form submission. You can also export the data collected on a custom HTML form using any export format supported by LiveBall. Form-level advanced rules will be available to leverage, as well!
You must provide your own button to submit the form.
You may also include ‹style› and ‹script› blocks, usually in front of the ‹form› tag, to impact the look-and-feel and behavior of the form. (Be careful to avoid CSS and Javascript conflicts with your master page templates and themes.)
Navigate to the 'Forms' library and select (or create a new) the category you would like to add your custom form to. Add a new form by selecting the green '+form' button.