Harness, section, and flow action forms
Implementing dynamic form actions and the Client Event Editor
|
|
C-1990 GROVS To reduce the size and complexity of work object forms, you can hide, show, or alter parts of the runtime presentation of harness, section, and flow action forms based on user input. Additionally, you can cause sections to repaint based on user interactions. GRP-224
For example, if a user selects 3 in a field labeled Children, the work object form can quickly change to present three input fields, to collect the name or other information about each child. Similarly, if a user checks a box labeled Earthquake Coverage?, fields appropriate and specific to that situation can appear.
The field to which an event is linked is known as the controlling field. Other fields that may become visible or hidden are known as the controlled fields. In the first example, the Children field contains the controlling field and the Child Name fields are controlled.
Internally, user interactions trigger the JavaScript events
OnBlur, OnChange, and OnClick that
then execute built-in JavaScript functions to change or refresh the
form.
1. Establish the
controlling field with the Client Event Editor
Use the Client Event Editor to associate an event with the value that the user enters into an input field for a property. C-2526
1. Consider the HTML Property rule that is to be used to present
the controlling property. This rule may be identified in the
Control field of the panel. Click the Preview
toolbar button (
) to see an approximate runtime presentation.
2. Click the magnifying glass icon (
) on the Behavior field
to start the Client Event editor in a new window.
3. Complete the Client Event Editor form. See Help — Client Event Editor.
2. For each
controlled element, enter a Condition
|
AJAX |
|
Harness, Section, and Flow Action forms — Fields — Adding a Text box |
