When we export some Excel data using the Excel To Record List action, the column headers is filled with the name of the field in the structure, but we are not able to translate that name. It will be very usefull to translate this name for Export in different languages

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.

In a multi team development environment, changes can be made to an integration such as ingesting a new field in a dev environment (ie adding a new attribute to an entity). Using Integration Builder, this attribute might be added to the integration and work as expected in the Development environment. However, if that integration is now required to be deployed with those changes through to production, but the integrated database doesn't have the required attribute deployed to production, this can cause production errors. My suggestion is to provide a log of changes showing what additions or subtractions have been made to an integration so that they can be validated prior to any deployment. Alternatively, during the preparation of a deployment, test that all integration attributes are valid and pause a deployment to alert of this missing attribute.

By Default fill in the Description Section of the Aggregate and Timers when a new aggregate or timer or any variable is created to avoid Architecture Dashboard Issues.The user can then change it to any values he wants. This will avoid issues on the Architecture Dashboard which in turn will increase the development speed.

Hi,Would be great for troubleshooting if the runtime values used in query parameters were also logged in the error log text. The tenant Id would also be a good idea to support multi-tenant scenarios.Of course this would only be applicable to query related errors and they could be shown in the log in a very simple manner like:"TenantId = 1Param1 = 123Param2 = "Text"Error in advanced query  (...)"This would allow much faster debug in Service Studio.Cheers,Hermínio

 It would be great if any new ODC forge component could be listed in OutSystems Community newsletters , as daily digests.

When working with popup's in service studio for a reactive application, they overlap with the screen they are used in. On the forum is a great solution for this problem -> https://www.outsystems.com/forums/discussion/55208/zoom-in-or-out-feature-on-interface-outsystems-service-studio-11/ Why not make it part of a next version of outsystems ui, so everyone has this solution at start ?

Problem today: Even with Architecture Dashboard and AI Mentor, developers only discover issues after they have already been built. Issues like: Upward references, Wrong layer usage, Poor data modeling, Monolithic modules, Heavy server actions, Inefficient aggregates or SQL, Performance bottlenecks, Bad dependencies. These issues accumulate silently and become extremely expensive to fix later. I would like to propose a new, transformative platform capability that would significantly improve application quality, reduce technical debt, and strengthen governance for teams of all sizes — especially enterprises. The proposal is an AI-driven engine built into Service Studio that: Detects architecture violations in real time. Predicts future technical debt before it occurs. Suggests optimal module placement, layering, and reference patterns. Auto-fixes architectural mistakes with one click. Simulates performance and scalability impact of design decisions. Ensures every app follows Outsystems recommended architecture from day one. I hope this would bring huge value to the entire community.

Create a grid component that has advanced features like dragable columns, native grid editable fields, filter options, resizable columns, better sorting.  The Kendo UI grids are a good example.https://demos.telerik.com/kendo-ui/grid/index

Hi, As a secutiry increase to our applications it would be nice if we could assign roles (former permission areas) to screen actions and user actions. This way users that didn't have permission to run them, would never be able to use firebug and other tools in order to activate buttons that trigger the action and we wouldn't need to always be "asking" in every action, if the user has permission to run it. Another benefit would be, by unchecking the anonymous role, we could also automatically know if a session timed out, without having to "ask" that also in every action. What do you guys think?