New Application Version Notification and Update

I agree with this and I like the part of transforming the forge into a more dynamic market of apps.

For Forge modules/applications that have not been modified locally, the platform could regularly check whether the installed version corresponds to the latest stable version (or under development, if you want to add an extra option for that) or not, and display a visual cue that the module/application is outdated.

It would be great to see any indicator that installed components like Silk Mobile are updated and can be upgraded.

Its will allow to avoid fixing things that are already fixed in new version and do not manually check all components.

List of changes or quick link to component version history would be also great.

This Idea can be marked as duplicate of https://www.outsystems.com/ideas/2456/service-center-show-when-a-new-version-is-in-the-forge

CA

It would be useful for developers to get a notification during publishing or on open the app in studio that there are updated versions of the component that the are using from the forge.

Merging with a few other related ideas, the concept is the same.

J.Ja

A dashboard that - on one screen - shows what Forge components have newer versions released (compared to what is installed in an Environment), and ability to batch download (more than 1 at a time) as well as (maybe) installing that batch at once (maybe downloaded as Solution Pack?) into that Environment.

I guess it might be problematic, as it's a good practice to test everything before publishing. A new version can always contain bugs and crash something that used to work fine in your apps, don't you think?

Besides the fact that it would be a hard one for my environments since I split up most of the forge component since I don't need all the example screens/modules in my test/acpt/prod environments.

I don't know if batch download-install all forge components is a good one, most of the time their library components and it requires quite some republish of all the consumers and that can have quite some effect.

Have an "Upgrade" button/link available when we are inside of an application in Service Studio.

It's way faster and easy to understand instead of using the first tab that loads all the forge and I need to search for the component.

Right now it's not possible to see what version of an item is installed from the forge. Especially if you have changed such an item there is no way to tell anymore if there is a new version available.

An improvement would be to show in Service Studio and on LifeTime what version of an item from the forge is currently installed, so that it is easier to maintain extensions and keep track if there is an update for it.

Hi Paul,

I know this is quite annoying. I don't have the solution but in my most recent blog[1] you can find some tips how to manage your LifeTime to make it a little bit easier for yourself.

Kind regards,
Martijn Habraken

[1]: https://medium.com/@m.habraken/how-to-manage-your-life-time-f6c4e38f4e0e

The forum topic from where this idea was created from (gives some insight): https://www.outsystems.com/forums/discussion/30283/proper-way-to-update-a-module-from-the-forge

Kind regards,
Evert

Thanks, Evert!
@Paul I think that the replies of Eduardo & Evert in the original post already give you a pretty good idea about how to work around this problem. Maybe a little tip, when you have a changed forge component you can install the new version. However like already stated you will lose your changes, but with the merge functionality, you could easily merge your (old) changes and the changes of the Forge developers.  

Right now it's not possible to see what version of an item is installed from the forge. Especially if you have changed such an item there is no way to tell anymore if there is a new version available.

An improvement would be to show in Service Studio and on LifeTime what version of an item from the forge is currently installed, so that it is easier to maintain extensions and keep track if there is an update for it.

Hi Paul,

I know this is quite annoying. I don't have the solution but in my most recent blog[1] you can find some tips how to manage your LifeTime to make it a little bit easier for yourself.

Kind regards,
Martijn Habraken

[1]: https://medium.com/@m.habraken/how-to-manage-your-life-time-f6c4e38f4e0e

The forum topic from where this idea was created from (gives some insight): https://www.outsystems.com/forums/discussion/30283/proper-way-to-update-a-module-from-the-forge

Kind regards,
Evert

Thanks, Evert!
@Paul I think that the replies of Eduardo & Evert in the original post already give you a pretty good idea about how to work around this problem. Maybe a little tip, when you have a changed forge component you can install the new version. However like already stated you will lose your changes, but with the merge functionality, you could easily merge your (old) changes and the changes of the Forge developers.  

Right now it's not possible to see what version of an item is installed from the forge. Especially if you have changed such an item there is no way to tell anymore if there is a new version available.

An improvement would be to show in Service Studio and on LifeTime what version of an item from the forge is currently installed, so that it is easier to maintain extensions and keep track if there is an update for it.

Hi Paul,

I know this is quite annoying. I don't have the solution but in my most recent blog[1] you can find some tips how to manage your LifeTime to make it a little bit easier for yourself.

Kind regards,
Martijn Habraken

[1]: https://medium.com/@m.habraken/how-to-manage-your-life-time-f6c4e38f4e0e

The forum topic from where this idea was created from (gives some insight): https://www.outsystems.com/forums/discussion/30283/proper-way-to-update-a-module-from-the-forge

Kind regards,
Evert

Thanks, Evert!
@Paul I think that the replies of Eduardo & Evert in the original post already give you a pretty good idea about how to work around this problem. Maybe a little tip, when you have a changed forge component you can install the new version. However like already stated you will lose your changes, but with the merge functionality, you could easily merge your (old) changes and the changes of the Forge developers.  

Right now it's not possible to see what version of an item is installed from the forge. Especially if you have changed such an item there is no way to tell anymore if there is a new version available.

An improvement would be to show in Service Studio and on LifeTime what version of an item from the forge is currently installed, so that it is easier to maintain extensions and keep track if there is an update for it.

Hi Paul,

I know this is quite annoying. I don't have the solution but in my most recent blog[1] you can find some tips how to manage your LifeTime to make it a little bit easier for yourself.

Kind regards,
Martijn Habraken

[1]: https://medium.com/@m.habraken/how-to-manage-your-life-time-f6c4e38f4e0e

The forum topic from where this idea was created from (gives some insight): https://www.outsystems.com/forums/discussion/30283/proper-way-to-update-a-module-from-the-forge

Kind regards,
Evert

Thanks, Evert!
@Paul I think that the replies of Eduardo & Evert in the original post already give you a pretty good idea about how to work around this problem. Maybe a little tip, when you have a changed forge component you can install the new version. However like already stated you will lose your changes, but with the merge functionality, you could easily merge your (old) changes and the changes of the Forge developers.