Confirmation emails Approval emails

Data insertion into a CentralPoint module Data insertion into a third-party database Creation of a user/member profile Data submission to web requet/response page

Creating Forms

To begin a new form, locate the Forms Management link in the console and click it. The system will automatically send you to the grid view of the Forms module. Click the "New" button in the upper left- hand corner of the grid view to create a new form.

Within the Forms module, the "General" tab allows administrators to build the form to their specifications. This tab contains the following fields: System Title, System Caption, Publish Start Date, Publish End Date, Results, CpSCript, Manage Form Buttons, Submit Button, Cancel Button, PRevious Button, Next Button, Number of Pages, Page 1 through Page 10, Completed, Thank You Message, Prevent Multiple Submissions, Display Status and Audiences.

The "System Title" field is used for console purposes only, but should contain a label that administrators can recognize.

Likewise, the "System Caption" field is used within the console only. Administrators can insert a 512-charactrequireder description for the form's function within this field.

Administrators can set the date range in which the form is available for display on the front end by altering the "Publish Start Date" and "Publish End Date" fields. Take note, too, that you can begin and end the form's display at a precise moment in time by using the hour, minute, second fields.

The "Results" field provides administrators with a link to their form's submission results. This link is also displayed on the module's grid view.

The form that administrators build is referenced through the "CpScript" field. Administrators can copy the contents of this field and place it within a page (or any other RTF field that supports CPscripting) to display the form. A "copy link" feature is also available in the grid view of the Forms module.

"Manage Form Buttons" is a switch (Yes/No) that allows administrators to insert their own custom image buttons that will display as part of the form. Choosing "No" means that CentralPoint's default buttons will display. Choosing "Yes" allows administrators to upload a button for the following actions: "Submit", "Cancel", "Previous Page", "Next Page".

Administrators can define the number of pages a form will contain by choosing the appropriate number from the "Number of Pages" radio button array. Choosing more than one page will trigger the console to display a new RTF editor that corresponds to that page number. The front-end display will always default to the "Page 1" information, and users can toggle from page to page using the "Previous Page" and "Next Page" buttons. Administrators can require users to enter form item values to move from one page to the next. More about that in the "validators" section below.

The "Page [n]" RTF field is where administrators build the form elements. CentralPoint currently supports these form elements:

Text box - [cp:literal:scripting key='FormTextBox' id='Name of Item' /]

Multi-line Text box - [cp:literal:scripting key='FormtextBox' id='Name of Item' TextMode='MultiLine' Rows='5' style='width:250px;' /]

File Upload - [cp:literal:scripting key='FormUpload' id='Name of Item' /]

Check boxes - [cp:literal:scripting key='FormRadioButtonList' id='Name of Item' SelectionMode='Multiple' AddListItems='<listItem value="Item1" index="1">Item2</listItem><listItem value="Item2" index="2">Item2</listItem><listItem value="Item3" index="3">Item3</listItem><listItem value="Item4" index="4">Item4</listItem>'/]

Drop-down menu - [cp:literal:scripting key='FormListBox' id='Name of Item' AddListItems='<listItem value="Item1" index="1">Item1</listItem><listItem value="Item2" index="2">Item2</listItem><listItem value="Item3" index="3">Item3</listItem>'/]

CAPTCHA validation - [cp:literal:scripting key='FormCaptcha' id='Captcha' /]

U.S. State list drop-down: [cp:literal:scripting key='FormListBox' id='States' SystemType='KeywordList' SystemName='StatesCodes' defaultValue='' PleaseSelect='Please select state...'/]

Country list drop-down: [cp:literal:scripting key='FormListBox' id='Country' SystemType='KeywordList' SystemName='CountryCodes' defaultValue='' PleaseSelect='Please select country ...'/]

Months of the year drop-down: [cp:literal:scripting key='FormListBox' id='Months' SystemType='KeywordList' SystemName='Months' defaultValue='' PleaseSelect='Please select month ...'/]

The form element attributes id is the name of the form field.  Underscores are valid, however dashes may not be used as part of the id.

The form element attribute selection and its value determines whether a radio button array displays or a check box array displays. Selection='Multiple' displays a check box array. The default is a radio button, or administrators can input Selection='Single' for a radio button array.

The listitem element attribute index determines where in the drop-down, check box or radio button array the item appears. Index="1" displays the item first.

The listitem element attribute value is the value of the list item and is equivalent to the <option value=""> attribute in HTML.

A full list of attributes and their values can be found in the Scripting help file. There are also a number of built-in jquery elements referenced in the Scripting help file that can help you extend the functionality within your form. In that scripting help file, search for any of the following terms: ExtAutoComplete, ExtDatePicker, ExtPasswordStrength, ExtMaskFormInput, ExtWaterMark.

The "Completed" field allows administrators to determine the action upon form submission. Choosing "Thank You Message" allows administrators to display the contents of the RTF "Thank You Message" field. Upon submission, the "Thank You Message" field will appear in place of the form itself. The "Thank You Message" RTF field is required if the value of "Completed" is "Thank You Message".

Alternatively, administrators can redirect their form submitters to a specific page by choosing the "Redirect" option. The value of the "Redirect URL" field governs where the form submitter will be redirected to. The "Redirect to URL" field is required if the value of "Completed" is "Redirect".

To prevent more than one submission of a form by the same person in a one-year period, choose the "Yes" option on the "Prevent Multiple Submissions" field. The "Yes" option sets a cookie on the form submitters browser that will prevent that submitter from sending in more than one form in the time frame that you choose in the "Intervals" and "Interval Values" fields. To limit a user to one form submission per day, choose "Days" in the "Interval" option, and insert a numeral 1 in the "Interval Values" field.

Choose "No" to allow any number of forms submissions from the same person.

The display status option allows administrators to toggle on and off the display of the form on the front end. Choosing "Hold" will not allow the form to display on the front end. Choosing "Release" displays the form on the front end.

The Audiences multi-select field is used for console filtration only, meaning that administrators can limit the display of the form within the console to only certain administrators by audience. This value doesn't affect the front-end display of the form.

Many forms require specific fields to be validated before the form itself can be submitted. Below are the types of form validations CentralPoint supports.

Property	Description
id	The id of the form validator. This required property allows the form state to uniquely identify this validator within the group.
itemToValidate	The id of the form element to validate.
type	Integer - minimum and maximum String - minimum and maximum characters Decimal or Currency- minimum and maximum Date - any valid date in .NET help file
minimumLength	The minimum number of the characters the field must have.
maximumLength	The maximum number of the characters the field can have.
minimumValue	The minimum integer of your range.
maximumValue	The maximum integer of your range.
defaultValue	The Error Message user will see if the submitted value does not pass the required validation.
errorColor	Optional property. Can contain Color HEX value(Example: FF0000 or FFFF00) or Color Names (Example: red or yellow)
ItemToEnable	Optional property. Loading...