studio
2022.10
false
- 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
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- ST-USG-005 - Hardcoded Activity Arguments
- ST-USG-009 - Unused Variables
- ST-USG-010 - Unused Dependencies
- ST-USG-014 - Package Restrictions
- ST-USG-020 - Minimum Log Messages
- ST-USG-024 - Unused Saved for Later
- ST-USG-025 - Saved Value Misuse
- ST-USG-026 - Activity Restrictions
- ST-USG-027 - Required Packages
- ST-USG-028 - Restrict Invoke File Templates
- ST-USG-032 - Required Tags
- ST-USG-034 - Automation Hub URL
- Variables
- Arguments
- Imported Namespaces
- 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
- Studio testing
- 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

Studio User Guide
Last updated Sep 3, 2025
Example of Using an If Activity
linkTo exemplify how you can use the If activity, let’s create an automation that asks the user for two numbers, checks to see if one is divisible by the other, and depending on the result, displays a different message in the Output panel.
- Create a new sequence.
- Create two integer variables,
FirstNumber
andSecondNumber
for example. - Add two Input Dialog activities to the Designer panel.
- Type titles and labels for both activities and, in the Value entered fields, add the
FirstNumber
andSecondNumber
variables. - Add an If activity to the Designer panel, under the previously added Input Dialog ones.
- In the Condition section, type
FirstNumber
modSecondNumber
= 0. This expression checks if the first number is divisible to the second one, using the mod operator. - In the Then section, add a Write Line activity.
- On the right side of the Text field, select Plus
> Open in Advanced Editor.
- Inside the Expression Editor window, type
FirstNumber.ToString
+ " is divisible by "+SecondNumber.ToString
+ ".". This is the message that is displayed if the first number is divisible by the second one. - Click Show Else to display the Else section, and then add another Write Line activity in the Else section.
- Inside the Expression Editor window, type
FirstNumber.ToString
+ " is NOT divisible by "+SecondNumber.ToString
+ ".". This is the message that is displayed if the first number is not divisible with the second one. - Press F5. The automation is executed.
- Add numbers when prompted. Note that the Output panel displays the result, depending on the values added in the Input Dialog windows.