Specifications

Failure Codes
Example 3: The following transaction definition demonstrates the use of a
choice statement within a failure statement to define multiple paths for a
failure case. It also demonstrates use of the Web FailedLoad event action.
transaction "WebLogin"
module "WebLogin"
{
event "Begin" Windows SetTitle {Title="Login"}
event "Success" Windows SetTitle {Title="Login Succeeded"}
}
failure1 "CancelLogin"
{
event "Begin" Windows SetTitle {Title="Login"}
choice
{
event "404-NotFound" Web FailedLoad {FailureCode=404}
event "Stop" Windows ButtonPress {Text="Stop"}
}
}
Failure Codes
The FailureCode parameter for the Web FailedLoad event action supports the
following failure codes.
Note: Some versions of Internet Explorer do not properly report 404 failures
or other types of browser failures.
Failure Code Code Message
400 HTTP_STATUS_BAD_REQUEST
401 HTTP_STATUS_DENIED
402 HTTP_STATUS_PAYMENT_REQ
403 HTTP_STATUS_FORBIDDEN
404 HTTP_STATUS_NOT_FOUND
405 HTTP_STATUS_BAD_METHOD
406 HTTP_STATUS_NONE_ACCEPTABLE
407 HTTP_STATUS_PROXY_AUTH_REQ
408 HTTP_STATUS_REQUEST_TIMEOUT
409 HTTP_STATUS_CONFLICT
BT Language Reference 175