There are multiple activities that can be used to automate apps or web-apps and you can find them in the Activities panel, under the UI Automation category.
All of these activities have multiple properties in common:
- ContinueOnError – specifies if the automation should continue, even if the activity throws an error. This field only supports boolean values (True, False). The default value in this field is False. As a result, if this field is blank and an error is thrown, the execution of the project stops. If the value is set to True, the execution of the project continues regardless of any error.
If the ContinueOnError field of an activity inside a Try Catch is set to True, no error is caught when the project is executed.
- DelayAfter – adds a pause after the activity, in milliseconds.
- DelayBefore – adds a pause before the activity, in milliseconds.
- TimeoutMS – specifies the amount of time (in milliseconds) to wait for a specified element to be found before an error is thrown. The default value is 30000 milliseconds (30 seconds).
- WaitForReady – wait for the target to become ready, before performing the activity. There are three available options:
- None – does not wait for the target to be ready.
- Interactive – waits until only a part of the app is loaded.
- Complete – waits for the entire app to be loaded.
- Target – identifies the UI element the activity works with.
The target is composed of multiple pieces, namely the container, selector and clipping region, to ensure that you correctly identify a UI element.
A container gives you a little more context for the button or field you want to use, so that you can tell windows apart or different areas of the same app. They are automatically generated, but you can make changes to them in the Properties panel.
The following are containers: