Description : On the Asset Moderation History page, it would be extremely helpful to have Edit and Delete buttons for user comments. Currently, if a user accidentally submits a comment multiple times, such as due to button loading delays or double-clicks, there is no way to either delete the duplicate or update the text. Use Case Example : I recently experienced this issue where, due to a slight UI lag, I unintentionally clicked the "Comment" button twice in the Add Comment PopUp. The same comment was added twice to the moderation history. Unfortunately, I wasn't able to delete the extra comment or update it with corrected or different information. This can lead to confusion or clutter in the comment history. Proposed Solution : Add Edit and Delete buttons for each comment in the Asset Moderation History list. Ensure appropriate permissions or audit trail is maintained to preserve moderation integrity. This enhancement will improve user experience and data cleanliness in moderation workflows.

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.

Add the ability to the cloud infrastructure to block or allow specific IPs on an OutSystems cloud environment like the service aws is offering. See this link https://aws.amazon.com/premiumsupport/knowledge-center/ec2-block-or-allow-ips/ for more information.We now have to resort to building a custom ip filter, based on  HTTPRequestHandler_API getipWhich requires to build it into every application.Goal is to achieve a similar solution for reactive web and mobile applications as what is available for traditional web. See  Restrict Access to an Internal Network .

In Service Center, would be cool take the time elapsed on a publish, maybe it could be useful to know for another publish in another enviroment like Production and estimate some stoping time, for example.

After a while, in a big company, we have a lot of Roles and when we create a new page for only one or two roles, we have to uncheck dozens of checkbox to have the one we need.Can you guys put a select all/unselect all above the roles list in the properties panel of a Screen?Thx

We should be able to test connectivity between the environment (FE) and other endpoints using SC.In order to use this feature, we are required to install other forge components tool like "NetChecker"

You always have to use the Swap Connectors because True has to go down and False to the side for the exceptions.

Thanks for the Manage Environments option on Service Studio and the possibility to give a name/alias to the environment, to make it perfect I would I love to have the possibility to organize my environments by ordering them as it betters suits my needs so that they appear in the list of Switch Environment in the desired order. For some of us, it will make sense to order by customer and for others by type of environment (DEV, ..., QLT, ..., PRD), for example. PS: The existing order by column action in the Manage Environment list should  have an effect on ordering the dropdown of environments. A t this point changes the ordering of the list but has no effect on the dropdownThanks

It is only possible to assign fixed-style classes to table rows, not dynamic ones, based on the row value. It would be beneficial to have the ability to add classes and events to a row based on an expression. This way, we can apply styling and events to an entire row instead of every cell, reducing duplicate code.

It is very useful for me that module's version number can be see at progress of 1-click publish like below picture.We often use module's version number when talking with colleagues.Like "I fixed it in v.82."Currently we have to check Service Center or 'Open other Version' menu every time.