Content Panel Web form

Web Form Styles

The default RPI form CSS styles are contained in the stylesheet ‘/RPIFormValidation/shared/css/validation.css’

The following table contains the HTML class names used by RPI to control web forms and their elements:

For each form element, the Field name property is used as the element’s ID.

Submitting a Web Form

When displayed in a landing page in a web browser, a web form contains the following:

• Form header, with CSS applied as defined at the web form.

• Elements, accordant with their properties at the web form, and any CSS settings applied, are listed in the order defined by the web form. These can include:

  • Static HTML

  • Textbox: if a RegEx is supplied, the value entered must be accordant with its stipulations.

  • Radio buttons

  • Checkbox

  • Dropdown: the first value in the Values list is selected by default.

  • List: shown as a series of checkboxes

  • Email: the value entered must be a valid email address.

  • Date

  • Hidden: the form element is not shown

If a form element is required, its label is accompanied by an asterisk. If the form's Required field text property was set, it is displayed at the top of the form.

If any elements’ HTML class name properties have been set, the class style or scripts thus referenced are applied to the elements. Classes referenced can be included in the form’s Style and script HTML elements property, the WebFormDefaultStyleScripts system configuration setting, or a manually-supplied reference. This applies when the form is used in an RPI landing page, or an external web page.

Note that it is necessary for a site visitor to clear his or her browser cache to pick up any changes to a forms’ referenced style sheets. Also, if style sheets are changed, you will need to clear your local Internet Explorer cache to view such changes at the form’s usage within the Landing Page Designer, at that interface’s Preview section.

Submit button

A web form can only be submitted when all required fields have been completed, and when the values in all fields are valid.

On submission of a web form:

• The browser is redirected to the URL configured in the form’s Redirect URL property

• Notification of the form’s submission is sent to all email addresses configured in the form’s Email notification list property.

The mail sent has the following properties:

• Subject: ‘Web form submission – [Form Name]’

• Body:

'A new web form submission for form [Form Name] has been processed

[Email notification message]

Form details:

• Form identifier

• [Details of each field in form, with value(s)]’

• The data in the form are passed to a private Microsoft Message Queue called rpiwebformsubmission. This queue is flushed every time system task Web form processor is run.

• On flushing the queue, the Web form processor task writes the form data to three data warehouse tables:

  • RPI_WebForm: this table contains one row per unique web form. It contains the following columns:

    • FormID (PK)

    • FormName

  • RPI_WebFormSubmission: this table contains one row per unique instance of a web form's being submitted. It contains the following columns:

    • FormSubmissionID (PK)

    • FormID

    • SubmissionDate

    • EmailAddress: populated if email is provided in the form.

    • ChannelExecutionID: populated if directed to the web form by an RPI email.

    • RPContactID: populated if directed to the web form by an RPI email.

    • VisitorID

    • Fields: this field is used when system configuration setting FormSubmissionPersistFieldsAsJSON is set to True. It is used to persist form field submission data in JSON format, e.g.:

{

"FieldName": "email",

"EmailFieldName": "some.one@redpointglobal.com"

}

• RPI_WebFormFieldSubmission: this table is used when system configuration setting FormSubmissionPersistFieldsAsJSON is set to False. It contains one row per piece of data submitted within a web form. It contains the following columns:

  • FormFieldSubmissionID (PK)

  • FormSubmissionID

  • FormID

  • FieldName

  • FieldValue: note that checkbox values are shown as ‘True’ or ‘False’. If multiple values are selected within a list, one row per selected value is added. A hidden field is always set to its Value, as defined at the web form.

If a web form is hosted on a landing page configured with a Matomo adapter, a form field called ‘rpiTrkPiwikVisitorID’ is used to track the Matomo visitor ID.

You can optionally define that any submitted web form data are written to the realtime cache. This is carried out by setting the value of the following web processing website web.config setting to True:

<setting name="CacheWebFormData" serializeAs="String">

<value>True</value>

</setting>

When set in this way, the realtime cache is populated with all data submitted at web forms. You can then leverage this data to execute generic realtime decisions in respect of the same. For further information on realtime decisions, please see the Realtime Decisions documentation.

On submission of a web form at which a Queue listener interaction and workflow is selected, a JSON package is automatically placed on the listener queue and is picked up by the queue listener with which the web form is submitted. Any queue activities downstream from the queue listener are fulfilled.

If such a queue activity is configured with an email offer, the email is delivered to the email address as submitted in an Email form element. If any web form element parameters are included in the email offer's content, the values submitted in the web form are substituted. If the web form does not contain an Email element, emails are unable to be delivered (the queue activity's Log, as displayed in the Results Window, advises of this fact).

Web Form File Metadata

When a web form associated with file metadata is published, a row is added at data warehouse table RPI_WebForm_Meta:

• PublishHistoryID: you can use this field to join to RPI_WebFormSubmissions

• PublishDate

• FormName

• FormMeta: stored as JSON; large varchar field by default