studio
2023.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-021 - Hardcoded Timeout
- 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
- Coded automations
- Trigger-based Attended Automation
- 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
- About extensions
- SetupExtensions tool
- UiPathRemoteRuntime.exe is not running in the remote session
- UiPath Remote Runtime blocks Citrix session from being closed
- UiPath Remote Runtime causes memory leak
- UiPath.UIAutomation.Activities package and UiPath Remote Runtime versions mismatch
- The required UiPath extension is not installed on the remote machine
- Screen resolution settings
- Group Policies
- Cannot communicate with the browser
- Chrome extension is removed automatically
- The extension may have been corrupted
- Check if the extension for Chrome is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and Incognito mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Chrome
- Chrome Extension on Mac
- Group Policies
- Cannot communicate with the browser
- Edge extension is removed automatically
- The extension may have been corrupted
- Check if the Extension for Microsoft Edge is installed and enabled
- Check if ChromeNativeMessaging.exe is running
- Check if ComSpec variable is defined correctly
- Enable access to file URLs and InPrivate mode
- Multiple browser profiles
- Group Policy conflict
- Known issues specific to MV3 extensions
- List of extensions for Edge
- Extension for VMware Horizon
- SAP Solution Manager plugin
- Excel Add-in
- Troubleshooting
Studio User Guide
Last updated Nov 18, 2024
Workflow Diff
Comparing changes between a process, library,
project.json, or .txt file in a local repository and the latest version from GIT, TFS, or SVN is done using Workflow Diff in Studio. It shows a side-by-side comparison between the two files, highlighting added or removed activities, packages,
variables, arguments.
When comparing changes between two
.xaml files, Workflow Diff shows added or removed activities, variables, arguments, or modified activity properties. Default values for properties are
not visible in the Show Changes window.
Workflow Diff is used for comparing changes made in the
project.json file, such as adding, updating or removing dependencies, modifying the runtime rule, making workflows private, or setting
a Global Exception Handler.
Note: Workflow Diff must be used after the file is saved, and before it's checked into the source control repository.
- Check out a workflow or library from the GIT, TFS, or SVN repository, make modifications, and then save the file, but don’t check it in.
-
In the Project panel, right-click the
.xamlfile and click Show changes. The Workflow Diff window is displayed.
The Remote column on the left displays the
.xaml structure for the file versioned under the GIT, TFS, or SVN repository, while the Local column on the right shows the file mapped locally.
The Modified Properties columns show the before and after states of activities properties, sequence display names and text boxes.
Note: If the locally mapped
.xaml file is corrupted, the Workflow Diff window is opened in the project.json/.txt view.
- Check out the
project.jsonfile in Studio and open the Manage Packages window to install, update, and remove dependencies. Click on Save to update theproject.json. -
In the Project panel, right-click the
project.jsonfile and click Show changes. The Workflow Diff window is displayed.
The Remote column on the left displays the
project.json structure for the file versioned under the GIT, TFS, or SVN repository, while the Local column on the right shows the file mapped locally.
Dependency names are arranged alphabetically to aid with the comparing process between the two files.
Field Descriptions for the Workflow Diff Window
|
Option |
Description |
|---|---|
|
Previous |
Navigates to the previous change in the compared files. |
|
Next |
Navigates to the next change in the compared files. |
|
Collapse All |
Collapses all nodes in the
.xaml files.
|
|
Expand All |
Expands all nodes in the
.xaml files.
|
Aside from Workflow Diff, Show History from the same context menu allows you to compare changes between two versions of the same file. This option is available
for GIT, TFS, and SVN versioned files, either
.xaml or project.json.
- Check out your project from source control in Studio. Make sure that the project has multiple commits.
-
In the Project panel, right-click the
.xamlfile and click Show History. The History window is displayed. - The History window displays the revisions made to the file, together with Commit messages, the author, and the date. Double-click a revision to open the Workflow Diff window and view changes between the selected file and the previous version.
The Details tab part of the History window displays the author, date, revision number, and commit message. The Changes tab reveals the files that were in during the selected commit. Double-click a file to open the Workflow Diff window and view changes between the selected file and the previous version.
Context Menu for Show History
Right-click a revision entry in the Show History window to open the context menu with options.
|
Option |
Description |
|---|---|
|
Compare with Previous |
Compares the selected version of the file with the previous version. |
|
Compare with Local |
Compares the selected version from GIT, TFS, SVN with the local version. |
|
Compare with Latest |
Compares the selected version of the file with the latest version. |
|
Compare Selected |
Compares the selected two versions of the file. Use Ctrl + Click and then right click to compare the versions. When more than 2 versions are selected, the newest and oldest are compared. |
