This idea is about adding the detection a pattern of developers calling a REST or SOAP api method from a Service Action. REST / SOAP services are already a loosely coupled services, and there is no need to wrap them in a Service Action, which only results in two times the latency, without any additional benefit.

In service studio, when we are managing dependencies, for entities, we are able to preview the attributes of the entity. This is very useful, as it allows us to see whether we are adding entities which contains the FK or PK references. In ODC studio, this option is not available. Which means we have to add the public elements, and then go to the data tab and preview the attributes. Good thing we do not have to do a publish first. Because, actually i don't even need to see the data or values, i just want to see the attributes which quite often, it is good enough And the worst part, we can't even resize the pop up in ODC studio. So have to hover over the description one-by-one to look at it

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.

In the Language Translations editor, please enable multi-select dropdown support for the Behavior filter. Currently, when searching for a word to translate, the editor also shows results already marked as Don't Translate, which adds extra effort to filter them out manually. If Service Studio allowed filtering to show only items marked as To Define and Translate, it would significantly simplify the translation process.

When reading OutSystems documentation or forum posts, I’ve noticed that images usually appear bright and clear. However, when I reach a step where I need to read the content of an image step by step, hovering over it causes the image to become less bright or slightly blurred. To restore its original clarity, I have to click on it to zoom in. If the goal is simply to follow the flow and read the content while pointing at different parts of the image—without zooming—it would be helpful if the image didn’t blur upon hovering. on focus: - normal view: - on focus/hover: - on focus/hover: - Just a suggestion!

Hello, I currently work with version 8 of the OutSystems software and noticed something that could be improved. Not sure if someone suggested this idea already but here it goes: When in debug mode, every time I am analyzing an SQL object, there are times I need to test it. Unfortunately in debug mode I must manually insert all input variables before hitting the test button. In simple websites/systems this might not be an issue but with complex systems it becomes hard to find out the values of certain parameters. My suggestion would be for the software to automatically fill in the parameter values based on the current object. For example: If I am currently analyzing object A and the SQL query needs this object's ID then it would be filled automatically so I can just hit the Test button instead of me searching for it. Keep up the good work! Regards, Ricardo de Freitas

Currently, the Service Studio CSS editor does not recognize "@layer" directives (notice the warning and the missing syntax highlighting on my ".test" class. Layers are a part of CSS and already mostly supported in all browsers. Althought this does not impact atual usage, it would be nice for it to be supported in the code editor. This could be as easy to implement as updating the underlying editor (I think it's Monaco Editor )

Hello,Since there is no good way to search for a specific field in aggregates I would suggest an easy way to make the group by. Something, similar to what we have with the sort functionality, where you can select a field from the result set.My suggestion would be to create a new tab on the aggregate header so that we can introduce the group by that we want. Possible a multiple select would also be nice.Attached I am adding rough scratch.

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.

Lately I've run into a number of Forge components that have 'Try Now' buttons but the try now page fails.  This is typically because most of the user created components are now using their own personal edition environments to maintain those web pages. Recently a number of these personal environments are either completely gone or suspended.  While the recent improvements in the Forge for version 9 are great, it's a real pain to click the 'Try Now' button, watch it fail, download the component, play with it for a while and realize it doesn't do what you want.  Seems that the Forge needs to be more like an app store where there is at least some documentation (most have none), a working 'Try Now' button and at least some assurance that installing the component won't screw up my environment.  (This was a bigger problem in the past, less so now.)