GUI: Element Property Actions
Description
GUI:Element Property Actions step allows user to check element property values (based on the Element Property chosen).
Prerequisites: If you want to use the Java technology in the step, ensure you have Java 1.8 32-bit installed on your system. For details on installing Java 1.8 and setting up access bridge, see Appendix: Java access bridge installation
Limitation: The step will not work for Java and Windows technologies on Linux. For Java technology:
- The scaling factor of the machine must be 100% only.
- Resolution and scaling of workflow recorder machine and workflow runner step must be same.
- This release does not support minimizing frames or maximizing internal frames. Designer can use GUI: Universal Actions step for robot handling
- Max Timeout in step configuration is only applicable for Java and Windows technology.
- Recorder is not supported for java/applet.
Known issues: For Java technology:
- When the Access Bridge is configured to run the GUI Java automation steps, then SAHI automation will not work.
- A few positive and reverse conditions are not working correctly.
| No. | Field Name | Description |
|---|---|---|
| 1 | Step Name | Name of the step. The name must be unique in a single workflow. The data type is string and the field is mandatory. |
| 2 | Technology | Select the technology used by the target application: Java or Windows. The data type is string and the field is mandatory. |
| 3 | Action Information | Click to open the Action information dialog. Select the field details, as required. Click OK, and the selected Action Information details appear in the tabular format. Note: The fields will change depending on the selected technology. For details, see the respective sections in the table. |
| For Windows/Java Technology | Provide the following field details in the Action Information dialog | |
| I. | Action Type | Select the action type from the list. - Get Property Value - Wait Until (some condition (element property value) is satisfied). The data type is string, and the field is mandatory. |
| II. | Window Path | Window Path is the relative\absolute path of the Windows application on which element exists. It is captured by GUI Spy in the Generate Step dialog. It is then populated in the step configuration upon Step Generation. You may also enter or modify Windows path manually on the Step Generation window or step configuration. Windows path may be provided as a String or regex. Sample of Windows Path as string: w[Desktop]/w[Application Name], w[Desktop]/w[/Application N/], w[Desktop]/w[/Application .*/]. If you are providing partial application name then put it as a regex between / and /. Also, if the Application name changes dynamically, it is a good idea to provide it as a regex. Java: Provide the Window Name on which automation actions should be performed. For example, Windows Name: AutomationEdge Applet App Users can also utilize a regex pattern to match the window name, instead of specifying the exact window name of Java Application. For example: Suppose the Java application window title is, “Oracle Apps 2024-11-26“, a user can provide: - Oracle Apps \d4-\d2-\d2 - ^Oracle - Any other valid regex |
| III | Element Index(Starts with 0) | For Multiple elements with same criteria, specify index of the element you want to locate. Provide index 0 if you want first element from the located elements, increment index by 1 for the next elements. |
| IV | Criteria | Criteria is the criterion to locate element on Windows \Java application. It is captured by Windows Spy in the Generate Step dialog Upon step generation it is populated in the step configuration. You may change criteria by choosing from the list in the Step Generation window or step configuration. The data type is string, and the field is mandatory. |
| V | Criteria Value | Specify relevant criteria value for the criteria provided above. |
| VI | Element Property | Select any of the following element property: - Is Exist : for all elements - Is Checked : for checkbox - Is Visible : for all elements - Is Enabled : for all elements - Is Selected : for all elements but specifically designed for radio button - Application Exist Note (Windows Technology) - Is Checked Element Property is not supported for radio button elements. - With element property : Is Exist or Is Visible avoid Absolute XPath criterion. In a workflow it is recommended to first check if element exists (Wait Until – Is Exist) followed by Get Property Values steps. |
| VII | Checkbox: Reverse above Element Property Condition | Enable the checkbox to reverse the Element Property chosen above. |
| Dynamic fields: | ||
| VIII | Output Field | Specify an output field name to hold the output of step execution (The output is True/False). Note- The field is visible if the selected Action Type is Get Property Value. |
| 4 | Max Timeout (In Second) | Specify the timeout value for the action to be performed. |
| 5 | Step Description | Describe the intended action for better step-row clarity. |
Common Buttons:
| No. | Field Name | Description |
|---|---|---|
| 1. | Button: Edit Element | Click to start spying and change step details as desired. Opening spy from step is restricted to the scope of the step. Only relevant elements are detected with active spy. Use Hotkeys (‘Shift’ or ’~’) to detect the element. We may call it as a ‘Step Restricted Spy’ for understanding purposes. e.g. Suppose spy is started from ‘Element Action’ step. Now spy is restricted to elements that support ‘Element Action’. All elements that support ‘Element Action’ will be highlighted in blue color and the rest will be highlighted in ‘Red’ color upon hover. Notice Step dropdown is disabled and value selected is ‘Element Action’. Note: Edit Element is visible for Java Technology or Windows Technology. |