Release date: 12 December 2018
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. If this raises your interest, get all the details from here.
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. For more information, click here.
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. More details are available here.
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. Check out more details about the Global Exception Handler here.
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. For the Dark Theme to work, automation projects must have as a dependency at minimum
UiPath.UIAutomation.Activities v18.4.2 and
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 whichever one you want. Get a glimpse of the repository browser in the documentation.
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. Read more about it here.
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. Find more information here.
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.
- Microsoft.Activities v.1.0.1 and Microsoft.Activities.Extensions v22.214.171.124 are no longer packaged in the
UiPathStudio.msiinstaller. More information about this is available in the here.
- Launching the Community Edition Studio
UiPathStudio.exeinstaller while another such installer is running, results in corrupt installation.
- When copying activities in the Designer panel from one flowchart into another, the order is not maintained. This does not occur for activities copied from one sequence to another.
- When creating a new library from a template, the Designer panel doesn’t automatically open the
.xamlfile, unless the library template has a
- Due to the experimental nature of Dark Theme, some tooltips, error messages, notifications and buttons in Studio are displayed in Classic Theme after the switch.
- After updating Studio Community Edition
UiPathStudio.exe, it is recommended to close the
UiPath.Agent.exebefore opening Studio.
- Fixes were brought to autocomplete functionality for variables and arguments part of automation projects.
- Fixed an issue that caused Studio to become unresponsive for a short period of time after typing a network path in the location field part of the New Blank Process and New Blank Library windows.
- Fixed an issue that prevented files versioned under TFS version control system from being deleted if they contained pending changes.
- Files located in paths with restricted access permissions can now be opened in Studio in read-only mode.
- Fixed an issue that caused the Designer panel to throw an error when opening workflows with names containing double-byte chars and arguments with default value.
- The Expression Editor no longer truncates and hides the inputted condition if written on multiple lines of text.
- Fixed an issue that prevented processes and libraries without descriptions from being published from Studio.
- Variables of type
System.Windows.Forms.Integrationare now properly imported and used in automation projects.
- Validation error occurred when adding an activity resulted from a library project which imported workflows that were created in a version prior to v2018.3 and used
- Fixed an issue that caused Studio to freeze or improperly display certain controls after being left idle for a while on a remote desktop machine.
- Projects created in Studio v2018.2 and saved on shared drives, could not be migrated and opened in v2018.3.
- Keyboard shortcut CTRL+Tab didn't switch between active workflows if the focus was inside the Designer panel.
- In some cases, DiagTool would generate inconsistent or empty report files.
- Validation error occurred in some cases when the type of variable was modified in the Variables panel.
- In the project folder, renaming a workflow and deleting the
project.jsonfile would result in a second
Main.xamlfile being generated when the workflow was opened in Studio.
- If you updated your Studio and Chrome extension while the browser was opened, an error was displayed.
- Solved an issue that caused a workflow validation error of automatically imported namespaces when copying VB expressions into activity input fields.
Updated about a month ago