1. Working with Oracle Forms
  2. Integration
  3. Working with Server and System Events
  4. System Events

System Events

Often it is required to have an application be aware of events that occur on the system hosting it and, have an ability to react to these actions.

In most cases, such events are not directly caused by the running Forms application, but knowledge of their occurrence could provide valuable information to it. This is most common on the client tier of an Oracle Forms application. An example of such a system event might be an indication that the end-user has been idle for an extended period of time. Knowledge of such a condition would allow the application developer to react and take appropriate actions. System Events can provide that desired knowledge.

There are five System Events. For all of these Events, little to no administrative configuration is required to use them. To use any of these events the application developer will be required to create the appropriate event object and code the WHEN-EVENT-RAISED trigger to perform the desired action. However, a brief description of each will be provided here. More information can be found in the Form Builder Help.

Note:

Because System Events rely on actions outside of Oracle Forms or the successful completion of an action within the application, they should not be used as the only means for implementing application security. If for any reason the action associated with the System Event does not complete successfully or is undetected by the application, the related application trigger may not fire. Although this is likely to be rare, it should be considered when developing with System Events.