- 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
- Managing Arguments
- The Arguments Panel
- Using Arguments
- Imported Namespaces
- Control Flow
- Object Repository
- Logging
- The ScreenScrapeJavaSupport Tool
- 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
- JxBrowser applications troubleshooting
- User Events Monitoring
- Citrix Troubleshooting
- Automating Applications Running Under a Different Windows User
Due to the nature of arguments, you are going to use them a lot in relation with the Invoke Workflow File and Launch Workflow Interactive activities. They can be found in the Activities panel, under Workflow > Invoke and they enable you to browse for a project, and import and edit their arguments.
Example of Using an Argument
To exemplify how to use an argument in an automation with an Invoke Workflow File activity, we are going to create two separate sequences. A very simple one in which to assign a value to an argument, and a second that invokes it and displays the value in a message box.
-
Create a new sequence.
-
In the Arguments panel, create an argument,
out_StoreValue. -
From the Direction list, select Out, and do not change the Argument Type from String.
-
Add an Assign activity to the Designer panel.
-
In the Properties panel, in the To field, add the
out_StoreValueargument. -
In the Value field, type a string, such as "How does one use an argument?".
The first project should look like in the screenshot below.
-
Create a new sequence.
-
Create a string variable,
FinalValue. -
Add an Invoke Workflow File activity to the Designer panel.
-
On the activity, click the Browse (…) button and browse for the previously created sequence.
-
Click Import Arguments. The Invoked Workflow’s Arguments window is displayed. Note that the argument of the first sequence is displayed here.
-
In the Value field, add the
FinalValuevariable and click Ok. The argument is imported and the value from it is going to be stored in the current project through theFinalValuevariable. -
Add a Message Box activity under the Invoke Workflow File.
-
In the Properties panel, in the Text field, type
FinalValue+ " This is how", for example.The second automation should look like in the screenshot below.
-
Press Ctrl + F6 in the second sequence. The automation is executed correctly and the message box displays the desired text.