Specifications

Syntax for Resource Definitions
event "EndDownload" Web EndLoad { Level="top" }
}
When you define an application whose rule set contains this transaction
definition, you can use the Application Properties page of the eHealth Web
interface to specify one or more URLs to monitor. If you supply the values
www.concord.com and www.irs.treas.gov, Application Response expands the
transaction definition in the following way. (The choice statement is necessary
so that Application Response recognizes the BrowseAnywhere transaction if
any one of the URLs listed is accessed for a Web BeginLoad event.)
transaction "WebActivity"
module "WebActivity"
{
# Begin page download.
choice
{
event "BeginDownload" Web BeginLoad
{ Level="top" URL=contains:$(URLs) }
event "BeginDownload" Web BeginLoad
{ Level="top" URL=contains:"www.concord.com" }
event "BeginDownload" Web BeginLoad
{ Level="top" URL=contains:"www.irs.ustreas.gov" }
}
# End page download.
event "EndDownload" Web EndLoad { Level="top" }
}
Case Insensitivity
BT Studio and Application Response make text comparisons regardless of
whether the letters are uppercase or lowercase. For example, the following
event specifications are equivalent.
event "Event1" Windows StatusMessage { Text="Change Purchase Order" }
event "Event1" Windows StatusMessage { Text="change purchase order" }
Comments
When writing rule sets, include comments to document the purpose of each
section. You can include comments within resource and transaction definitions
by preceding comments with a pound sign (#). On each line, Application
Response and BT Studio ignore any text that follows a pound sign. When
editing rules in the BT Studio rules pane, you can use the Comment Out
command to indicate that one or more selected lines are comments. This
BT Language Reference 119