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

In O11, we are still able to retrieve the description of roles via system entities and display them in our UI In ODC User API, there is not such feature. It will be nice to have them, as a similar point to this Idea , we can't have spaces in the RoleName. And it does really looks awful to just display the role name in the UI

The proposed feature to delete all unused elements from a module in OutSystems Service Studio with a single click is highly useful. It streamlines the development process by reducing module clutter, enhancing performance , and improving maintainability. This feature simplifies the management of codebases, making them more navigable and less prone to errors. Additionally, it saves developers significant time by automating the cleanup process, allowing them to focus on more critical development tasks. This contributes to overall efficiency in application lifecycle management and deployment.

Hi, I have an idea to simplify email development in OutSystems a screen to preview email's HTML with dynamic data directly in the browser. the goal will be, Allow us developers to see the final rendered email (with parameters) in a browser during development. Benefits: Speeds up email design & testing. Easy debugging of layout/data issues. Can be reused as a live “View in Browser” link if needed. Best Regards, Faiz Khan

Web developing means having to working in many aplications including many browsers that makes us lose focus on service studio Playing sound on done or erro during run or publish could help keeping notion on the state of the application while on other windows

We frequently have problems with our database CPU being over-utilised by one or two resource-heavy queries and then our users experience poor performance and time outs because the database can't keep up with demand. We don't think one or two queries should be allowed to bring down our whole database, even if they are resource-heavy. Could I suggest some functionality which would allow us to cap the resources consumed by an individual query, please? Or something which reduces the resources allocated to a particular large query if there isn't enough resource available for incoming requests? Perhaps the Resource Governor available on SQL Server?

When we have the need to invoke the same entity twice in advanced queries we have the absolute need to put an alias in one of them, to distinguish them. The thing is that service studio puts a warning to it if you use Alias.* ... Perhaps one could assign an alias to the output structure?

Enhance the OutSystems Entity Actions Wrappers Accelerator to: Centralize validation logic: Automatically create a dedicated wrapper for validation rules specific to an entity. Consolidate Create and Update: Generate a single, unified server action that handles both entity creation and updates, utilizing the centralized validation wrapper for consistent and maintainable logic." This approach would: Reduce code duplication: By separating and centralizing validation logic, developers avoid maintaining identical or similar rules in both Create and Update actions. Improve maintainability: Changes to validation rules can be implemented in a single location, ensuring consistency and reducing the risk of errors. Simplify development: Streamline the development process by requiring fewer actions and reducing the need to manage duplicate logic. This enhancement would significantly improve the efficiency and maintainability of applications built with the OutSystems platform.

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.

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"