How to update the process and use the same version?

Help Orchestrator
,
1

We are using 2022.10 version. If we replaced the new xaml into installated package location (with new code instead of republishing again) then that new code is not reflecting during the process execution.

Job is taking previous xamls which are originally downloaded from /.nuget/packages.

Kindly help to find a way to replace the xamls with new code instead of republishing.

2

do you mean, you want to replace files for process which is running on orchestrator while republishing new package ?

3

I have a process called “ABC” published to production Orchestrator with version as 1.0.1. Now, I want to remove message box activity from Mail.xaml.

I do not want to publish new version again to production just to remove message box. I can update the already published version xamls to remove message box from Main.xaml ?

If I replace mail xaml in 2020.10 version, it worked but it is not working in 2022.10 version.

4

Got it, there can be chances for package version mismatch , try to update project.json also with updated version. As there are quite updates happened in 22.

5

You need to perform these in case you have the source code (xaml file):

  1. Download the nupkg file from Orchestrator and extract it on the Studio 2022.10.x machine or open the project directly in Studio if you have the source code already.

  2. Remove the Message box from the xaml.

  3. Close any Studio instances.

  4. Open the project.json of the impacted process and modify the projectVersion to a lowerversion than the one from Orchestrator.

  5. Now open the project in Studio, check if everything is working.

  6. Go to Orchestrator and delete the old version (the package version should be in inactive state, basically to not be in any folders in Orchestrator).

  7. In Studio, publish the process.

  8. Now you will need to delete the old installed process folder from the robot .nuget\packages root folder location from all the robot machines that already installed it.

  9. At the next run, the robot will install the same version of the process but without the message box.

In conclusion, this is a not good practice , as it will create more difficulties for you to find the root cause why a process is not taking the latest changes even if you published to Orchestrator. Better, modify the xaml with your automation update in Studio and publish a new version instead of using the same version. Also, in the release notes of the process you can mention what was actually modified.

I hope that this helps you.

6

thank you. I’ll try this.

7

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