The FormCollection allows developers easy access to the name-value pairs contained in the body of an HTTP POST request.

FormCollection provides a number of utilities to help developers quickly access the names and corresponding values in the post content from a form. The body of the request must be structured in conformance with the form content type of application/x-www-form-urlencoded. In general, a form in a web page or most web libraries will follow this convention. More detailed information can be found in the HTML 4.01 specification.

To initialize a FormCollection variable with the post content from an incoming GotRequest event, set the InitializeWith property of a variable in the event handler to the event parameter Body.

To read a form field in from the FormCollection type, use the .NET indexer syntax on the variable, specifying the name of the form field as the argument to the indexer. For example, if one had a variable of the name post, and wanted to know the value of a form field called 'user', then the C# snippet post["user"] would resolve to that value. Note that one can use the GetValues( System.String ) method to return a string array, which is the more appropriate option if your form defines the same field name more than once.

To programmatically determine all the form fields passed in, three members defined by FormCollection in particular are of interest. One is the Count property, which will indicate how many fields are defined in total. Using that as a loop count, one can then use the GetNameAt( System.Int32 ) method and this[ System.Int32 ] indexer to determine the name and value(s) of each form field defined in the request. For example, one can build a CustomCode action that takes a variable named post as an argument, and iterates over every form field like the below example:

public static string Execute(Metreos.Types.Http.FormCollection post)
{
    for(int i = 0; i < post.Count; i++)
    {
        string post = post.GetNameAt(i);

        string post = post[i];  // note that one may want to not use the indexer and instead 
                                // use post.GetValuesAt(i) if the field has multiple string values

        //perform logic...
    }

    return String.Empty;
}

None.