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

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.

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).

like to see service studio having a inbuild animated icons like animated SVGs

here are the way if we want to create the pagination logic by the help of local varibles

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)

Currently, OutSystems UI provides built-in Open and Close actions for individual Tooltip components. However, if we review the Tooltip API implementation, we can see that there is also a GetAllTooltips method available. https://github.com/OutSystems/outsystems-ui/blob/53a8f0e/src/scripts/OutSystems/OSUI/Patterns/TooltipAPI.ts#L2 If you want to show all the tooltips in the screen you need to rely on a iteration and trigger the open tooltip action. Add the GetAllTooltips and ShowAllTooltips to the list of OutsystemsUI Actions.

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.

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.

This idea is a suggestion for OutSystems UI but also for an improvement on Service Studio. Add support for a dark theme in OutSystemsUI. This version of the theme would be similar to the viewport simulation approach, with classes in the body tag displaying which type of device the user has. The new classes would be "dark" and "light". Add a ThemeSwitcher Pattern to OutSystemsUI. This pattern would be responsible for managing the theme, keeping the user's preference in local storage/client variables. Add a dark theme simulation in Service Studio Again, similar to the viewport simulation that lets the developer see the page in 3 different screen sizes, there would be an option to see the page in dark or light mode. The dark theme is a great modern addition to any app, because it lets users choose which theme is best for their condition. Having it integrated both in OutSystemsUI and ServiceCenter would allow OutSystems developers to have an implementation of this feature that is both universal and officially suported.