From The Field

<Data>

<Name>YourConnectionName</Name>

<Default>True/False</Default>

<ConnectionType>ADO</ConnectionType>

<ConnectionString>YourConnectionString</ConnectionString>

<Query>Your SFW Query</Query>

</Data>

Property Name / Element

Property Use / Function

<OutputType>

When omitted, the default is “text/xml” however “text/html” and ”text/plain” are also supported

<XslStylesheet>

Actual XSL to transform the response from your Provider. However, it is recommended to use an attached stylesheet (see next property) as opposed to including your XSL in line here.

<XslStylesheetLocation>

The URL to the location of an XSL stylesheet (can be .xml, .xsl or .xslt) to be applied for transforming the Provider response. This transform occurs *before* the data is rendered or passed on to another component.

<ErrorRedirect>

A URL to redirect a user/connection to when the connection called results in an error.

<ReportErrors>

A true/false flag to indicate whether errors are reported. If set to “true”, and an <ErrorRedirect> is specified, the error message will be attached to the redirect URL as: ErrorRedirectURL?Error=(Error Message)

<RedirectTo>

The URL to redirect this connection to upon successful completion. This is the ability to take the response from one connection and instantly pass it into another to complete a process or validate a response. If you specify a parameter in the RedirectTo, you can pass the value of the initial connection using a pre-defined variable called %Data%.

Ex. http://site.net/subsite/providers/ADO.aspx?

ConnectionName=SecondConnection&FirstValue=%Data%

<RDConnection>

The URL to pass the results of this connection into. This is different than a <RedirectTo> which literally forwards the request on to a new page/connection. With an <RDConnection>, the results of the first connection are passed into a second connection for use in processing said connection, and the results of the second connection are then returned to the first one. This is most useful when needing to send a collection of XML into a second connection since, with the RedirectTo, the entire response of the first connection is passed via query string variable; see the next property for setting the XML elements you wish to post into the second connection.

<RDConnectionPost>

A property for specifying (via XPath) the XML results from your first connection that you wish to post into a second connection, as well as the parameter names to use when posting them. The <RDConnectionPost> also supports setting a default value to pass for a parameter, should the XPath for the parameter value not exist within the first connection’s result.

<Values>

The Values element simply holds empty child nodes representing each and every parameter that you wish to pass into this connection. Thus, if you plan to pass in a parameter called “Department” into your connection for use in your query, you would need a self-closing <Department /> element inside your <Values></Values> elements. This has the effect of letting the connection know to look for a GET/POST parameter with the name specified. There is no limit to the number of parameters you can list here.

<CacheOutput>

A true/false value indicating whether or not the output from this connection should be cached. If set to “true”, you can use the following three properties to customize the cache label and/or duration. Absent any of the following properties, the default label will be TheConnectionName+”Output”+WebPartID with a duration of 200 mins.

<CacheLabel>

A text value to specify the cache label; if not specified, the default Web Part ID will be used for this portion of the cache identifier.

<CacheAddUserID>

A true/false value indicating whether or not to add the ID of the user running the connection to cache label; this is akin to a cache per user mechanism. If set to “true” the User’s ID will be added to the end of the cache label.

<CacheDuration>

An integer value indicating the cache duration in minutes.