Specifications

Event Specifications
Within the transaction definition, you can create more complicated constructs
using the choice, sequence, and last statements. (You cannot use choice,
sequence, or last within the event specifications for the except and failure
statements.)
Application Response looks for the specified event sequence interspersed
among all of the events occurring within the application. When searching an
application’s event sequence for a specified transaction, Application Response
examines only those events that occur from defined resources of the
application. As such, each transaction rule should only reference events from
the application’s defined resources. (Event types listed in transaction
definitions must match resource types listed in the application’s resource
definitions.)
except
Optional. Use the except statement to specify one or more events that indicate
that the transaction should not be monitored.
failure1 - failure5
Optional. Use the failure statement to define failure cases for the transaction.
Example
The following transaction definition applies to a PeopleSoft application for
updating employee data. The rule body consists of a simple sequence of
events. When Application Response observes that these five events have
occurred in the specified order for the specified application, it recognizes the
transaction and measures its response time.
transaction "Update"
module "Update"
{
event "Event1" Windows SetFocus { Title="Correction – Personal Data" }
event "Event2" Windows ButtonPress { Text="OK" }
event "Event3" Windows SetFocus
{ Title="Administer Workforce (U.S.) – Use – Personal Data" }
event "Event4" Windows MenuCommand { Text="File->Save" }
event "Event5" Windows StatusMessage { Text="Record Saved" }
}
Event Specifications
In the BT language, each event specification describes a single application
event. Event specifications are a core component of the transaction definition,
122 BTStudio Administration Guide