Introduction

Flowster UI Recorder

Flowster UI Recorder activities are simulating a graphical user interface (GUI) automation tool in order to automate anything that can be seen on the screen using the image recognition method to identify GUI elements. Flowster UI Recorder activities allow users to automate GUI interaction by using screenshots. Flowster UI Recorder is very useful in testing applications or web pages when you don’t know the ID/name of the elements. Flowster UI Recorder will check the appearance of the image and if match found, it will interact with the image accordingly, without the need to know the object ID or name, like other automation tools require. It can also be used for automating repetitive tasks like daily usage of applications.

RDC

Automate with Flowster UI Recorder

In order to automate scenarios using a specific user session ID, Remote Desktop Connection (RDC) activities must be used in integration with Flowster UI Recorder to provide an active session ID for the desired user. For detailed information about RDC, Flowster UI Recorder activities and server prerequisites please check links  RDC and UIRecorder.

Automation Scenario -  Open Chrome Browser

This workflow will open Chrome browser using double-click action using a specific user session ID.

Automation Implementation

Open User Session

• The user session is opened by Connect To Remote Desktop (ConnectToRDC) activity. The 'Connection' output will be used to disconnect the user from the remote server and the 'Output Session ID' parameter is passed on to the 'ConnectToUIRecorder' activity. When using RDC activities in integration with Flowster UI Recorder, the ‘Is Local machine’ parameter must be set always to True, because the workflow will be executed either on the local Execution Agent or an additional Execution Agent installed on a server where the Flowster UI Recorder activities will be used. In both cases, the remote server will become Local machine in terms of execution.

Open Chrome Browser

• Connect To UIRecorder - The action (e.g. double-click action) process is started using the session ID provided in the ‘Session ID’ parameter. The other parameters are needed because the workflow is executed via an execution agent. For more information about how to set the Flowster Rest API client app, click here.

• DoubleClick - The pattern was selected from the remote desktop server by opening a remote desktop connection using Remote Desktop Connection application.

• Disconnect From UIRecorder  - This activity will end the specified UI Recorder session.

Close User Session

• Disconnect From Remote Desktop - This activity provides two options: to reset the user session by selecting Disconnect option, or to logoff user from the server using Sign Out option. Because the server is a local machine. the Connection object will be used to disconnect the user from the server.