The green input connector in the header is used to trigger the block to start executing.
The green output connector in the header triggers when the UI element has been successfully collapsed.
The title of the block (“Get Window Details”) can be changed by double-clicking on it and typing in a new title.
This property contains the title of the open application window
This property contains the process name of the open application window
This property contains the Interaction state of the open application window
This property contains the Visual state of the open application window
Is model returns true if the application window is model dialog else it will return false
Is topmost returns true if the application window is the topmost window else it will return false
Can maximize returns true if the application window is allowed to maximize else it will return false
Can minimize returns true if the application window is allowed to minimize else it will return false
By setting this property, the building block will use a specific application window.
This green output connector triggers if the UI window is not found within the time specified in the timeout field (see below). If no building blocks are attached to this connector and the window is not found, then the case will end in status Fail.
This connector can be used to branch the execution of the flow depending on whether the window is found or not.
The maximum time spent searching for the UI window before giving up and triggering the “Not found” connector (see above).
The default value is 10 seconds.
Note: All cases have a “global timeout” that can be configured in the “Settings” panel. This is unrelated to the timeout of a single building block. However, a running case will automatically be cancelled if it runs for longer than the global timeout.
When checked, the building block will wait for any changes happening on screen within the specified timeout before looking for the specified window.
Updated March 14th 2018.