As indicated in Chapter 3, Case Study Introduction AHA has the requirement of tracking all view hits to be able to identify frequently used views and to provide data for business process management. The preconfigured Usage Tracking Service has been identified as the solution for this requirement.
The solution also includes the use of the runtime event architecture that has been introduced in Chapter 16, Menus and Buttons. We will however discuss how runtime events work in more detail in the following section.
As indicated in Chapter 16, we can use runtime events to handle events in Siebel applications. We can understand runtime events as a means to registering distinct events such as a method invocation on a business component or applet with an action set. An action set, as the name suggests, is a set of discrete actions that can be one of the following:
Invoke a business service method and pass input...