studio
2022.10
false
- Release Notes
- 2022.10.3
- 2022.10.4
- 2022.10.5
- 2022.10.7
- 2022.10.8
- 2022.10.9
- 2022.10.10
- 2022.10.11
- 2022.10.12
- 2022.10.13
- 2022.10.14
- 2022.10.15
- 2022.10.16
- 2022.10.17
- 2022.10.18
- Getting Started
- Introduction
- The User Interface
- Keyboard Shortcuts
- Signing in to Your Account
- Configuring Studio Settings
- Project Templates
- Orchestration Process
- Background Process
- Robotic Enterprise Framework
- Trigger Based Attended Automation
- Creating a Basic Process
- Creating a Basic Library
- Tutorials
- Setup and Configuration
- Hardware and Software Requirements
- Install Studio
- Deployment guidelines
- Services Studio Connects To
- Common Installation Errors
- Modify or Uninstall Studio
- Activate Studio
- About Flex Licensing
- Update Studio
- Command Line Parameters
- Supported Applications and Technologies
- Enabling Gmail for Email Activities
- Opting Out of Telemetry
- Studio Executables
- Automation Projects
- About Automation Projects
- Deprecation of the Windows-Legacy Compatibility
- About the Windows - Legacy Compatibility
- About the Project.Json File
- About Publishing Automation Projects
- About Libraries
- Loading Web Services in Libraries
- Activities Generated from Web Services
- Designing Automations
- Managing activity packages
- Configuring Activity Project Settings
- Signing Packages
- Governance
- Importing Entities
- Modern Design Experience
- Linking a Project to an Idea in Automation Hub
- Using the Data Manager
- Dependencies
- About Dependencies
- Managing Dependencies
- Project Dependencies Mass Update
- Mass Update Command Line Parameters
- Missing or Invalid Activities
- Types of Workflows
- Sequences
- Flowcharts
- State Machines
- Global Exception Handler
- Workflow From a Template
- File Comparison
- About File Comparison
- Comparing Files
- Automation Best Practices
- Workflow Design
- UI Automation
- Project Organization
- Automation Lifecycle
- Methodology for reusing UI components
- Source Control Integration
- About Version Control
- Managing Projects With GIT
- Managing Projects With TFS
- Managing Projects With SVN
- Workflow Diff
- Debugging
- About Debugging
- Test Activities
- Debugging Actions
- The Locals Panel
- The Call Stack Panel
- The Breakpoints Panel
- The Watch Panel
- The Immediate Panel
- Remote Debugging
- Profile Execution
- The Diagnostic Tool
- About The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- Naming Rules
- 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
- Design Best Practices
- 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
- Project Anatomy Rules
- ST-ANA-003 - Project Workflow Count
- ST-ANA-005 - Check Project.json Exists
- ST-ANA-006 - Main Workflow Exists
- ST-ANA-009 - File Activities Stats
- Maintainability and Readability Rules
- ST-MRD-002 - Activity Name Defaults
- ST-MRD-004 - Unreachable Activities
- ST-MRD-005 - Redundant Sequences
- ST-MRD-007 - Nested If Clauses
- ST-MRD-008 - Empty Sequence
- ST-MRD-009 - Deeply Nested Activities
- ST-MRD-011 - Write Line Usage
- ST-MRD-017 - Incomplete If
- Usage Rules
- 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
- Performance and Reusability Rules
- ST-PRR-004 - Hardcoded Delay Activity
- Reliability Rules
- ST-REL-006 - Infinite Loop
- Security Rules
- ST-SEC-007 - SecureString Argument Usage
- ST-SEC-008 - SecureString Variable Usage
- ST-SEC-009 - SecureString Misusage
- Variables
- Managing Variables
- The Variables Panel
- Types of Variables
- UiPath Proprietary Variables
- Arguments
- Managing Arguments
- The Arguments Panel
- Using Arguments
- Imported Namespaces
- About Imported Namespaces
- Managing Namespaces
- Control Flow
- About Control Flow
- Control Flow Activities
- The Assign Activity
- The Delay Activity
- Example of Using the Delay Activity
- The Do While Activity
- Example of Using a Do While Activity
- The If Activity
- Example of Using an If Activity
- The Switch Activity
- Example of Using a Switch Activity
- The While Activity
- Example of Using a While Activity
- The For Each Activity
- Example of Using a For Each Activity
- The Break Activity
- Example of Using a Break Activity
- Object Repository
- About Object Repository
- Creating an Object Repository
- Reusing objects and UI libraries
- Logging
- Studio Logs
- Setup Logs
- OCR Diagnostic Logs
- Logging Levels
- Types of Logs
- Protecting Sensitive Information
- The ScreenScrapeJavaSupport Tool
- About the ScreenScrapeJavaSupport Tool
- Argument Descriptions for the ScreenScrapeJavaSupport Tool
- Studio testing
- Introduction
- Application Testing
- Testing project templates
- SAP Testing Project
- Test Cases
- Data-Driven Testing
- Test Data File
- Auto-generated Test Data
- Data Service
- Test Data Queues
- RPA Testing
- Execution Templates
- Test Case Templates
- Test Explorer
- Test Results
- Activity Coverage
- Descriptor Coverage
- Mock Testing
- API Test Automation
- Extensions
- About extensions
- SetupExtensions tool
- UiPath Remote Runtime
- Troubleshooting
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- Extension for Chrome
- Group Policies
- Troubleshooting
- Chrome Extension on Mac
- Extension for Edge
- Group Policies
- Troubleshooting
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Extension for Firefox
- Troubleshooting
- Extension for Java
- Troubleshooting
- Extension for Silverlight
- Troubleshooting
- Extension for Citrix
- Troubleshooting
- Extension for Microsoft Remote Desktop and Apps
- Configure the UiPath Remote Plugin for custom remote applications
- Troubleshooting
- Extension for VMware Horizon
- SAP Solution Manager plugin
- Excel Add-in
- 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
- Automating Applications Running Under a Different Windows User
- Validation of large Windows-legacy projects takes longer than expected
OUT OF SUPPORT
Studio User Guide
Last updated Nov 3, 2025
The SAP Testing Project Template is a project template based on an execution template. Through this template you can understand the usage of SAP transactions and SAP programs during the test case execution, as part of Change Impact Mining. Through SAP Monitoring, information about executions of SAP transactions and programs, and associated dependencies is collected at runtime.
Any new or current test case can be assigned to the execution template called
SAP Change Impact Mining.xamlNow the test case runs in parallel with SAP Session Attributes Change Trigger to track and log any change in the SAP sessions attribute (e.g. SAP transaction information).
By default, monitoring is set for SAP Transactions and SAP Programs. You can define which SAP session attributes you are interested in.
For information on all available SAP session attribute, see .
The data collected at runtime is then sent to Orchestrator as a test execution attachment.
For more information, see Analyze test executions.
In Test Manager, this information is applied to test cases as labels.
You can use this information to filter test cases by SAP labels, and then create a test set that will execute the affected test cases.