Until now, I was using ‘UiPath.System.Activities’ v25.10.2 and utilizing the “Use Application/Browser” activity.
At that time, I was specifying the selector to select the window. By clicking the part of the image labeled “Specify the application to automate,” I was able to make the selection.
After updating ‘UiPath.System.Activities’ to v25.10.32, I can no longer perform the equivalent selection task. How can I select the selector as before by clicking on it?
I think that is quite possible. (Although I can’t say for sure without trying.)
Another perspective could be that if there’s no pressing need to update the UiAutomation package, you may consider continuing to use the stable version.
Thank you very much.
I have been switching to a higher version for packages that have been around for about six months to ten months, but since there is no particular need to upgrade, I am thinking of reverting to v25.10.2 for the time being.
I am not particularly tracking which version is stable, so I am just using versions that catch my eye.
I feel that frequently upgrading can cause significant differences in usability across projects, making it difficult to manage.
Generally, how often should one reconsider the version of a package?
There are various ways of thinking about it, but changing the version of the activity package can affect the behavior of the activities, which means testing will be necessary. Therefore, unless it’s absolutely necessary, many tend to leave the activity package version unchanged.
Additionally, the support for activity packages in each version of Studio is as follows. For the 24.10 series, you should upgrade Studio to the latest minor version of 24.10 and use the versions of activity packages listed on this page to be covered by UiPath’s support. Conversely, the System.Activities package 25.12.2 in the screenshot is part of the STS product bundle, so if you prioritize stable operation and support, it’s better not to use it.