Home| Printable Version
The events section allows events to be associated with each field. This is achieved by specifying the script to execute when a particular event (e.g. onclick) occurs. FormMaker allows events to be associated with both the field and its label. Screenshot of Event Details The Show events for radio buttons are used to select whether to see the events associated with the field control or its label. The selected events will be shown in the area below the buttons. To add a new event, we simply click the New Event button. This will add a new row to the table for the new event. The Event select box is used to set the event we are interested in handling. This list of events includes standard web page events, such as when a key is pressed, when a cursor is hovered over a field, etc. However, one of these events - anchor activated - cannot be accessed unless an anchor button is chosen as the current field's control. Each event can be linked to any of the entries in the following select box - Action, which shows a list of actions that can be performed on any selected event. The adjoining Required Information section to the right of the action provides a set of details that depend on the type of action selected. In general, the Required Information section will provide a set of dropdowns in the first column that enable you to decide how to indicate the values for a given action. For example, for the Form Submission action, you will see an Action dropdown. You can select Show actions to view the list of predefined actions in the application map or select Enter action name to enter your own free-text action name.
The available actions in this list are described in detail below:
URL Location - This action type is only made available if an anchor activated event is selected; hence, its availability also depends on having an anchor button control. This enables standard URL based calls to be made to other parts of the application, or any other location. When selected, three fields will appear in the Required Information column. The Action dropdown list will hold the actions of the links connected to the Page (as set in the Required Information panel on the Application Map screen). These actions are different from those specified for the Form Submission action type: they will appear only if the submission method for this page is set to URL Parameters on the Application Map screen (see the Required Information section for information). Conversely, users may wish to enter a specific URI, which may be any valid local or Internet address, or choose a dynamic URI. In this case, an additional data binding will be required to specify where to get the URI from at runtime. If this option is chosen, any Set Value events defined for the anchor activated trigger will be converted into parameters added to the URL called. (Please note that field value type set value events are not supported in this case.) Form Submission - This action type is similar to the action type mentioned above, except that it enables the page to be submitted through the MVC architecture as a standard HTML form, to be processed by the application's server-side components. When selected, a dropdown list will appear in the Required Information column, and will hold the actions of the links connected to the Page. However, actions will only be present if, in contrast to the Target Location action type, the Form submission method is selected on the Application Map screen. The Validate checkbox can be enabled if the user needs to validate all the elements of the page upon submission. It performs a validation check on each of the page's fields, depending on the fields' data constraints. You can also choose to validate information based on server data. If this option is selected then don't need to enter anything further here, but will need to enter an XPath to locate the validation indicator within the server data in the Data Bindings page. AJAX Submission - This action type provides the ability to submit part of a page asynchronously and refresh another part independently, without having to refresh the complete page. Similar to the Form Submission method, the AJAX Submission requires an Action Target to indicate one of the links that was defined in the Application Map. Please Note: that the Action Target will contain a combination of the actions available from the partial page and the actions available from the page that contains the partial page. This action type also requires a Target Group. This is the group where the results from the asynchronous call will be placed. The Source Type option determines whether the submission should be made using the whole form data or data from a specific group. Finally, each AJAX Submission action provides the Validate option in the same way as for the standard Form Submission actions. Set Value - For this action type, when the specified event fires, a field in the page can be populated with a certain value of choice. The Target dropdown list contains the fields already present within the page. The Value Type list includes 3 options: for Static, the relevant target field will be populated with any user-specified value in the textbox area below; Dynamic will set the target field with a value depending on dynamic data (see Data Bindings); and Field allows users to set the target field with the value of another field on the page, to be selected from the Source dropdown list below it. Group Toggle - This straightforward action type enables the use of showing or hiding a group when the selected event is fired. You can also tick the Animate checkbox to achieve a rollover effect when hiding and showing the group information. Custom Script - For more advanced use, customised script can be inserted into the generated XSL by filling in the textbox for this action type. This can be any script code supported by web browsers (i.e. JavaScript), including calls to functions defined elsewhere.
To remove an existing event, we simply need to click on the remove (x) button alongside the event to remove it. Multiple events can be defined for the same Event Trigger, and they can be reordered by using the up and down arrows at the side of each event entry. An example use for this feature would be to validate and submit the web page when a button is clicked. In this case you would create a new button control, and then use either the onclick or anchor activated Event Trigger to specify the function. Then, selecting the Form Submission action type, selecting the action defined for this page, and clicking on Validate, should be all that is needed to successfully submit a page. For more information see the How To Guides in the FAQ, located at.
Visibility Details Data Constraints