This activity adds an event handler to a Form Element at runtime. This is especially useful when you add the Form Element via the Add Form Element activity since there is no way to configure events for such Form Elements in the Designer. However, you can also use this activity for Form Elements that you add in the Designer.
This activity replaces any existing event handler for the specified event on the specified Form Element.
You could use an Add Form Element activity to add a new Text Box element to a form at runtime and then use Set Form Element Event to add an event handler to handle its "validate" event.
You must also add a Container or Try Catch activity which contains the subworkflow to be executed when the event takes place.
Display Form Id |
Optional Type: String The ID of the Display Form activity that contains the element to add the event to. If not specified, the form that contains the element that triggered the subworkflow is used. You can use the "activities" object in an expression to specify the ID of an activity, such as "=activities.form1". This can help avoid typos, and warns you if it is wrong. |
Element Name |
Optional Type: String The ID of the form element to apply the event to. If not specified, the form element that triggered the subworkflow is used. If no element is found, the activity will fail with an error. |
Event Name |
Required Type: String The name of the event to add to the Element. |
Target Activity Id |
Required Type: String The ID of the activity to use as the event handler. This can be a Container or Try Catch. You can use the "activities" object in an expression to specify the ID of an activity, such as "=activities.tryCatch1". This can help avoid typos, and warns you if it is wrong. |
This activity has no outputs.
For information about the ID, Display Name, and Description properties, see Properties Common to all Activities.
This activity works when the device has intermittent connectivity to the network.
Supported from: Geocortex Viewer for HTML5 2.9, ArcGIS Web AppBuilder 2.4.
See also...