Package versions

Help Studio
, ,
1

Hi,
If I build a process in Studio version 2022.10 with package versions available in Studio 2020.10, will the process be compatible when run in Studio2010? Or because the Studio version is different, does it inroduce any issues?
Thank you so much,

Forum Engagement Daily Reports
2

@A_Learner,

You will have to upgrade/downgrade the package versions as per dependencies and their compatibility.

Thanks,
Ashok :slight_smile:

3

Hi @A_Learner

Before starting to develop your process, make sure to keep the dependencies in the Latest version and Runtime Rule as Lowest As Applicable.

This will not give you package version issues.

Regards

4

Thank you, Can you please provide more details?

Thank you,

5

Hi @A_Learner ,

Could you check the compatibility section in the below post:

I believe it is mentioned that Backward compatibility is supported but not forward compatibility. It would mean we can develop in 2022 version and use it in 2023 but developing in 2023 version and deploying in 2022 Robots/Studio might not always work directly.

1 Like
6

@A_Learner,

In Studio 22.10 update all packages to to Lowest Applicable version. Then Compile the code.

image
image1132Ă—632 63.6 KB

Transfer to lower version and check if any errors.

Thanks,
Ashok :slight_smile:

7

Pay attention to the package description when you’re in the Manage Packages window. It tells you the Studio version needed.

Also, you’re using ANCIENT versions of Studio. Why?

8

That’s not what that setting does. That setting means when there are multiple dependencies that have the same sub-dependency, it will use the sub-dependency version that is lowest.

  • Some Package
    • A Sub Package v1.0
  • Another Package
    • A Sub Package v1.2

Assuming “A Sub Package” is defined in both “Some Package” and “Another Package” as “lowest applicable version” then the automation will use v1.0.

9

@postwick

Thank you. Using the Studio version that is allowed.

Please clarify the following. I am trying to build a process in 2022 with package versions that were working with 2010. When I install this process for a user who has 2010, will it work?

Though I plan to build with 2010 compatible versions, I am concerned that the my Studio version is 2022, if that introduces any issues.

Thank you so much,

10

It could cause issues. You should all be on the same version. And you all shouldn’t be on ancient versions.

1 Like
11

When the package versions are matched would there be a compatibility issue from Studio version to Studio?

Thank you,

12

@A_Learner ,

Even though the package versions are matched, there could be issues as the updated Studio version may have additional capabilities which would not be suitable for the lower version studio and it could cause in missing imports, or activity not able to be reproduced or have design issues.

Some cases it might work but it would mean that it is very close to the studio versions used.

And I am not very sure if there is a 2010 version available at all. Did you mean 2020.10 ?

1 Like
13

Yes I meant 2010.10 and the version I am trying to mimick 2010.10 is 2022.10.3

Thank you,

14

Overview - Compatibility Matrix

1 Like
15

So looking at compatibility matrix, 2022.10.3 is compatible with 2020.10.3, 4

I notice that I need 2020.10.6 to be compatible with 2022.10.3

Would that be an issue?

Thank you.

16

If it says you need that version, and you don’t have that version, then yes it will be an issue. That’s why it says that.

The real question is why don’t you just upgrade?

17

It is the version that is allowed.

Thank you, appreciate all the input.

18

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