Solutions Management Release Notes Guide
February 2024
We're excited to announce that Solutions Management is now Generally Available (GA). We thank all preview users for their valuable feedback and encourage you to start exploring the enhanced capabilities this new release brings.
The before
A solution is a collection of components built and configured on the UiPath platform that function together to automate a business case. In the UiPath world, a solution can be anything ranging from a Studio workflow to a combination of workflows or processes, assets, quesues, ML Skills, and more.
While you know that all these independent pieces that work together form your solution, there is no built-in option to define them as a unitary artifact that you can easily manage; and this is exactly where Solutions Management comes into play.
The after
As you can see, we were no strangers to the concept of a solution before. However, what Solutions Management now brings to the table is the possibility of handling all these components in a standardized manner.
To put it briefly, you now have an out-of-the-box means to manage the lifecycle of your solutions. The process of transferring solutions between environments, deploying them, and applying environment-specific configuration is significantly easier now that the new set of platform capabilities help you bundle everything together.
How do I start?
https://cloud.uipath.com/{orgName}/solutions_. It is there where you can start creating and configuring solution packages so that you can subsequently transport them from
one environment to another.
However, to make the most of its potential, we strongly recommend taking a moment to explore the Solutions Management User Guide. The documentation will be your go-to tool whenever you want to dive into topics such as prerequisites, solution package configuration or deployment, transport, etc.
-
We have fixed an issue preventing you from deploying a package that includes certain components with a shared dependency in another folder.
-
You can now upgrade packages that contain action catalogs.
-
Previously, when editing a solution package to create a new version, in order to fetch the latest updates form the source environment for a certain solution component, you had to remove and re-add that component. You can now use the sync functionality for this purpose.
-
We have fixed an issue causing older automation package versions not to be removed from the target environment at upgrade.
-
When creating a new solution version, if you removed a component and replaced it with one of the same type and with the same name, a conflict occured and caused the upgrade to fail. This behavior no longer occurs.
-
If you upgrade a solution that had an asset with robot asset values configured post-deployment, the robot asset values are deleted and must be re-entered.
-
Upgrading triggers that reference calendars will fail at deployment.
-
The deployment fails when a new bucket, having the same name as an existing one, is placed into the solution folder. This results in a naming conflict.
-
The solution deployment is unsuccessful, and validation errors are seen for triggers when arguments are inherited from the process.
Your draft solutions are becoming solution projects. A project serves as a container for the solution state prior to being published and can be used ongoingly to publish newer solution versions. Projects are bound to your source tenant where you create the solution.
Building a new project involves adding new components and adjusting the component properties as necessary. In addition to that, you also have the option to include automation packages and libraries in your projects.
In terms of project development, you should know that you can edit projects and create new versions. For details, see Creating a solution project and Editing a published solution project.
Wondering how solution projects fit into the broader scheme? Once you build a solution project, you can publish it to obtain a a new solution package, ready for deployment when required.
We have brought in support for libraries. You can now upload and incorporate them into your solutions easily.
You can now monitor your package deployment history. To access this feature, navigate to the Deployments tab and select the three-dot button corresponding to an operation you are interested in. Choose Deployment history to view all executed operations for that package along with other details, such as version, status, and author.
Moreover, when making changes to a project, you can now monitor its publish history. While editing the project, you will see a Publish history button in the upper-right corner of the Solutions builder. Selecting this button reveals a panel that outlines details on each version of the project, including timestamps and author. You also have the option to download each version.
When creating or modifying a project, you can now select all component in a folder with just one click.
Aside from that, you may want to know that the process of adding adding multiple components to a project happens in the background.
Last but not least, you can now lock component properties that you do not want altered by others. To do this, while creating or editing a project, navigate to the component whose property you wish to lock, and then select the icon next to it.
