Geocortex Workflow Help
Open topic with navigation
In Geocortex Workflow, an event is something that happens in a form. This could be an action by the user, like a button click, or a step in the form's life cycle, like the validation step after the user has submitted the form.
Events allow you to monitor what is happening in the form and customize how the workflow responds. For example, you could monitor a checkbox and show additional form elements if the user selects the checkbox. To customize the response, you add a subworkflow that defines the custom behavior. When the event occurs ("fires"), the subworkflow runs.
Adding an event subworkflow overrides Geocortex Workflow's default behavior for handling events. Having an event subworkflow is your way of telling the workflow that you want to take control of how the event is handled.
Sometimes, you may want to have both custom behavior and the default behavior. In this case, you can add a Propagate Form Event activity to the event subworkflow. The Propagate Form Event activity instructs the workflow to perform the default behavior after the event subworkflow completes.
Different types of form elements support different types of events. For example, radio groups have
change events, whereas button bars have
submit events. Each element in a form has its own events. For example, if a form has two radio groups, each radio group has its own
Geocortex Workflow has the following types of events:
load: When a Display Form activity runs, the form elements load. Every form element has a
load event that tells you when that element has finished loading.
change: When the user makes a selection or enters some input, the
change event fires. The
change event can fire zero or more times, depending on whether the user enters anything for that element.
click: When the user clicks a button, the
click event fires.
cancel: When the user cancels the action, the
cancel event fires.
validate: When the user clicks a button that causes validation, the
validate event fires.
submit: When the user clicks a button that submits the form and all form elements have passed validation, the
submit event fires.
For more information about a particular event, refer to the documentation for the form element.
Some events can fire multiple times for the same form element, causing the event subworkflow to run multiple times. For this reason, we recommend that you make sure that event subworkflows are not computationally intensive or long running.
Submit a Form
Validate the User's Input