The constant concern with accessibility has forced us to be extra careful with the HTML semantics with which we build our pages. Depending on the context in which we are building an application, it's always a good practice to carefully structure our information hierarchy.So, even if there are situations where we don't want a DIV to be rendered in our DOM, we want that DIV to exist in design time to help us organize the elements, and consequently keep the code in a more effective and cohesive way.The idea would be the existence of a "ghost DIV" that is only used to organize the elements in Service Studio (in design time), completely ignoring it in the rendering of the page.

It would be nice to add the possibility of dragging and dropping a structure to a screen to create a form. Not having to go by the entity. The goal is to store the object generated in the form in a local variable. For instance to be sent out to API. When we need Outsystems only for the front end of an application (in case of legacy for instance), it could be handy to work with structure instead of entities that will be empty shell creating useless call the a db. Thanks

To improve Forge quality, which in my opinion is decreasing day by day, OutSystems should moderate all the new components submissions.Instead of being instantly available after submission, they should wait for someone from OutSystems to check them and approve.This would avoid the submission of tests, spam, exploits, redundant components, etc.

When we develop actions and specially change them later we sometimes remove code in the flow.When a variable is not used anymore after changing / deleting some code in the flow service center warns you about this (yellow line under the variable and a message in the warning panel).When an aggregate is not used anymore service center does not warn you about this.I would like service center to warn me so I can check if the aggregate can be deleted or not.In the example below the GetUsers aggregate is not used.

A weekly/monthly competition can be done for the community members to upgrade there community ranking. Where all community members can participate and showcase there skills. It should have some time limit. MCQ questions in first level and then in second level best practice question which can help people in there certifications too. Just a thought !!

In many online games with ranking systems, such as League of Legends, players are grouped into tiers and divisions like Bronze, Silver, Gold, Platinum, etc. Each tier reflects a player’s experience and performance, such as how long they’ve been playing and how many wins they’ve achieved. While this is mainly a very simple UI concept, it’s actually a very cool one 😄 For example, if a user’s rank is above 50,000, they could be placed in a tier like Bronze, which can be displayed on their profile and also used as a filter when browsing members. If their rank is below 6,000, they could be Silver, and so on for the other tiers. Features like this were very motivating for me personally. They encourage users to progress for the next tier within the community, serving as a strong source of motivation alongside of course the other elements like badges and achievements. On top of that, tier-based badges could also be added, such as Bronze, Silver, Gold, and Platinum badges when a user reaches one of these tiers, to further reinforce progression and recognition.

It would be interesting to show the execution time of the query when pressing the "Test" button in the SQL Editor for advanced queries.Yes, it's not a real view of how the query is doing, but it may help in understanding if a query is REALLY slow, or slightly slow.

The logs generated by the platform (screens, errors, integrations...) help us a lot when we are investigating an error. But I think it would be better if the platform allowed us to turn off these logs. We have recurring problems with the log database due to the large number of logs generated by accessing screens and integrations. Most of the time we do not need these logs but we cannot prevent them from being saved. We know that the logs are saved asynchronously, so there is no impact on the application (we use a separate database for logs), but we would like to have autonomy to turn on/off the generation of logs.

From the current list of certifications, I think the only critical topic missing is Frontend. It could englobe topics like CSS, UI widgets, best practices, security.A proper course to study would be welcoming as well.

 The current Menu is somewhat cumbersome and doesn't feel right. It's too much hassle to create an easy menu. Make it better and more customization friendly.