Controls and Images Repository

Store all the elements that your Automation will interact with in a central reusable repository

WinAutomation can interact with any application on your machine. This interaction takes place through Controls, which are elements of any desktop or web application that your Processes will access through dedicated actions. A control can be a button, a link that you wish to hit, a text filed that needs filling in etc., associated with the appropriate WinAutomation step. For all the different applications that your Automation is accessing while executing, you are able to save the Controls that you have chosen to interact with, based on your automation flow.

In this aspect, the Controls and Images Repository is where you are Modeling the applications used in your Processes and you may store the different Controls into a central repository. Finally, you are accessing the application controls that you have saved, through your automation, while it is running.

Editable Controls

Controls are UI or Web elements that can be captured and fully managed by the user. In order to access an application element, you may try one, two, three or …unlimited different selectors to do so. Controls can be renamed, edited, changed, updated or deleted. All the UI or CSS selectors behind each control are editable, supporting variables for custom control accessing in case of complicated scripts with multiple repetitions. Same applies to any image that the Process will try to find on the machine’s screen.

Risk Control

Desktop or web application, are more than often updated, in order to provide new features and fancier interface. Therefore, and their UI may constantly change.

What would happen to your Process if it’s Controls were no longer valid due to application updates? Obviously you would have to model the application again and grab the new Controls or Images. Otherwise, the Automation would simply fail to access them and error out. The advantage of the Central Repository for Controls and Images, apart from keeping the Process neat and easy to modify, is apparent here! Regardless of any application interface change, you will not have to change a single line of your process, but ONLY update the central Controls. Your Automation will be up and running again in no time and with minimum effort!

Risk Control

Desktop or web application, are more than often updated, in order to provide new features and fancier interface. Therefore, and their UI may constantly change.

What would happen to your Process if it’s Controls were no longer valid due to application updates? Obviously you would have to model the application again and grab the new Controls or Images. Else, the Automation would simply fail to access them and error out. The advantage of the Central Repository for Controls and Images, apart from keeping the Process neat and easy to modify, is apparent here! Regardless of any application interface change, you will not have to change a single line of your process, but ONLY update the central Controls. Your Automation will be up and running again in no time and with minimum effort!