studio
2021.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
- 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
- Test Suite - Studio
- Extensions
- Troubleshooting

OUT OF SUPPORT
Studio User Guide
Last updated Nov 18, 2024
Example of Using a True or False Variable
linkTo exemplify how you can work with true or false variables, we are going to create an automation that asks the user for his name and gender, and displays the results in another window.
- Create a new process and add a Flowchart.
- Create two string variables,
Name
andGender
. The first is going to be used to store the name of the user, and the second to store the user’s gender. - Create a boolean variable,
Male
. This variable is going to be used to verify if the user is a male. - Add an Input Dialog activity to the Designer panel and connect it to the Start node.
- In the Properties panel, in the Label field type "What is your name?".
- Add a title and, in the Result field, add the
Name
variable. - Add another Input Dialog activity and connect it to the previous one.
- In the Properties panel, in the Label field, type "What is your gender?".
- Add a title and, in the Result field, add the
Gender
variable. - Add a Flow Decision activity to the Designer panel, and connect it to the second Input Dialog.
- In the Properties panel, in the Condition field, type
Gender
= "Male" orGender
= "male". This activity checks if the user is a male or female. - Add two Assign activities.
- Connect one to the True branch of the Flow Decision activity.
- In the Properties panel, in the To field enter the
Male
variable. - In the Value field, type True. This assigns the True value to the
Male
variable when theGender
= "Male" orGender
= "male" condition is met. - Connect the second Assign activity to the False branch of the Flow Decision.
- In the Properties panel, in the To field, enter the
Male
variable. - In the Value field, type False. This assigns the False value to the
Male
variable when theGender
= "Male" orGender
= "male" condition is not met. - Add a new Flow Decision and connect the previously added Assign activities to it.
- In the Properties panel, in the Condition field, type
Male
= True. - Add a Message Box activity and connect it to the True branch of the Flow Decision.
- In the Properties panel, in the Text field, type
Name
+ " is a " +Gender
+ ".". This message displays the name of the user and its gender, ifMale
is true. - Add another Message Box activity and connect it to the False branch of the Flow Decision.
- In the Properties panel, in the Text field, type
Name
+ " is a " +Gender
+ ".". This message displays the name of the user and its gender, ifMale
is false. The final project should look like in the following screenshot. - Press F5. The automation is executed. Note that the final Message Box displays the message as expected.