GUI: Web Wait Until
Description
Web Wait Until pauses workflow execution until a specified condition is met on a web page element, or until the timeout expires. Use this step to synchronize your workflow with the web page state — for example, waiting for a button to become clickable, a spinner to disappear, a specific text to appear in an element, or an alert to be present. It supports conditions such as Element Visible, Element Invisible, Element Present, Element to be Clickable, Text to be Present in Element, Element Checked, Alert Present, and Element Selected. Place this step before any action that depends on the target element being in the expected state.
Limitation The Step GUI: Web Wait Until will not work, if the browser is Mozilla Firefox and Expected condition is set to Alert Present.
Configurations
| Field Name | Description |
|---|---|
| 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. |
| 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. |
| Expected Condition | Specify the condition for the element from given list. -Element visible -Element invisible -Element present -Element to be clickable -Text to be present in element -Text to be present in element value -Element checked - Alert Present -Element Selected |
| Timeout (in Milliseconds) | Maximum time in milliseconds to wait for the expected condition.Default Value: 0 |
| 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. For list and description see Criteria Table. |
| Criteria Value | Relevant criteria value has to be specified. |
| 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. Note: Field is not available for the following selected Expected Condition field: - Text to be present in element - Text to be present in element value |
| 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']. |
| Frame ID | Provide the current Iframe Id to target a specific iframe to perform the action. Default Value: frameID |
| Additional value | Select an additional value that is required to complete the action depending on the selected criteria. Note: This field is available when the following criteria is selected in the Expected Condition field: - Text to be present in element - Text to be present in element value Note: Similarly, in GUI Spy, the Additional value field is available when you select the specific options in the Expected Condition field. |
Similarly, in GUI Spy, the Additional value field is available when you select the specific options in the Expected Condition field.