Match Rules for Remedy Controls

Studio uses Windows, web, and virtual match rules to match Remedy Forms and objects. This example shows Object Explorer with some Remedy Form controls interrogated:

Windows match rules are used to match the Remedy User application window (BMC_Remedy_User_Home_Pa in the example), MDI Client, Form Window (AA_JBS_TestForm_New) and generic control.

For the Form object (Form1), these match rules are used:

Windows Text match rule - Matches based on the text associated with the Form, such as FormView.
Virtual Native Window Name match rule - Matches based on the native control name for the form window, such as RemedyForm.

The Virtual Native Window Name match rule has these properties:

Property	Description
Virtual Window Name	The expected native control name for the window, such as RemedyForm.
Culture IgnoreCase Mode Text	Go to the Virtual Window Name property to open the Match Rule Editor and modify these properties, when necessary, to specify how the Name text is matched. For more information, see Match Rule Editor.

For the Form virtual controls (owner-drawn), the Native Control Name match rule is used. This match rule has these properties:

Property	Description
NativeControlName	The expected native control name for the window, such as the Check Box Field.
Culture IgnoreCase Mode Text	Browse the NativeControlName property to open the Match Rule Editor and modify these properties, when necessary, to specify how the Name text is matched. For more information, see Match Rule Editor.

For web controls on Remedy Forms, web application match rules are used, such as: Element Inner Text and Anchor URL (for a link). For more information, see Match Rule Definitions.