About the Application Event System Design Forms
The system includes a set of specialized forms created to enable you to create and use your own custom application events. With the exception of the Access As form and the System Configuration Parameters form in this table, these forms are located in the Explorer under . The Access As and System Configuration Parameters forms are located at .
Access to these forms is controlled by the System Administration authorization group.
This table lists and briefly describes the use of the application event system design forms:
| Form name | Description |
|---|---|
| Access As |
Although not directly used in the creation and customization of application events and handlers, this form displays the current Access As setting. The Access As value is an indicator of which application event system elements you are authorized to modify and delete. |
| Events |
This form is used to name application events. Once named here, application events are available on other forms as well, particularly the Event Triggers and Event Handlers forms. |
| Event Triggers |
This form is used to define event triggers, which set conditions that cause a named application event to fire. |
| Event Handlers |
This form is used to display and define event handlers, which determine the work to be done when an application event fires. |
| Event Handler Diagram |
This form is used to present a graphical representation of an event handler flow. You can also use this form to access the Event Actions form for selected event actions to view or modify them. Finally, you can also add event actions to an event handler flow by using this form. |
| Event Handler Sequence |
This form is used to change the order of any handlers that have the current Access As identifier as indicated on the Access As form. |
| Event Actions |
This form is used to display and define the actions to be performed by a particular event handler during its execution. These are the individual tasks accomplished by the event handlers. |
| Event action parameter forms |
These forms are used to define the event action parameters for each action type. |
| Event Variable Groups |
This form is used to display and define initial states, which are sets of event variables and the initial values they are to pass to the event handler when it starts to run. |
| Event Global Constants |
This form is used to display and define event global constants, which are static values that can be accessed and used by expressions during the running of an event handler. |
| System Configuration Parameters |
This form is used to define certain parameters that affect the system configuration. Although not directly used in the creation and customization of application events and handlers, you can use this form to control some aspects of how application events and handlers behave on the system. These aspects are concerned mostly with retest and reset intervals that globally govern when and how often various conditions can be retested or events can retry. |
| Workflow Event Handler Activation |
This form is used to activate predefined event handlers that represent
common workflows. You must specify some information, such as users
or email addresses that are notified when an application event
occurs. You can also copy and modify these event handlers.
Note: This form is not available with all Mongoose-based applications,
including Mongoose as a
stand-alone application.
See the online help in your application for this form. |
This diagram shows the functional relationship between the design forms and elements for the application event system:
