Specifications

Example: Develop a Text-Based Transaction Rule
}
}
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
{
Event "Type_S" Windows KeyPress { Key=83 } # uppercase S
Event "Type_s" Windows KeyPress { Key=115 } # lowercase s
}
# Type an underscore
#
Event "Type_underscore" Windows KeyPress { Key=95 }
#
# 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" }
}
Example: Develop a Text-Based Transaction Rule
To monitor transactions based on keystrokes, you need to define a rule set
whose transaction definitions specify the keystrokes to watch for. For example,
suppose that you want to monitor how long it takes customer support
Monitor Transactions Based on Keystrokes 97