Use Case

Estimated reading: 3 minutes

Scenario

In a basic automation task, website elements change dynamically. The manager wants to record actions for troubleshooting as the robot logs into the website and checks for specific elements. However, the process fails during the element check.

To address this, we use the ‘Screen Recorder’ activity. We place the necessary actions inside it for recording. The recorded data is stored in a specified filepath, allowing organized recording and troubleshooting, with data retained every 10 days.

Steps to execute the bot

1. Create a new solution or workflow as “Recorder”.
2. Install the latest version of “Screen Recorder” activity from the “Manage Feature”.
3. Drag and drop the “ScreenRecorder” activity and set it as start node.
4. Double click on the activity.
a. It helps the user to record the activities in real time during the execution of the bot.
5. Navigating to the “FramePersecond” in the properties to provide the frame rate.
a. Here I am providing the value “3”.
6. Moving to the “OutputfilePath” to provide the filepath to store the output of the recorded data.
a. Here, the user has stored the value in variable as “FilePath”.
7. Now, we are adding the “OpenWebBrowser” from the WebAutomation feature into the scope.
a. It helps to launch the specified URL on the specified browser.
b. Here I am using the URL as https://www.sutherlandglobal.com.
c. You can provide the specified URL to proceed.
8. Next, placing the “Click” activity from the WebAutomation feature to select the login username and password. (You can detect the specified element from your webpage to select).
a. Double click on the activity.
b. Here, choose the “Select Active Application” option.
c. Double-click on the activity and choose the element where you want to perform the click, then proceed to the next step. In this case, I am spying over the “Contact” us button.
d. Once you have chosen the “Element,” the attributes will be stored in the “Spy” window, along with an “image” of the element.
e. If you wish to add or remove any attributes, you can edit the “Attributes Editor.” In this case, we are not making any changes in the “Editor.
f. Once you click on the “Save” button, the elements will be stored in the activity window.

9. Now, adding the “ElementExist” activity from the WebAutomation feature to check the element.
a. Double click on the activity.
b. Here, choose the “Select Active Application” option.
c. Double-click on the activity and choose the element where you want to perform the click, then proceed to the next step. In this case, I am spying over the “Contact” us button.
d. Once you have chosen the “Element,” the attributes will be stored in the “Spy” window, along with an “image” of the element.
e. If you wish to add or remove any attributes, you can edit the “Attributes Editor.” In this case, we are not making any changes in the “Editor.”
f. Once you click on the “Save” button, the elements will be stored in the activity window
g. Now, navigating to the “ExistStatus” in the properties to declare a variable to view the output.
10. Then place the “Writelog” activity from the Notification feature.
a. Double click on the activity.
b. Enter the input string as “Result.ToString” here. The “.ToString” is advised to use along with any other data types other than string format. It converts any data type into string.
c. Choose the log level as “Info”.

11. Now, execute the workflow.

You can view the output of the activity in the specified filepath.

Use Case

Scenario

Steps to execute the bot

Use Case

CONTENTS