Hi there! Let’s cover another new improvement in the life of RPA devs. Today’s topic: proper publishing capabilities.
Remember the Publish button that would just automagically publish your process somewhere. You weren’t sure if it was on the Orchestrator or local folder or how did it come to the new version number. Now everything is much more transparent, but let’s start with the beginning:
The publish button was moved in the Design ribbon, where it is a better fit for it.
Let’s move forward and look at the new Publish window and what it can do
- You can now choose where to publish right from this window, without the need to connect/disconnect the robot. You can either publish your project (be it Process or Library) to the Orchestrator or to a custom feed or folder. If the robot is not connected to the Orchestrator, the default option will publish the package to the robot setting.
- When going for custom location publishing, you will be able to set the NuGet feed you want your package to be published or a folder where you usually store your processes. If the NuGet feed you chose requires authentication, you can pass your API key to it when publishing the package.
- Unfortunately, our memory is not always perfect and we may forget what changed between 1.2.6435.21107 and 1.2.6546.34563. That’s why we added release notes that will help you remember what you forgot about your releases. Those release notes will be visible in the Orchestrator under the Packages page
- Semantic versioning will now make sense. You can easily choose if your upgrade is Major, Minor or something else. Moreover, you will be able to patch your already updated process/library. E.g: you created a library for handling SAP login, and you reached already version 184.108.40.20678 but you find a bug in the version 220.127.116.1167 Now you can just release the 18.104.22.16878 version and use it without having to port every process from v1 to v2.
For the Library we have two more settings:
- Where the Library activities will be found inside the Activities Panel. You can choose any “folder” you want: System, User Events, Orchestrator, etc.
- By including the sources when publishing your Library, you will give others the ability to review your work. In the future, they will also be able to debug it while using it in another project. Be aware that this can mean everyone can see your source workflows including private ones.
Please note that a Library can only be published on Orchestrator from 2018.3.0 onwards.
This is about everything regarding the new publishing options. Let us hear your thoughts and remember to keep you release notes short and clean!