Refresh your dependencies without having to open all sorts of panels (very time consuming). Bonus: You can also see when code has changed :)As a addon on: https://www.outsystems.com/ideas/6095/refresh-all-dependencies-in-service-studio-menu

On Service Studio, it would be nice to have an icon indicating if there are modules inside the applications that are broken (with errors).For instance, I've updated a component and after that there are 2 apps with broken eSpaces, but in my Service Studio list view of the apps I don't have a way to see it. I need to go into Service Center and go to the eSpaces' list, filter by the ones with errors, check the application and open on Service Studio to refresh the dependencies and publish (jumping in two different "windows" just to clear the errors).

If we can see who and when have done the eSpace last published in Manage Dependencies window at footer, it would be very useful to manage the refresh.Sample in attachment.

Guys,If the "Manage Dependencies" window only shows the used dependencies by default, It would be more time saving when I just want to refresh dependencies that I already have.Even with the performance revision you made recently on this screen.  On a recent dev environment it takes sometimes 2-5 sec do show ALL modules I have, to create new dependencies, and almost all the time I just want to refresh the ones I already have.I know that there is a button to strict the collection, BUT the data was already loaded and the time has already taken.Please consider this.

There might be a button to update the dependencies if any.

Solutions are great way to refresh dependencies and to deploy to another environment, and on our project we use them often. But maintaining them is not easy. I think some improvements would be great:1. Possibility to clone a solution - if you need to have another one with few components removed or added, but don't want to add everything from scratch.2. Possibility to associate many components at once. Ideally to have a list of all modules where you can check/uncheck them. This will be so much better than current auto-complete to add only one (with waiting for submit to reload the page).3. Automatic read-only solution with all user modules (no system components), which you can publish, create version and download as normal.

I think it will be amazing if LifeTime have the capability to auto refresh when we have our plan already built.Sometimes when i am building my plan to promote the code between environments and happens that some of the dependencies are outdated for some reason, there's no chance to auto refresh the already built plan.I need to open the outdated dependencies, correct the problems and then rebuild my plan all over again (and sometimes it becomes boring because we have a huge list of Applications).

Currently we have to refresh and republish manually to keep the sequence.  Automating that is going to be hard -there will sometimes be cyclic stuff, sometimes other things.But one idea was to have a place in service centre, like in a solution, that would go one step deeper.1 - define modules in this solution2 - order them in a specific sequence so that it makes sense going up the 4LC - especially where there are combinations.3 - execute - effectively automatically do the same as we do manually - open the module, refresh dependencies, apply, publish, move to next module4 - exceptions are fine to throw & cancel operation, should be able to communicate with the team directly when this is used.5- outcome should be that all producers / consumer warnings are handled.

Opening multiple modules on service studio or search for multiple modules in the Service Center to refresh the dependencies can be time consuming. It would be quite useful to have a tool to refresh all dependencies, next to the move module icon, in each module inside an application. Service studio is always open, and it doesn't log out for inactivity like Service Center. So, I believe it would be much quicker than login and search for the modules in the Service Center every time. They don't always show up on recent items, so I found searching for them as time consuming as opening every single module on Service Studio. The icon would be responsible to refresh the dependencies without publishing a new version.

When you change a record in a static entity and  forget to refresh the dependencies in a consuming eSpace, you don't get a warning like you do when a structure is changed.Because of that, it's easy to miss such a change and deploy an application with bugs. After deploying the exposing eSpace, you see a yellow/orange triangle next to the consuming eSpace, but if you don't refresh but just make another change in the eSpace, the warning is gone.I would like to see a waning in service studio and/or lifetime, when there are still some unrefreshed dependencies.In the OAP the dependencies of eSpace 'aaa' (sorry for the name) need to be refreshed, but service studio and lifetime don't show warnings.