Specifications

Example: Develop a Text-Based Transaction Rule
#
Event "Type_underscore" Windows KeyPress { Key=95 }
#
Note: For a list of decimal ASCII codes for printing and non-printing
characters, refer to www.asciitable.com.
The final part of the transaction definition recognizes when users click OK on
the login window, and the login window is destroyed.
#
# User clicks the OK button on the Login window
#
Event "ClickOK" Windows MouseClick { Title="OK" }
#
# Login window is destroyed
#
Event "DestroyLoginWindow" Windows Destroy { Title="Login Status" }
}
So the entire transaction definition for CS_Login is as follows:
transaction "CS_Login"
module "CS_Login"
{
# Remedy (aruser) starts and creates the login window
#
Event "StartAruserProcess" Process Start { ExecutableName="aruser" }
Event "StartAruserWindow" Windows Start { ExecutableName="aruser" }
Event "CreateLoginWindow" Windows Create { Title="Login" }
Event "SetTitleLogin" Windows SetTitle { Title="Login - Remedy User" }
#
# All customer service login names begin with CS_
# so check for the user typing CS_
# after the login window is created
#
# For login name, type uppercase C or lowercase c
#
Choice
{
Event "Type_C" Windows KeyPress { Key=67 } # uppercase C
Event "Type_c" Windows KeyPress { Key=99 } # lowercase c
}
# For login name, type uppercase S or lowercase s
#
Choice
{
Monitor Transactions Based on Keystrokes 99