This event is triggered whenever a visitor submits a form on a site page.
Example: A form is submitted where formName
is decemberSurvey
When the page developer adds a form to a site page, he or she includes a formName
parameter in the JSP or JHTML code for the form. The Scenarios module uses the value of the formName
parameter to identify the form that the visitor submits. If the page developer does not specify a formName
value, the value of the absoluteName
property is used instead; for example, the formName
of the /atg/userprofiling/ProfileFormHandler
component defaults to /atg/userprofiling/ProfileFormHandler
.
Note that forms do not trigger this event by default; you must set the sendMessages
property of the form handler component to true to have this event work correctly.
Class name |
|
JMS name |
|
Display name | A form is submitted |
Message context | Request |
Message scope | Individual |
Message source | Component: Class: |
Component that calls the message source | An instance of |
How this event is triggered | Triggered by the form handler component after the visitor submits the form. |
How to turn this event off | Set to false the |
The message that triggers this event contains the following properties:
Property | Type | Scenario Editor Label | Description |
---|---|---|---|
|
|
| The name of the form that the visitor submits. |
|
| Does not appear. | The ID of the current site. The value is provided by the Site Context Manager. This parameter applies to multisite environments. |
|
| Does not appear. | The IDs of the site groups associated with the current site. The values are provided by the Site Context Manager. This parameter applies to multisite environments. |