We are a team of developers using the latest LTS Studio version and sharing our work using GIT.
Some of us are interested in the latest improvements that are announced in the STS version.
Are there any disadvantages that we may run into when moving to STS?
Any best practices you can share?
From the prospective of long time support from the product, LTS is always a good choice but as the UiPath Studio evolving at the highest speed, it’s tempting to test all the latest features.
@loginerror, please throw some light here on this not much explored topic.
1 Like
1 Like
For testing they may use it…there are chances something might break that is the reason new patches are released…so before doing the patch if the effected activity is used you might face errors which might effect…but if they want to try then can and bare in mind that if any ticket is raised as well then based on ticket as well new patches can be released and you would need to move again to newer patch so that the issue is fixed and you can continue exploring and work as well
cheers
1 Like
Is there a risk if we have a mixed setup?
Like some continue to use LTS while others move to STS? I am wondering if there is a chance to break the files that are used by all - like the project.json.
At least I assume that a STS script cannot be changed by a LTS developer.
1 Like
One point to take into account: You need your robots at same (or later) version than your Studio. Otherwise you may face issues with processes published from later Studio version not running under earlied robot. That is my experience confirmed by UiPath.
Cheers
2 Likes
for that you might need to first time create with LTS and use same project to avoid backward compatibility but forward should be there
Also yes the issue of developing on multiple versions also can be mostly addressed in this case of first time creating on lower version
as @J0ska the risk of different version would exist..specifically when the versions were 22.x and 23.x where major changes were done
cheers
1 Like