- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Variables
- Arguments
- Imported Namespaces
- Trigger-based Attended Automation
- Recording
- About Recording
- Recording Types
- Automatic Recording
- Example of Automatic Recording With Basic and Desktop
- Example of Automatic Recording With Web
- Manual Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Citrix Technologies Automation
- RDP Automation
- Salesforce Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- Test Suite - Studio
- Extensions
- Troubleshooting
- About troubleshooting
- Microsoft App-V support and limitations
- Internet Explorer X64 troubleshooting
- Microsoft Office issues
- Identifying UI elements in PDF with Accessibility options
- Repairing Active Accessibility support
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
Example of Automatic Recording With Basic and Desktop
To exemplify how you can use the automatic recording and understand more about the differences between Basic and Desktop, let’s create the same project for the two.
The two screenshots below display part of the resulted projects for the Basic (first screenshot) and Desktop (second screenshot) automatic recordings. As you can see, the second one generates an Attach Window container, while the Basic one does not.
Desktop recorder - The top level window selector from the Attach Window container:
Desktop recorder - The partial selector for the Type Into activity:
Basic recorder – The full selector for the Type Into activity:
You can also customize and parameterize this project after it is recorded. To exemplify this, let’s take the Desktop recording example and build upon it.
For example, let’s assume that we want to extract the number of an invoice from an Excel file, copy it to a new Notepad application which we close in the end.
- Add an Excel Application Scope activity before the recording sequence.
- In the WorkbookPath field, type the path of the Excel file you need to extract information from.
- Add a Read Cell activity in the Excel Application Scope.
- In the Properties panel, add the Sheet Name and Cell information from the Excel file used.
- Right-click in the Result field, and click Create Variable. The Set Name field is displayed.
- Fill in the name, such as
InvoiceNumber
, and press Enter. The variable of type 'GenericValue' is created and displayed in the Result field and Variables panel. - Change the scope of the variable to Main.
-
In the recording sequence, in the Type Into activity, in the Text field, add the
InvoiceNumber
variable. This copies the value stored in the variable to Notepad.What was added to the project should look as in the following screenshot.
- Add an Open Application activity between Excel Application Scope and the Recording sequence.
- Use Indicate window on screen to select the active Notepad window.
- Place the Recording sequence inside the Open Application activity.
- Add a Close Application activity after Open Application.
- Use Indicate window on screen again to select the active Notepad window to be closed.
-
Make sure the OffsetX and OffsetY properties (Cursor Position) are empty.
What was added to the project should look as in the following screenshot.
-
Press F5. The automation is executed as expected.
Note: To ensure that the workflow execution ends, close the Save Notepad window.