UiPath Studio Community Changelog

What's new in UiPath Studio Community 22.10.5

Feb 1, 2023

Option to disable the Windows - Legacy deprecation message
The connection selector now supports displaying Integration Service connections based on the folders where they were added.

New in UiPath Studio Community 22.10.4 (Dec 7, 2022)

New in UiPath Studio Community 22.10.3 (Oct 31, 2022)

What is new:
Support for global variables and constants
New design for activities
Design-time triggers
Windows is the new default project compatibility
Design automations in Studio and Studio Web
Profile execution
Introducing the Data Manager
Customize activities generated from libraries
Extract processes as libraries
Quick tour on first run
Edit text files in Studio
Improvements:
Workflow Analyzer
Usability
Test automation
Other improvements
Breaking changes:
Studio 2022.10 is not compatible with older cross-platform activity package versions that were available in Studio 2022.4 or earlier. If you created cross-platform projects in Studio versions prior to 2022.10, update the installed packages to the latest versions before you edit them in Studio 2022.10. Some properties may no longer be available for editing.
Bug fixes:
The right Ctrl and Alt keys did not work when used in keyboard shortcuts on Japanese keyboards.
An error occurred when opening a workflow file that contained multiple Flow Switch activities connected to the same activity.
If a C# library which included a dependency to the UiPath.DataService.Activities package was installed in a VB project, an error caused by duplicate references to the UiPath.DataService.Definition assembly occurred when you tried to run the project.
The installation sometimes failed if telemetry was not disabled during the installation and a proxy server was in use.
Studio could become unresponsive during project validation if a project analysis was triggered when the main workflow file was open and it contained unsaved changes.
The Project Dependencies Mass Update Tool did not successfully update projects from TFS if the project paths contained spaces.
Studio allowed adding package icons with the ICO extension, which caused errors when publishing projects.
Tooltips added to workflow files in library projects were not saved.
Workflow analysis sometimes failed to run when a project included an Invoke Code activity.
Removing unused variables sometimes also removed variables that were used.
The Design Properties window did not open for certain argument types, preventing you from adding tooltips to the arguments.
When a library created in a Studio version prior to 2021.4 was updated in a later Studio version, execution was slow in projects where the updated library was installed as a dependency.
Clicking inside the Activities or Project panels sometimes caused the panels to move unexpectedly.
Renaming Dictionary type variables and arguments did not update the names in the activities where they were used.
You were prompted to restart Studio after executing a test case.
Selecting multiple files from different subfolders in the Project panel and then deleting them caused the entire project to be deleted.
The direction of Dictionary type arguments used in an activity was incorrectly changed when the activity was extracted as a workflow.
When multiple interdependent libraries were installed in a project, opening workflow files from that project caused higher than expected memory consumption and Studio sometimes crashed.
Referencing a file path in a library activity was causing the current directory to change unexpectedly when executing projects where the library was installed as a dependency. To avoid this issue, use the new global constant UiPath.Constants.Project.Location when you need to reference a file path in a library project. For example, UiPath.Constants.Project.Location+"InputDataEmployee.txt".
Installations didn’t complete successfully when performed in mass deployments through SCCM.
When you configure a device, the Appium Url field now provides an inline error message stating that HTTPS is not supported.
Executing a test case with a template containing multiple placeholders did not fail when one of the placeholders was not placed in a Sequence activity. This behavior has been addressed by providing an error message through the Studio logs.
Running test cases with templates containing multiple arguments failed when the workflow had arguments.
Addressed an issue in which the Test Case Without Annotations rule was not updated properly.
Importing data from Excel occasionally resulted in cells formatted as Date due to a language compatibility issue.
Using a variable in the Random Date activity failed during Design time.
Known issues:
You cannot close or float Studio panels.
On rare occasions, an error with the message System.ArgumentException: Cannot dock to the side of an auto-hide target. (Parameter 'target') occurs during project compilation. As a workaround, reload the project.
Global variables are not serializable, and therefore incompatible with long-running persistence activities.

New in UiPath Studio Community 22.4.4 (Aug 3, 2022)

New in UiPath Studio Community 2020.10.4 Beta 0001 (Jan 27, 2021)

Improvements:
Installation and Activation:
When you install using the .msi installer, a screen now prompts you to choose what to install at the beginning of the installation process. The installation is configured based on your choice, and you only need to use the advanced options of the installer if you want to select the Studio or Robot features to install.
You can select one of the following:
Studio - Installs UiPath Studio, Assistant, and the user-mode Robot for creating and testing automations.
Assistant - Installs UiPath Assistant and the user-mode Robot for running attended automations.
Unattended Robot - Installs the service-mode Robot for running scheduled unattended automations (via Orchestrator) and UiPath Assistant for troubleshooting.
When you first launch Studio after installation, you are now prompted with the recommended licensing method for your installation scenario:
If you used an installer downloaded from Automation Cloud, you are prompted to activate by signing in to your UiPath account.
If you used an installer obtained after your organization purchased the on-premises UiPath Platform, you are prompted to activate by connecting to Orchestrator with your machine key.
If you installed Studio as part of a trial of the on-premises UiPath Platform, you are prompted to activate by adding a license key.
If you perform a fresh installation and you have an Enterprise license, the Studio profile is now automatically selected based on the license allocation in Orchestrator. If you installed Studio as part of a trial of the on-premises UiPath Platform, you are prompted to select which profile to use during activation (Studio, StudioX, or Studio Pro).
Governance:
You can now enforce the governance policy through Orchestrator by creating a uipath.settings.config folder and either adding the contents of the governance file in an asset named uipath.studio.governancepolicy or adding the path to the governance file in an asset named uipath.studio.governancesource. For more information, see Governance.
The following location settings can now be configured through the governance file: Project path, Publish process URL, Publish library URL, Publish project templates URL.
Usability:
The tooltip displayed when you hover a project from the Open Recent list in the Start tab in Studio Backstage View now also displays the path to the project.json file.
A new option named Search by Description has been added to the View Options filter activities
menu in the Activities panel. When this option is enabled, searching in the Activities panel returns results from activity descriptions as well as activity names. By default, this option is not enabled and searches return results from activity names only.
To make it easier to identify screens and elements from the Object Repository, unique IDs are now displayed in the Edit Screen and Edit Element windows. In addition, when you open the windows from the Snippets panel, a version number is displayed as well.
For greater clarity, the Workflow Analyzer Rules Location setting in Studio Backstage View > Settings > Locations has been renamed Custom Workflow Analyzer rules location. In addition, its corresponding tooltip includes more details about the location.
The Connect package source has been renamed Marketplace to correspond with the renaming of the collaborative library of RPA components to UiPath Marketplace.
Known Issues:
If you debug a file or a project that contains Pick and Pick Branch activities with both Slow Step and Execution Trail enabled, the execution gets stuck when it reaches the Pick activity. As a workaround, disable one of the options (use either Slow Step or Execution Trail, but not both).
Because the namespace of several System activities has changed after version 19.4, if you added one of the affected activities to the list of Favorites using version 19.4 or earlier of the System activities package, the activities no longer appear in the Favorites list when you update the package to a version after 19.4. The available workaround is to add the activities to the Favorites list again.
The activities with a changed namespace are: Log Message, Filter Data Table, Message Box, File Change Trigger, Invoke Code, Retry Scope, Do While, and While.
When you publish a project to a custom URL that becomes unavailable while the Info dialog box at the end of the publishing process is open, if you click the Location link in the dialog box, it can take longer than expected (over 1 minute) for an error to be displayed and inform you that the location cannot be found.
An error occurs when you use the Test Activity feature for an activity that requires a scope.
In Studio Pro:
Renaming a Studio Pro test project that includes test cases causes an error when publishing the tests.
Design time and runtime performance of C# projects is lower when compared to VB.NET. When runtime performance is essential, we recommend using VB.NET instead of C#. We plan to update the speed related to C# with future updates.
You cannot delete an activity within a mock file if the mock file is derived from an unresolved activity.
Bug Fixes:
Pressing Enter in multi-line editors that have a single-line height no longer adds a new line, it now submits the expression instead.
The Expression Editor no longer opens with the cursor positioned at the end of the line; the cursor position is now at the start of the line.
Fixed an issue that could cause publishing a library to fail when the library contained Invoke Workflow File activities.
When you publish from the command line with the command UiPath.Studio.CommandLine.exe publish
, the output now displays the process name, publish location, and version.
Fixed an issue that could cause a namespace used in a deeply nested activity to be incorrectly removed when you selected to Delete All Unused option from the Imports panel context menu.
If a process contains an activity from a library and the Environment.CurrentDirectory
function is used in that activity, the current directory of the process no longer incorrectly changes to the current directory of the library.
Projects no longer have missing default dependencies when Studio is not connected to Orchestrator, all external feeds are disabled, and the local feed is the only enabled package source.

New in UiPath Studio Community 2020.4.1 (May 14, 2020)

New in UiPath Studio Community 2020.4.0 (Apr 8, 2020)

New in UiPath Studio Community 2019.1.0 (Feb 6, 2019)

New in UiPath Studio Community 2018.4.3 (Jan 22, 2019)

New in UiPath Studio Community 2018.4.1 (Dec 13, 2018)

The latest release of 2018 brings us a Long Term Support version and multiple features to help you in terms of scalability, stability, as well as user experience.
With Citrix environments being so popular, we are further extending automation capabilities with native support for Citrix XenApps. Once the Citrix Remote Runtime component is deployed on all the Citrix server machines and the new Citrix extension is installed on the client machine, elements in such environments are natively detected by Studio and the Robot. As such, selectors are properly built, without any hassle.
Authentication:
You asked, we delivered. This release ships with the much-awaited support for SAML 2.0 which allows Orchestrator to handle single sign-on authentication. You can now take advantage of the speed and convenience of accessing your Orchestrator instance with the same set of credentials used within your organization. In this regard, the new ExternalAuth.Saml2.Enabled parameter has been added in the web.config file.
A notable addition in this newest release, Smart Card Robot Authentication is now here to handle Common Access Cards and Personal Identity Verification support. As such, Unattended, Development, and NonProduction Robots can simply use your SmartCard to start sessions on machines, besides the conventional way. The connection method is easily selected when a Robot is created or edited. Check out how it is done on this page. Lastly, the Orchestrator API, namely the /odata/Robots endpoint, has been updated to accommodate this functionality.
Scalability:
Do you think Attended Floating Robots are sweet? Good! Because the Floating Robots feature has been augmented to incorporate Development Robots as well. This is a major step forward in ensuring better, more convenient resource management of your Non-Persistent VDIs and hotseat environments. Create and configure your Development Floating Robots and connect to them from any defined machine.
This, paired with the fact that you can now activate your Studio license from Orchestrator through the Robot that connects them, makes for a broader automation experience, since workflows can be executed, modified, and debugged with Development Floating Robots.
Orchestrator’s scheduling mechanism has been substantially improved in terms of performance. As a result, enabling multiple custom schedules in clustered environments does not pose a threat to the performance of system operations.
Extensibility:
For an even more fruitful partnership between your UiPath automation and your complex existing app network, we made it possible to use webhooks with Orchestrator. You can now subscribe to Orchestrator events and send them to any external DCM, BPM, or CRM solution. Multiple users can be informed, for example, that there is a new item in a given queue, a schedule has failed, or a process has been updated. As you might have gotten used to by now, the Orchestrator API has also been updated to accommodate this new functionality.
This release, we bring you the first incarnation of the SAP BAPI activities pack. This package enables RPA Developers to invoke a SAP BAPI using a workflow. The package comes with a SAP BAPI Wizard that enables the user to generate a workflow for a specified BAPI. This workflow can then be invoked from any automation process by using the Invoke Workflow File activity. The Open SAP Connection and Close SAP Connection activities manage a connection to the SAP Instance. It is unique for each SAP Instance you connect to and, once obtained, it is stored in a IConnectionService proprietary variable, and can be subsequently used throughout your automation projects for connecting to the said SAP Instance.
Reusability:
To remove the necessity of configuring the same project again and again, any automation you now create, along with all its dependencies, libraries, invoked workflows, custom components, and so on, can be saved as a Template. Thus, your custom Templates are available at your fingertips in Studio, ready to be used for new projects and are persistent across future updates.
Agility:
Centered around improvements regarding error handling, the new Global Exception Handler project template is aimed at executing a process every time the workflow encounters an error. When the error occurs during execution, the Global Exception Handler steps in and performs a user-defined action. It may either continue the execution and re-throw the exception, ignore the error, retry to execute the activity or abort the execution. The Exception Handler comes in handy during debugging, as it pauses the execution, allowing users to inspect the target application, correct it or retry the activity which threw the error.
Fancy using the command line? You might want to know that starting processes this way is now a thing on all Robots, regardless of their type. As long as a process is available for the Robot Agent (Tray), it can be started with a simple command, as well as with arguments. Used along with the Windows Task Scheduler, it is an efficient way to have processes started as soon as a user logs in. The appropriate process is downloaded by the Robot before execution, or updated if necessary.
Document Processing:
The IntelligentOCR package has received a major update, as we've developed three new activities that enable you to approach Document Processing in a much simpler manner.
The new activities are:
Present Validation Station - offers attended users the ability to make real-time CRUD (Create, Read, Update, and Delete) operations on documents for the purpose of classification and human data validation and extraction.
Prepare Validation Station Data - creates a bridge between FlexiCapture's Process Document activity and the new Validation Station, ensuring a much more user-friendly data validation experience.
Digitize Document - provides a new way of generating text versions from incoming documents, being able to process any PDF and most image formats.
User Experience:
Intended to make collaboration with Attended Robots easier, the Robot Agent (Tray) displays the currently running process in an individual widget, while allowing you to pause, resume, or stop the execution. Not only does this help you keep an eye on what the Robot is doing, but also to pause the execution in case something unexpected happens and resume once everything is in order.
Also, to facilitate identifying which step the Robot is performing at any given time, we have created the Report Status activity and added it to the System activities pack, which enables you to create a custom status message that is displayed in the Robot Tray at any point in the execution of a workflow.
Furthering our efforts to bring you a smoother user experience, UiPath Platform now incorporates the highly-anticipated Dark Theme. Both Studio and Orchestrator have been painted in an eye-soothing gray, with bits of blue to keep the products’ color signature. Panels and controls are all available in a darker shade, making the whole UI more appealing and easier on the eyes. Please note that for Studio this feature is still considered experimental.
If you ever wanted to release the licenses on a machine, you are familiar with the tedious task of having to contact your IT support team and waiting for it to happen. As of v2018.4, this is no longer a problem as you can now easily enable/disable non-production and unattended-purposed machines. License consumption in this scenario is now yours to manage and it can be done straight from the convenience of your own Orchestrator instance.
Improvements:
Studio:Improvements have also been made available to the source control functionality in Studio. The newly introduced Repository Browser gives you a peek inside TFS and SVN repositories, with the option to have multiple projects in one place, and check out any one you want.
Continuing the efforts on improving error handling and making the whole automation process more comprehensive, error messages for certain activity packages missing from workflows are more exhaustive. Missing or invalid activities are marked in the Designer panel, while an error banner provides additional information regarding the workflow and its unresolved dependency conflicts.
Custom NuGet feeds that require authentication can now be added to the Package Manager through the NuGet.config file, and activities packages that they contain can be imported to automation projects.
The Expression Editor in the Properties panel keeps its size when reopened, making it easier to read through the text or expressions that you’ve saved inside.
Orchestrator:
Validation has been added to the /odata/Processes/UiPath.Server.Configuration.OData.SetArguments endpoint. Additionally, please note that this endpoint can no longer be used to change the input and output parameters of an automation package if you upload it to Orchestrator through the API, the Packages page, or the NuGet feed.
Additionally, please note that the serialized string of input and output parameters is now used all throughout Orchestrator.
We simplified the process of creating an Attended Standard Robot, by removing the Password field. A gladdening "side-effect" of the removal is the consistency between the Floating and Standard Robot-creation scenarios.
All email address input fields are now limited to 254 characters.
In terms of setup, you might want to know that the UiPathPlatformInstaller.exe, UiPathStudio.msi, and UiPathOrchestrator.msi installers now also check the operating system to ensure a smooth execution of the entire ecosystem.
SignalR has been upgraded to v2.2.3 in an effort to attain a more reliable WebSocket communication and better memory management.
The performance of deleting Robots has been significantly improved in the context of a large deployment.
A confirmation dialog is now displayed when you grant a user Edit permissions on Robots. This comes in addition to the existing Edit permissions on Settings, Roles, and Users which require user confirmation.
The Jobs and Robots charts on the Dashboard have been enhanced so as to achieve better visibility.

New in UiPath Studio Community 2018.3.3 (Nov 21, 2018)

New in UiPath Studio Community 2018.3.2 (Nov 1, 2018)

New in UiPath Studio Community 2018.3.1 (Oct 23, 2018)

What’s New
The third release of this year puts a great emphasis on a central component of UiPath Platform, Studio. Thus, Studio gets some very appealing UI changes, important features in terms of project control and component reusability, as well as various enhancements under the hood. The focus has been on redesigning the Studio architecture and setting the building blocks for a more appealing and reliable Studio, in a continuous effort to increase developer productivity and efficiency.
With this in mind, Studio now comes with a reduced start-up time and improved reliability, together with optimized resource consumption.
Another important announcement that we want to share with you is that UiPath Robot and Studio are now Ready for Citrix. This is an important step in our final goal of becoming Certified by Citrix, and coupled with the scalability improvements we made in this release, we are sure you're gonna love it. To view all the Citrix environments that UiPath has proven compatibility with at a glance, visit this page.
In an effort to enhance agility in developing automations and process execution, Studio now brings dependencies per project. Compared to previous versions, activity packages can now be installed for each project specifically, making it easier to control the usage of your automation. Dependencies thus become highly contextual and specific to each project. As a result, upon creating a new project in Studio, the activity packages that are actually needed for workflows can be added from the Manage Packages window. Optionally, you can add any other pack.
Because activity packages have multiple versions, Runtime Rules were set in place, to select which version to use at design or execution time. For more information on these rules, please take a look at the documentation.
The Core Activities Package is now split into two distinct packs: UIAutomation and System. The first contains all the activities that mimic human interaction, such as Click or Type Into, while the latter sums up all the blocks required for building an automation, from invoking another workflow to logging a custom message in Orchestrator.
This change was made so that both in present and future versions, you can reference any version of the UIAutomation and System packages as dependencies for your projects, completely independent of Studio. This is a step forward for being able to update UiPath Platform components without worrying about how they affect your automations. For more information, check the documentation.
As part of the Studio UI and functionality upgrade, the Package Manager now shows the list of dependencies linked to the current project. The Package Manager window offers a seamless navigation among custom and UiPath official feeds. More details are available here.
Extensibility
To increase productivity and improve interoperability, Studio now allows for creating and publishing reusable components in the form of a library. Specifically, such projects can now be published as a .nupkg package, which can then be used as an activity in multiple processes. A Library has its own editable version number and Release Notes, and can be published to Orchestrator, a custom feed or the local machine. More details are available here.
In Orchestrator, this implies a centralized location where libraries are stored with the purpose of being further used and shared across tenants and teams effortlessly. Library management - upload and download - is done at host level from the Libraries page with the click of a button. For more information, click here.
Release notes added to better keep track of changes made in-between package versions are available in Orchestrator, both at library and package levels. For more information, click here.
We have exposed the input and output arguments you are already used to in Studio, as a way to seamlessly integrate the tools you use, such as various DCMs or BPMs. This means that any process you create can now receive input parameters through the Orchestrator API or interface, as well as return an output to all of the aforementioned. Last but not least, this is a stepping stone in linking processes together. This extensibility helps you better integrate UiPath in your company’s ecosystem. For more information, please see the documentation.
Being one of the most used programming languages, we have now integrated Java into our product in the form of some new activities. This new addition to our ever-growing pool of languages enables you to invoke your already existing Java code directly from UiPath. The Java Activities Pack features six new activities and a proprietary variable, JavaObject, that help you harness the full power of Java into your automation projects. You can find out more about this package here.
Scalability
The feature you’ve all been waiting for has arrived - Attended Floating Robots support! Create and configure your own Attended Floating Robots and connect to them from any defined machine in the blink of an eye. Since the machine name is not relevant for the Floating Robots scenario, we created a type of entity that fits the new requirements, the Machine Template. A template enables an AD user to use any machine, as long as the Robot uses the key generated at the template level and the aforementioned username. This scenario goes hand in hand with Non-Persistent VDIs, thus ensuring overall better resource management. On top of that, templates do wonders for hotseat environments, so people working in shifts on the same computer have a smoother than ever experience.
To make things even better, a Floating Robot connects automatically to Orchestrator when you open the Robot tray. For more information, click here
In order to make it easier for you to keep track of your Robots and Machines, the Robots’ versions are now displayed on the Machines page.
We’ve also made it possible to distribute and reallocate licenses to your tenants with just a few clicks and without the hassle of contacting our support team. The new process consists in uploading a single license file which aggregates multiple Robot licenses, which can then be allocated from a centralized location according to your requirements without any other additional steps or unnecessary delays. For more information, click here.
To facilitate license usage monitoring, we have brought to you the possibility to check historical licensing data. The historical graph in question is available on the License page, both at host and tenant level, and it shows the maximum number of licenses used concurrently by each type of Robot. This way, you can easily assess if there’s room for maximizing license efficiency or not. You can also filter out data or adjust the time interval as desired. Last but not least, you can now configure permissions per user for the License page. For more information on how to do that, click here.
As a way to maximize your results in terms of Robot utilization, we made it possible to add jobs to environments. This means that a job from the environment is automatically assigned to any available Robot instead of being placed into the queue of busy Robots. For more information on how to do that, click here.
Agility
The moment is finally here - the entire UiPath Platform has been localized, so that you can have a truly immersive experience, from install to design and execution. Now, besides English, you can access everything, including our online documentation, in Japanese.
If you worry about your long-run schedules during public holidays, weekends or any other day on which normal business is not transacted, we’ve got you covered. You are now able to define a list of non-business days on which schedules do not run. For more information about this functionality and how to use it, click here.
On top of that, to further improve scheduling flexibility, you are able to set a date and time on which schedules get automatically disabled. For more information about this functionality and how to use it, click here.
The efficiency of workflow debugging has been improved! The debugger now stops before executing the activity, and the behavior of Step Into and Step Over has been improved. In addition to this, breakpoints can be toggled from the activity context menu. For more information, click here.
This release also brings a better user experience and more reliable integration with version control systems. The new Team tab in the Studio Backstage View hosts the tools for connecting to SVN and TFS version control systems, making it easier to add, check in and check out the latest project version from the repository. For more information on how to do that, check the documentation.
Office Integration
Excel is one of the most common data manipulation software, and one of our main focuses in this release is increasing the power you have upon it in UiPath. This brings a major update to the Excel Activities Package, which features 14 new activities. Below you can find some of the most requested ones:
Copy Paste Range - Copies an entire range, including values, formulas, table format, and cell format, and pastes it to a specified sheet.
Insert/Delete Rows - Adds or removes a specified number of rows at a certain position.
Auto Fill Range - Takes the formulas defined in the rule range and adapts them to the end range, mimicking the Autofill functionality in Excel.
Delete Range - Deletes a specified range in an Excel workbook. Can also be used to shift an entire row or column.
Copy Sheet - Copies a sheet from a specified workbook and pastes it to another workbook. If no other workbook is specified, it is copied to the source file.
Create Table - Creates a table from a specified range.
LookUp Range - Searches in a specified range for the coordinates of a cell with a certain value and returns them as String variables.
Also, the new PreserveFormat property check box enables the Read Cell, Read Column, Read Row, and Read Range activities keep the formatting of cells they work with, whether it's currency, date, or anything else.
The ReadOnly property has been added to the Excel Application Scope activity, enabling data extraction operations on workbooks that are locked for editing or have an edit password.
This release rounds off the edges of the Word Activities Package by adding two new activities:
Replace Picture - Identifies all the occurrences of a given picture according to its Alt Text in a Word document and replaces them with another specified image.
Insert DataTable - Inserts a table generated from a DataTable variable in a Word document. The table is created at a position relative to a specified text or bookmark.
Last but not least, the Send Outlook Mail Message activity now supports sending dynamic attachments.
Attended Automation
With attended automation in mind, the new Custom Input activity helps you gather data from a user through a custom HTML input form at any point in the execution of a workflow and then use it later on. For more info, check the docs.
As another addition to the suite of attended automation feats, we have created the Block User Input activity, which can disable your mouse and keyboard during the execution of a UI Automation process, making sure the Robot execution is not affected by the user that supervises the automation.
Processes are easier to find thanks to the newly added search function. Furthermore, the Robot Tray has become more flexible, literally. It's possible to resize and drag the Tray window as you see fit.
The Robot Agent (Tray) status bar displays clearer messages for connectivity and licensing. These are displayed and are as follows:
Connected, licensed - when the Robot is connected and licensed. Congrats, you have it all!
Connected, Unlicensed - when the Robot is connected, but there are no available licenses for it.
Robot unavailable - when there is no registered Robot, or you don't have an active license, or a floating Robot is already in use on a different machine.
The UiPath Robot now makes it possible to switch between multiple Orchestrator instances upon connection. The Orchestrator URL and Machine Key fields save the info for more flexibility and faster connection to Orchestrator.
Community
In this section, we refer to activities that specifically concern our community. Please refer to our GitHub repo and feel free to contribute at this link.
GDPR has been our favorite pastime lately, so we understand the importance of securing operational data. The new Cryptography Activities Package comes to meet this necessity, by offering some activities that feature state-of-the-art encryption algorithms:
Encrypt Text - Encrypts a string with a key, based on a specified key encoding and algorithm.
Decrypt Text - Decrypts a string, based on a specified key encoding and algorithm.
Encrypt File - Encrypts a file with a key, based on a specified key encoding and algorithm.
Decrypt File - Decrypts a file, based on a specified key encoding and algorithm.
Hash Text - Hashes a string using a specified algorithm and encoding format.
Hash File - Hashes a file using a specified algorithm.
Hash Text With Key - Hashes a string with a key, using a specified algorithm and encoding format.
Hash File With Key - Hashes a file with a key, using a specified algorithm and encoding format.
Compatibility Matrix
The following table lists what version of Robot and Studio works with what version of Orchestrator.
Please note that by not upgrading to the latest available version you are not taking advantage of the newest features or bug fixes added in our releases.
Orchestrator v2018.3 Orchestrator v2018.2 Orchestrator v2018.1 Orchestrator v2017.1 Orchestrator v2016.2
Robot v2018.3 check_mark check_mark close-window-xxl close-window-xxl close-window-xxl
Robot v2018.2 check_mark check_mark close-window-xxl close-window-xxl close-window-xxl
Robot v2018.1 check_mark check_mark check_mark close-window-xxl close-window-xxl
Robot v2017.1 check_mark check_mark check_mark check_mark check_mark
Robot v2016.2 close-window-xxl close-window-xxl close-window-xxl check_mark check_mark
Improvements
Selectors
Several improvements are also implemented for selectors and the UI Explorer. Selector Editor and UI Explorer now have enhanced functionality regarding Partial Selectors, as the current validation state of the selector is displayed. Selector Editor also comes both with a feature for highlighting a selected element and a Repair functionality for building more reliable selectors. For more information on these rules, please take a look at the documentation.
Robot in User Mode
Robots use the same key on a machine, so it's important to know the status of each Robot, and not just as a whole. Checking whether or not your Robots are alive and when is a must. As a result, the heartbeat is sent from each Robot, individually, even in High-Density environments. This also applies to Robots that are installed in user mode - not as a service. More details can be found in the online documentation.
Security
Because we know agility and security are key factors in providing a high quality product, we have made it possible for you to set an external feed for packages and custom activities. The feed can be secured either by defining basic authentication credentials or by using an API key. Choose and configure the option that suits you on the Deployment tab. For more information, click here.
In our neverending quest of having the most secure RPA platform out there, we made it easier to enable SSL encrypted connections between Orchestrator nodes and Redis. We changed the server, port, and password settings required in the web.config file to LoadBalancer.Redis.ConnectionString. If you're updating your Orchestrator to v2018.3, rest assured, we're going to take care of the conversion automatically.
Extensions
As we know that some of you work in offline and highly controlled environments, we have added several improvements on how to deal with your Chrome extension installation. You can choose to set it up directly through the UiPath installer and you no longer need Internet access for it. The extension can be installed per machine or per user, and it is possible to also uninstall it from the command line. Please note that this is now distributed with the Studio/Robot installer. For more information, be sure to check the online documentation.
Java driver installations are now kept track of, so that each automation process running on that machine uses its appropriate Java version. The ScreenScrapeJavaSupport tool might help you more with your Java installations.
Activities
This release features a new activity called Join Data Tables, which extends our datatable manipulation arsenal. It enables you to combine columns from two tables by using values common to each other.
The Build Data Table activity has been revamped, offering a better overall user experience. You can now edit and restructure columns while using the Build Data Table wizard.
For easier utilization, the For Each and For Each Row activities now have a new property, called Index, which automatically counts the number of iterations the activity has passed through.
We understood your need for supporting machine learning models, so we have improved the Python Activities pack, adding support for Python x64.
The Key property of the Send Hotkey activity can now receive variables as input. This enables you to create variables for frequently used commands and simply add them to this property field, instead of rewriting the hotkey combination as a string each time the activity was used in the process.
To help you maximize the utilization of queue item information, we now provide the possibility to use the .Output, .DueDate, .DeferDate, and .RetryNo properties with the UiPath.Core.QueueItem variable in Studio. Consequently, you can add this data to a project's logic, for example, or use it to add more verification steps. Please note that the .Output property works only for successful transactions.
Alerts
For a better user experience and in order to help you prevent the potential cluttering of Orchestrator, several alerts having Success and Info severities are no longer generated. At the same time, you now have the possibility to choose whether or not to receive alerts for specific categories. For more information, click here.
Installation and Update
The minimum .NET Framework version required to install the Robot, Studio and Orchestrator has been increased to 4.6.1.
To help you streamline the automatic deployment of the UiPath ecosystem on as many machines as you want, the UiPath Platform Windows Installer has been split in two: the first (UiPathStudio.msi) enables you to install and update Studio and/or Robot, while the other (UiPathOrchestrator.msi) deals with Orchestrator.
For those that still prefer the all-in-one approach, we did not forget about you: an executable file, UiPathPlatformInstaller.exe, bundles Studio, Robot, and Orchestrator, with all the options of both setups. More info about these installers is available here.
The Orchestrator Windows installer now checks if URL Rewrite is installed or not on the machine, to ensure that you have everything you need from the get-go. In addition, the Orchestrator Windows installer now also stops the IIS website when you update your Orchestrator instance, to avoid any requests that might be made during the installation process.
Another important enhancement that was brought to the Orchestrator setup is that all your configurations are retained, including the custom ones, if you update your instance to v2018.3.0. This allows for an easy, fast, and seamless transition. To read about all these changes, check out the installation and update topics.
Last but not least, for a performance boost in regards to large-scale deployments, please note that in multi-node installations of Orchestrator, the script automatically sets the session state to the same Redis instance used for caching. More information is available here.
User Experience and Performance
As it was a widely well-received feature, we now further extend the offline support for Robots to all types. This means that any Robot can now retain its license for a custom number of hours, keeping any possible downtime to a minimum. For more information on how to use it, please check the online documentation.
Packing a project can be done from the Robot CLI. The -pack command bundles the target project inside a .nupkg file which enables you to easily share your automation across continuous integration pipelines.
An UnknownType variable is now added to replace variables or arguments that might become undefined as a result of package removal or upgrade. This way, workflows with variables of missing types can be opened and edited in Studio. You can read more about this in our online documentation.
For a better handle of large scale Robot deployments in Orchestrator, we made it possible for you to customize how often the Robot and Orchestrator communicate. To read more, you can access this documentation page. Please note that you can make use of this functionality only with v2018.2.6 or v2018.3.1 Robots.
In order to have a better, ready to hand overview of your Orchestrator statistics, we made it possible for you to see the data behind each pie-chart component on the Dashboard by displaying their corresponding pages filtered accordingly. For example, if on the Robots chart, you click the slice corresponding to Disconnected Robots, the displayed Robots page has the Disconnected State filter automatically applied.
By using Connection String, you are now able to connect Robots provisioned on machines from any domain or subdomain to Orchestrator 2018.3. For more information, click here.
As a host administrator, you are now able to add custom HTML content to the Login page. The content is displayed right above the Login section. For more information, click here.
The Type column has been removed from the Environments page in order to avoid unnecessary ambiguity.
For the detail-oriented you, we made sure that exporting transaction items now also includes the Output and Exception Reason of each item.
In order to increase usability and ensure an easier management of existing users, the Units column is now displayed on the Users page if Organization Units are enabled.
To prevent confusion, the Runtime tab on the Add Robot window has been renamed to Settings.
The manner in which audit data is displayed has been improved to help you get all the info you need at a glance. Moreover, unnecessary details can be collapsed.
For an enhanced debugging experience and a more relevant categorization of logs, all error messages regarding business and validation rules are now displayed under a new event source, in Event Viewer, BusinessException, at Info level. For more information, check out the documentation.
Whenever a user is assigned to review an item, he receives an Info severity alert.
Server exceptions from Orchestrator, and the stack trace on the Job Details window, are logged and displayed in English, regardless of what language was chosen by the user.
To help you prevent potential cluttering of Orchestrator, you are now able to disable execution or debugging logs sent from Studio during development processes.
To keep things simple and avoid eventual confusion, the concept of environment type has been removed and is no longer displayed in the user interface. Rest assured, backward compatibility is still maintained as this option was not removed from the Orchestrator API. More information can be found here.
To avoid issues related to publishing processes, project names can no longer contain special characters.
API
Error handling is an important part in RPA, and as a result, we added error codes to each custom exception returned by the Orchestrator API.
Performance has been improved by implementing a bulk deletion feature which helps you remove a large number of robots without unnecessary delays. This has been implemented by adding a new endpoint, /Robots/UiPath.Server.Configuration.OData.DeleteBulk, in the Orchestrator API. You can find an example here.
To help you easily identify which Robots can execute a specific process, a new endpoint, /odata/Robots/UiPath.Server.Configuration.OData.GetRobotsForProcess, has been added to the Orchestrator API. An example of how you can make such a request is provided in the API guide.
Furthermore, it is now simpler to retrieve Per Robot assets, by using the new GetRobotAssetByRobotId endpoint. You can see an example request here.
Updating your password is now also possible through the /odata/Users/UiPath.Server.Configuration.OData.UpdatePassword endpoint, if you provide your credentials, as described in this example.
The GetRobotMappings and GetAssociatedProcesses endpoints have been deprecated. In their place, you can now use /api/RobotsService/StartService, and respectively /api/RobotsService/GetProcesses.

UiPath Studio Community Changelog

What's new in UiPath Studio Community 22.10.5

New in UiPath Studio Community 22.10.4 (Dec 7, 2022)

New in UiPath Studio Community 22.10.3 (Oct 31, 2022)

New in UiPath Studio Community 22.4.4 (Aug 3, 2022)

New in UiPath Studio Community 2020.10.4 Beta 0001 (Jan 27, 2021)

New in UiPath Studio Community 2020.4.1 (May 14, 2020)

New in UiPath Studio Community 2020.4.0 (Apr 8, 2020)

New in UiPath Studio Community 2019.1.0 (Feb 6, 2019)

New in UiPath Studio Community 2018.4.3 (Jan 22, 2019)

New in UiPath Studio Community 2018.4.1 (Dec 13, 2018)

New in UiPath Studio Community 2018.3.3 (Nov 21, 2018)

New in UiPath Studio Community 2018.3.2 (Nov 1, 2018)

New in UiPath Studio Community 2018.3.1 (Oct 23, 2018)

New in UiPath Studio Community 2018.2.6 (Oct 18, 2018)

New in UiPath Studio Community 2018.2.4 (Sep 13, 2018)

New in UiPath Studio Community 2018.2.3 (Sep 4, 2018)