ODC Allow choosing library version to update
171
Views
4
Comments
New
Service Studio

Recently I had a problem when updating the OutSystemsUI library, the version I updated had a bug. As I continued development, I only later realized that there were some misbehaving components, and I soon suspected the OutSystems UI update. 

This way I had to go back several versions of my application, to get back to the last version of OutSystems UI, without any problems. 

This can happen with any library, and without more serious scenarios.

There doesn't need to be many versions available to choose from, I believe that between 3 and 5 would be enough.


LibrariesUpdate.png

Hi Johnes,

Maybe I don't understand your idea, but I selecting a specific (lastest or older version) of a library (like OutSystemsUI or any other library) is already a working feature in ODC since October 2023

for more more information:

Those the above information, cover your idea?

Regards,

Daniel

For example: My applications are consuming version 2.19.2 of OutSystems UI, but I want to consume version 2.19.1, how do I do that today?

Hi Johnes,

You are touching I think weak point in the improvements OutSystems made in handling library versions in applications.

  1. At one time your app was using maybe version 2.19.1.
  2. Then OutSystems installed 2.19.2 in your tenant, but your app, by design of ODC, is still using version 2.19.1.
  3. When you opened your app you got the following dialog, and updated to the version 2.19.2 of OutSystems UI.
  4. Then you decided, for whatever valid reason, you want to revert back to version 2.19.1.
    • This is were I think ODC can improve and provide a way of selecting an older version of a library app we consume, as currently that is not possible:
      • Provide a button on the History overview tab in the ODC portal, to select another version of a consumed library, or
      • On the Properties of the consumed library app in ODC Studio, make the Version property a dropdown, with all available versions to select from.

I already shared this feedback with OutSystems, and will keep you posted, if they have any intentions to improve this use case of reverting back to an older consumed library version.

As a workaround, for now the only way you can get back to consume an older version of a library app in your application, is by reverting back to the application version, before you updated OutSystems UI to 2.19.1.

  1. Open the app in ODC Studio
  2. In the menu App > Open other version...
  3. Select the version which still uses OutSystems UI 2.19.1
  4. Validate that the selected version has the correct version by inspecting the version property of OutSystems UI

Regards,

Daniel

That's right, Daniel. You managed to understand my point!

Thank you for your time and for sharing this with OutSystems.

Big hug!