Specifications

Sequence Statement
# Match any status message that begins with an identification number
event "Event5" Windows StatusMessage { Text=regexp:"ID[0-9]+" }
Sequence Statement
Sometimes a transaction is valid only if a number of steps occur in a specific
order. The sequence statement allows you to specify an ordered series of
events for a transaction. Application Response considers a sequence statement
to be satisfied if it observes all of the event specifications to occur in order
within the application (although other events may be interspersed).
Syntax
sequence
{
event-specification
event-specification
event-specification
.
.
.
}
event-specification
A sequence statement is matched if all of the specified event specifications are
observed to occur in order within the application (although other events may
be interspersed). Each event specification can itself be a single event
specification, choice statement, last statement, or sequence statement.
Application Response always interprets the main rule body of a transaction
definition as an implicit sequence statement.
Example
In the example below, an application user can create a new employee record
by either manually entering the employee’s data into a screen, or importing it
from a file.
transaction "AddNewEmployee"
module "AddNewEmployee"
{
choice
{
BT Language Reference 165