GUI: Get Value
Description
GUI: Get Values step allow the user to read the value from element.
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.
Limitations:
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. For Windows Technology:
- On detecting the element using Edit Element button if the detected element is other than text box then it shows the Mouse Actions on Step from Dialog.
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.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 Windows/Java Technology: | Provide the following field details in the Action Information dialog. | |
| 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 |
| 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.The data type is string and the field is mandatory. |
| IV | Criteria Value | Specify relevant criteria value for the criteria provided above. |
| V | Action Type | Choose any of the following options: - Value: Get the actual value inside that control. - Name: Get the control name value. - Text: (Visible only for Window technology) |
| VI | Output Field | Specify an output field name to hold the output of step execution. Default Name: Result. |
| For Web Technology | Provide the following field details in the Action Information dialog | |
| 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 | 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. |
| IV | Criteria Value | Specify relevant criteria value for the criteria provided above.It is a mandatory field. |
| V | 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. |
| VI | Output Field | Provide name which hold the result on successful execution. Default Name: Result. |
| 4 | Max Timeout (In Second) | Specify a Timeout value for the action to be performed. |
| 5 | Step Description | Describe the intended action for better step-row clarity. |
| Common Buttons: | ||
| 1 | Edit Source Element/ Edit Destination Element | Click to start spying. Either Edit Source Element or Edit Destination Element button is visible depending on any field chosen on ‘Source element’ or Destination element’ group. Opening spy from step is restricted to the step, i.e. 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. E.g. is restricted to elements that support ‘Mouse Action’. All elements that are supported will be highlighted in blue color and others will be highlighted in ‘Red’ color upon hover. Step dropdown is disabled and value selected is ‘Mouse Action’. Note: Option is visible for Java Technology or Windows Technology. |