It would be nice if OutSystems would create a section in their Learn site to include a list of learn content (blogs, videos) created by non-OutSystems staff or OutSystems partners.See this post of a lot of training material on Reactive web and other topics: https://www.outsystems.com/forums/discussion/57112/a-series-of-tutorials-on-reactive-web-apps/

Hi,Service Studio could help our developers in maintainability/architecture tasks doing an analysis on all "Unused public objects". This option could be something like "Remove Unused Dependencies" but could check all objects that don't have usage in other modules.+ will allow developers keep applications smaller, delete unused features+ spare a lot of time, because this tasks is manually our days+ already have a manual task for that, so Outsystems will only automate, no extra work needed

Currently, OutSystems allows exporting the BPT Process Flow as an image, which is very useful for documentation and communication. However, this export only shows the high-level activities and does not include the logic implemented inside each activity. Adding the ability to export the internal logic of BPT Activities as an image would complement the existing Process Flow export, allowing developers to capture both the high-level process view and the detailed activity implementation.

Service Studio and Service Center should show the Forge application version.If I install an application from Forge, the version should be visible in Service Studio and Service Center. This way we can easilly compare the version we have installed with the latest versions from Forge.In Service Studio it could be visible in the apllication screen (see attached print screen)

Hi,I think it is interesting that Integration Studio saved passwords for connecting to the environment, just like in Service Studio.Or to make it easier, Integration Studio uses the same foundation as environments already saved in Service Studio (environment, user and password).

I very much like the feature of automatically connecting to an environment, but more often than I would like to admit I find myself doing changes in an environment where I do not intend to. This is partly because the environment that is opened doesn't stand out that much.When opening (for example) a TST environment, the next time you open service studio, the TST environment will be opened (instead of the DEV environment, which was opened earlier).I see two options that might prevent this.1. Enable configuration per environment (in 'Manage environments' to enable/disable automatically connecting to that environment). You would probably want this for all non-dev environments anyway.2. Set a fixed environment to automatically connect to, instead of the last environment. I think it's true for a lot of developers that 95% of their work done is in one environment.

New Accessibility category in Ideas and new Accessibilty tag in Forums. It may be that this was decided internally as not necessary, but with accessibility becoming a must, and since it's a very broad topic, I feel that a dedicated category and tag in the Ideas and Forums, respectively, would benefit and facilitate the search for this topic.

While in Debug Mode, have the chance of setting the Execution to step-back in the flow. Along with this Idea  debugging will be quicker.

In some situations the platform should auto refresh espaces and publish them (if possible).Scenario:Public Entities consumed by several espaces.There's the need to add a new column or record for static entities.Consumers will be outdated/broken.When the espace with the change is published which has consumers, should check if its possible to auto-refresh the consumer, and if so refresh it and publish it automatically.By the way it would be nice to have more filters on Espaces List in SC.

As confirmed by OutSystems in this forum topic , data fetch actions are not optimized and instead passing all screen data in every request payload. Even if the parameters are not used anywhere in the data action. Please optimize this.