UiPath activity version

We want to upgrade our 50+ BOTs to latest UiPath dependencies. We generally open each and every project, update the dependencies, test the chnages and deploy the new package. But doing this everytime we have a new upgrade is not feasible. Just wanted to check if there is any other alternate way to perform this upgrade , where no code change or testing is needed post upgradation. activities @uipatth

You can utilize the Mass Update Tool Available in the tool section of UiPath Studio.

To access it, navigate to Studio > Home > Tools > Project Dependencies Mass Update Tool.

I think there isn’t any way to bulk upgrade the dependencies and testing the bots. You’ve to do it manually. But if there is team to do soo then the efforts will be divided.

@bhavesh.choubey We can update the Project Dependencies of multiple projects using Mass Update tool.
Yes, for purpose of testing we have to test the processes individually.

1 Like

Okay didn’t aware of this. Thanks cheers

1 Like

Hi @pallavi.seth

You can try with Mass Update Tool
Note-project dependencies Mass Update Tool is available starting with Studio v2018.4.4.

Thanks all for your reply on this topic.
We can explore mass updation tool for the process upgradation purpose and can save some manual effort on this task. But the entire cycle of upgrading the processes, code commits, SIT tenant deployment , testing and finally live deployments take a lot of efforts. I was wondering if there is any other way to minimize the rest of the efforts as well. Thanks in advance.

Nope you have to test, upgrade your process manually because you or your team made the bot so it should be validated by you or your team for no error and successfull execution.

Cheers

1 Like

Hi @pallavi.seth
As per my knowledge , you have to test all the process before deploy to prod.
@marian.platonov Any other alternate suggestion ?

You are correct. For every upgrade (package, robot, Orchestrator, etc.), you need to test before deploying to Dev, QA or Prod.

1 Like

Thanks for the clarification.
@pallavi.seth you have to do same.

Happy Automation :blush:

Thank you for your inputs. Really appreciate. We will follow the manual upgrade and test approach as Git, CI/CD, PR approval and other processes are also involved in the dev work. So will follow the standard process only. Thanks.

2 Likes

Happy to help. Thanks!

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.