GUI: Get Element Attributes
Description
GUI: Get Elements Attributes step allows user to get or retrieve element attributes value(s), such as bgcolor, font-name, and others at runtime.
Prerequisites:
- If you want to use Java technology in this 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.
- If you want to use Web technology in this step, ensure valid extensions are added to corresponding web browser.
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 both, Java and Windows technologies: For Java technology: When the access bridge is configured to run the GUI Java automation steps, then SAHI automation will not work.
Configurations
| 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, Web or Windows. Note: The fields will change depending on the selected technology The data type is string, and the field is mandatory. |
| For Windows/Java Technology | Provide the following field details | |
| I | 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 |
| II | 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. Default Value:0 |
| III | 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 Step Generation window or step configuration. It is Mandatory Field. |
| IV | Criteria Value | Specify relevant criteria value for the criteria provided above. |
| For Web Technology | provide the following field details | |
| I. | Web Browser Name | Select any one Web Browser Name from the given list. Note: Select the same Web Browser Name, which was selected in Start Browser Step. |
| II. | Element Index(Starts with 0) | Specify the index of the element you want to locate. Note: One can also specify First or Last. First, if you want the first element from the located element or specify Last if you want the last element. Default Value: 0. |
| III. | Checkbox: Active Element | Select the checkbox to capture the current active element. |
| IV. | Criteria | ‘Criteria’ is the criterion to locate elements on Web GUI. GUI Spy can capture it 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. Note: For list and description of criteria, See Criteria Table. It is a mandatory field. |
| V. | Criteria Value | Specify relevant criteria value for the criteria provided above.It is a mandatory field. |
| VI. | Iframe Indices | Specify Iframe Indices value. Specifying iframe indices ensures that the target element is identified correctly within the nested frame structure. You can provide comma-separated values.For e.g. 0,1,2 |
| VII. | Iframe Xpath | Iframe Xpath is a uniquely generated path that represents the location of an <iframe> or <frame> relative to the top-level window. Iframe Xpath identifies each frame using a unique attribute such as id, name, or title if available, for example, iframe[@id='mainFrame']. If no such attributes exist, the frame is identified by its position among sibling frames, like iframe[2] for the second iframe. For nested structures, each frame is joined in sequence to form a full path. For example, if an element is inside an iframe[@id='outer'], which contains a frameset with a frame[@name='middle'], and that frame contains iframe[@title='inner'], the generated path would be: iframe[@id='outer'];frame[@name='middle'];iframe[@title='inner']. Note: If an iframe or frame has no id, name, or title, its origin (i.e., the src URL) will be used as a fallback in the path for unique identification. For example: iframe[@origin='https://example.com']. |
| VIII. | Frame ID | Provide the current Iframe Id to target a specific iframe to perform the action. Default Value: frameID |
| Attributes/property table | ||
| 3 | Type | Select the attribute from the list: - Element Attribute. -CSS Property Note: The CSS property will always get with computed styles and not exactly what you see in browser.Note: For Java/Windows technology, only Element Attribute is available.It is a mandatory field. |
| 4 | Name | For Java/Window Technology: Select the attribute name of the detected control from list.For Web Technology: Specify the name of the CSS Property or Element attribute based on the Type.It is a mandatory field. |
| 5 | Output Field Name | Specify the Name to hold the result on successful execution. Default Value: OutputFieldName It is a mandatory field. Note: User can provide multiple properties or attributes. |
| Common Buttons: | ||
| 1 | Button: Edit Element | Click to start spying. Opening spy from step is restricted to the step, that is, only relevant elements are detected from active spy. Use Hotkeys (‘Shift’ or ’~’) to detect the element. We may call it as a ‘Step Restricted Spy’ for understanding purposes. For example, suppose spy is started from ‘Get Table Data’ step. Now spy is restricted to elements of type ‘Table’ only. All element of type ‘Table’ will be highlighted in blue color. If we try to detect element other than of type ‘Table’ it will be highlighted in ‘Red’ color upon hover. Step dropdown is disabled and value selected is ‘Get Table Data’.Note: Option is visible for Java Technology or Windows Technology. |