Help files

Web Automation Overview

With WinAutomation you are able to automate your web related tasks in an intuitive manner with unprecedented speed and reliability. The Process Designer includes a number of actions under the "Web Automation" category, each of them corresponding to an action that a user would manually perform within a web browser.

For Web Automation Process WinAutomation support four Browsers:

  • googlechromeicon.png   Google Chrome

  • firefoxicon.png   Mozilla Firefox

  • internetexplorericon.png  Internet Explorer

  • edgeIcon.png  Microsoft Edge

  • The WinAutomation Automation Browser

In the current Web Automation Topic we will focus on the Internet Explorer browser to demonstrate the Web functionality, but, do keep in mind that everything explained here, is 100% applicable to the other browsers also!

The usual sequence for creating a Web Automation Process is the following:

  • You launch a browser window (or attach to an existing one) using one of the following three actions: "Launch New Internet Explorer", "Launch New Chrome","Launch New Firefox" or "Launch New Edge". These actions generate a variable containing the instance of the web browser that needs to be passed to subsequent actions (this is useful when you need to automate more that one browsers concurrently). By default a Web Browser instance is stored in %Browser%, but you can change the name of the variable to the most convenient name for you. Do keep in mind that any web actions on this specific browser that you opened with these actions, should respond to this instance.For example if you wish to use the "Click Link on Web Page" action, in the Web Browser Instance you should indicate the variable %Browser% (or the variable's name that you gave to the instance in any of the Launch new Browser actions).

launchfirefox.png
  • You add the appropriate actions based on the steps that you want to automate. There are actions available for clicking on links, filling and submitting web forms, extracting data from web pages, etc. In each action you will need to pass the variable containing the web browser instance (for example %Browser%) to specify the browser on which the action will be performed, as previously mentioned in [1].

  • Optionally, you may close the browser used for the automation using the "Close Web Browser" action.

In order to build your Process you have plenty of tools at your disposal. The easiest way to start is to use the Web Recorder that gives you the ability to record your web activities as you perform them and convert them into a Process.

Alternatively, you can build your Process manually by combining (and configuring) the appropriate actions in Process Designer. The rest of the overview will focus on the Process Designer approach, for Web Recorder usage please refer to the corresponding topic.