Release date: 24th April 2019
The highly anticipated GIT Integration with Studio is here. We’re bringing you all the goodies to help you clone a repository, create and manage branches, commit new project versions, and manage your work straight from Studio in a smooth way. For more details, check out the documentation.
Studio can now generate activities from SOAP and Swagger web services through the New Service wizard available for libraries. The service is added to the library’s dependency tree and from there on, you can add activities to your library from the Activities panel. Check out the documentation for more details.
Comparing changes between a process, library,
.txt file in a local repository and the latest version from GIT, SVN or TFS is done using File Diff in Studio. It shows a side-by-side comparison between the two files, highlighting added or removed activities, packages, variables, arguments. Read more about File Diff here.
The Compare Files feature offers the possibility to compare two similar files in the same automation project. Simply use the context menu options in the Properties panel to select the two
.txt files for comparison. Read more about this here.
Additionally, the Show History feature displays the difference between the file currently versioned under source control and previous versions. Use Show History from the Properties panel context menu as revealed in the documentation
To improve interoperability and streamline project versioning, Studio now has Semantic Versioning. Versions of your projects can now be set in the
major.minor.patch format, and you can set a
Prerelease tag for intermediary versions. Read more about semantic versioning in the documentation.
To enhance your automation experience, we’ve added Global settings and Default Locations for projects. Learn more about this here.
On top of that, we’ve also incorporated Project settings for renaming a project and changing its description, as mentioned here. Last but not least, Library properties bring the option to add a tooltip and a help link to the new activity. Read more about this here.
Package integrity and authenticity are vital in terms of security, which is why we’re introducing Package Signing for signing libraries and processes with your own certificate. The feature is available both from Studio’s Publish window and command-line. Learn how to sign packages when publishing processes here.
Furthermore, in support of this feature, you should know it is possible to enforce your Robots to execute only signed packages at install-time, by using the newly added
ENFORCE_SIGNED_EXECUTION parameter. More information about this is available here.
Debugging involves lots of attention to details and tinkering to bring the workflow to its best shape. After inspecting or making changes during debugging, use the Focus button to return to the activity where debugging stopped and then click Continue to resume from where you left off. Check out the documentation for more info.
In addition, we’ve implemented a way to enable or disable all or just a single breakpoint in a workflow, and persist these settings when reopening the project in Studio. Find out more here.
Automation processes developed in Studio now come with the option to prevent them from being paused. This means that when the process is running, the Pause button in the Robot Tray is disabled. This feature is useful when pausing an asynchronous execution might cause it to break. Find out how to use this option documentation.
The Package Manager now integrates support for activity packages with license agreements. Make sure to read and accept the license terms before installing the package to your automation project. To find out more check the documentation.
Studio introduces High Contrast mode, which adapts to the Windows setting and switches with a simple restart. To find out more check the documentation.
Renaming an argument from the Argument panel updates all its occurrences across the file.
Select one or multiple variables or arguments from the panel and copy them to another workflow. The name, type, and default value is also copied.
One or multiple variables can now be converted to arguments and the other way around from the panel context menu.
We’ve added keyboard shortcuts for creating both In and Out arguments. Check this page for an extended list of keyboard shortcuts in Studio.
Variable and argument types part of assemblies proprietary to Studio or Robot are now hidden. This was done to ensure forward compatibility in the event of any internal changes that we may bring to these assemblies. Workflows that reference types from such assemblies should not be affected at runtime. For more details, check the documentation.
Feeds for Activities Packages are now available in Studio Backstage view too, not just from the Package Manager. This way, you can adjust activity feeds even before you open a project. Find out more about this here.
Favorite activities can now be marked in the Activities panel. Simply use the new Pin Favorites context menu option and have all of your most used activities always visible in the panel. Check the documentation for additional info.
The project’s Full Dependency Tree is now visible in the Project panel. All you need to do is expand the dependency to view sub packages and their versions. In addition, it is now easier to differentiate between resolved, unused, not found and best match dependencies. Find more information about this here.
Info on Studio version, type of installer, device ID, license expiration and more is now available in Studio Backstage view as well. Hover over the details and get the exact date when the current Studio was released.
The Robotic Enterprise Framework template from Studio now includes a
project.json and UiPath.Credentials.Activities as part of its dependencies.
Studio also brings improvements in terms of usability and accessibility. As such, tooltips now remain persistent on hover, and a Restart button when changing the interface language and theme. Learn how to access it in the documentation.
For those that work offline, we have some good news: you can disable the default online feeds for Robot during the deployment process. This facilitates a seamless installation process even in restrictive environments without Internet access, from the command line. For more information, access this page.
You can now configure the download location of your automation processes and their dependencies, for Studio and Robot, through the command line of the
UiPathStudio.msi installer. This feature provides a customizable architecture to suit both secure deployments and hotseat scenarios. To read more about the newly added
PACKAGES_FOLDER parameter and how to use it in your mass-deployment of Robots, see this page.
Moreover, you can add your own activity feeds at install-time by using
UiPathStudio.msi's command line. More information about the
CUSTOM_NUGET_FEEDS argument and how to use it to set up your environment can be found here.
In our quest for continuous improvement, we collect usage and performance data to help diagnose problems and enhance our products. This feature now also comes with the possibility of turning off telemetry at install-time through the
TELEMETRY_ENABLED command line parameter or later on using the dedicated configuration keys. More information is available here for
To help you get a better handle on what happened during the setup process,
UiPathStudio.msi now also logs licensing information (
regutil.exe) while it is running, at a custom location.
UiPathPlatformInstaller.exe now also verifies if you have IIS 7.5+ and URL Rewrite installed on the machine, enabling a smooth set up process.
- GIT Integration with Studio does not currently support two-factor authentication. As a workaround, use SSO authentication method with a personal token, or the basic access authentication method.
- To merge a branch into the master of a GIT remote repository, you need to have the master branch checked out in Studio and then merge the modified branch into master.
- When trying to push a project to a GIT remote repository that has two-factor authentication, the Output panel shows a success message even though the operation failed, as two-factor authentication for GIT is not yet supported in Studio.
- Publishing libraries from the command-line user interface does not publish previously generated web service references. More details about this are available here.
uipath.configfile is not properly populated if you upgrade your Studio instance to v2019 Fast Track without specifying the telemetry parameter. To rectify this, please read this page.
- If you used the Extract as Workflow feature for an activity with two referenced variables, only one of them was extracted as an argument.
- If you placed a breakpoint on an invoked workflow and then used Step Over, the debugging did not return to the parent workflow.
- Fixed an issue that prevented variables in a Flowchart from being renamed across activities that contain Expression and Condition properties.
- The properties of the last executed activity were not displayed in the Locals panel after using Step Over while debugging.
- Fixed an issue that caused certain hotkeys to be improperly enabled while the Publish Project window was opened.
- Fixed an issue that made it possible for Studio v2018.3.3 and v2018.4.4 to publish
.xamlfiles in project subfolders with validation errors.
- When connecting Studio to Orchestrator Community Edition, the label Community Edition is displayed in Studio Backstage view, the Help tab. It is recommended to disconnect Studio from Orchestrator in order to update to v2019.4.
- Added a notification when trying to close the Manage Packages window although there are unsaved changes, like activities packages marked for installation, changed runtime rules and so on.
- Fixed an issue that caused Studio to hang in some scenarios after saving or installing activities packages to a large
.xamlfile of about
- Fixed an issue that resulted in validation errors for certain types of variables after using Extract as Workflow.
- An error message is now shown if you add a non-supported value for the Key Modifier property when using Dark theme.
- Fixed an issue that prevented you from adding dependencies or making project changes after resuming connection to a project hosted on a network drive.
- All items in the Activities and Project panel are arranged alphabetically.
- Fixed an issue that caused the focus to remain stuck on a versioned file in the Project panel, even though the file was closed in the Designer panel.
- During the migration of projects in Studio, the UiPath.UIAutomation.Activities and UiPath.System.Activities packages received the highest applicable version in the local feed instead of the UiPath.Core.Activities pack version.
- Fixed an issue that prevented Studio from logging exceptions generated by copying a large flowchart from one
.xamlfile to another.
- To ensure a smooth experience in offline environments, the list of activity dependencies has been updated in all our installers. Please note that as a result, the size of the artifacts has increased.
- An error message was displayed if you closed the
UiPathPlatformInstaller.exewizard while the installation process was being executed.
Updated about a month ago