Overview

qSIListForm is a form that displays data from external systems, such as SQL Server, Web Services, K2, or Salesforce. It allows you to associate a custom toolbar button with one or more actions, and enables you to write complex validation logic.

This web part validates the following properties before setting them:

•	Form Component Behavior. If this succeeds, it will execute the custom action.

•	Fields that are marked as required. See Required.

•	Displayed Fields Type (if Number is selected as the type). See Type.

qSIListForm allows you to:

•	define a mask for the input. Enforcing the format increases the consistency and data correctness.

•	create a description for each field. The description can be plain text or HTML.

•	define a new title for the field. This is useful if the title is too long or if you want to display a different title for the field.

•	assign a fixed value to a field.

•	assign a formatted value to a field based on values in other fields. The only requirement is that the parent fields must precede the field to be assigned.

•	fill the value of a field from a value stored in the Session variable. This feature usually works in conjunction with another web part, such as qSISelector or qSIListView.

•	auto-fill a certain field based on field in a consumed row.

•	implement the IWebPartRow interface to provide a row to another web part, such as qSIListView or qSISelector.

•	hide a field. A hidden field is processed during postback, but it will not be displayed.

•	create a read -only field.

•	define a CAPTCHA field thereby enhancing the authenticity of entered data.

•	define static text as separator for a field or group of fields in a field display sequence.

•	define header and footer fields in various form layouts.

•	store the displayed, new, or updated items into the Session. This feature enables a List Form to communicate with another web part, such as qSISelector in another page.

•	display, create, and edit data in your external systems. Out of the box, this Web Part supports the DAO Provider for:

•	Web Services

•	SQL Server

•

Oracle

•	Domino Server using XML over HTTP

•	Salesforce

•	K2Server (for SharePoint 2010 only)

•

Define a different title for different languages using the Resource List and the Title Resource ID properties. You can also define different texts for the buttons in the list form toolbar for different languages. The culture for the page can be defined by appending the Culture HTTP parameter to the page URL; for example, http://hostname/sites/sitename/default.aspx?Culture=en-US

 

TIP: To better understand SI web parts, read the System Integration Developer Guide.