Specifications

Failure Statement
transaction "Login"
module "Login"
{
event "Begin" Windows SetTitle {Title="Login"}
event "Success" Windows SetTitle {Title="Login Succeeded"}
}
failure1 "FailedLogin"
{
event "Begin" Windows SetTitle {Title="Login"}
event "Failed" Windows SetTitle {Title=contains:"Login Failed"}
}
Example 2: To expand on Example 1, the following Login transaction
definition includes four failure statements, which help to identify reasons for
the login failure: invalid password, invalid server, server not available, or
cancelled login. This level of detail is available in the ATV. Notice that each
failure case begins with the same Begin event that starts the transaction.
transaction "Login"
module "Login"
{
event "Begin" Windows SetTitle {Title="Login"}
event "Success" Windows SetTitle {Title="Login Succeeded"}
}
failure1 "InvalidPassword"
{
event "Begin" Windows SetTitle {Title="Login"}
event "Failed1" Windows SetTitle {Title="Login Failed - Invalid Password"}
}
failure2 "InvalidServer"
{
event "Begin" Windows SetTitle {Title="Login"}
event "Failed2" Windows SetTitle {Title="Login Failed - Invalid Server"}
}
failure3 "ServerNotAvailable"
{
event "Begin" Windows SetTitle {Title="Login"}
event "Failed3" Windows SetTitle {Title="Login Failed - Server Not Available"}
}
failure4 "CancelLogin"
{
event "Begin" Windows SetTitle {Title="Login"}
event "FailedLogin" Windows SetTitle {Title="Warning"}
event "Cancel" Windows ButtonPress {Text="Cancel"}
}
174 BTStudio Administration Guide