Just like many other sotfware solutions in the market, it would be very helpful if one could customize the workspace, for example, moving the toolbox to the right side of the main area or the development tabs to the top, etc, or even add my own shortcuts to the toolbar, show my favourite or most used widgets in the toolbox, etc... Customization should be only the first step, it should also allow to create a new MainEditor for side by side comparison, create different workspaces for different purposes (debugging, screen development, data modeling, etc). For reference this is how Service Studio is presented today: Source: https://success.outsystems.com/documentation/11/getting_started/service_studio_overview/ And I believe it has barely changed since the first versions. Its time to give it some refresh.

Like we have statIndex property in client side, it would be great if we have the same on server side as well, so that we can fetch limit records wherever required. --Sandeep Kolli

Suppose thatI have a Service module , exposing a service action (under the hood rest endpoint).I have a consumer application that references this service action.I change the name of the service module .This change does not result in an incompatible/outdated consumer in service studio.Now on run time I do get errors when I use the logic that uses the service action. This is understandable ofcourse since in the service action is just a rest endpoint (and changing the name, means the url path is changed).However, since the consumer is known, it would be so nice to have a TrueChange warning during deployment of outdated consumers.

Outsystems Mentor is great at building the first version of an app. However, technical debt still accumulates when human modify AI generated logic. The Future: " Self-Healing "Logic Dashboards. The Need: An AI service that constantly scans ODC environment for " Architectural Drift". If a developer creates a circular dependency or sub -optimal SQL query, the AI shouldn't just "flag" it - it should generate a "refactor merge request" automatically.

As I am working on more requirements in reactive application development, most of the requirements will be like opening/closing popup by clicking button without any validations or logic to display forms/details. In this case, if we have built-in assignment feature (enable/disable visible property) in button or link onclick/onchange property, we can easily assign visible property and filter variables.

Would be nice to have Markdown support in the Comment blocks inside the logic. This would enable better communication of significant implementation logic.Additionally, if the Description attribute could accept Markdown, it would greatly benefit documentation. This way, more complex explanations of how to use certain actions and parameters could be provided.

 Background & Current Behavior On OutSystems 11, we were able to query an aggregate view of Users and their Roles and/or Groups (both directly assigned roles and those inherited via group membership) in a single transaction. In ODC, many of the system entities are obsolete including Role. To replicate some of our page, we must now use the newly introduced User Access Management APIs. Get /users had been promising. It can return the list of users' based on the parameters provided. It could have been the best alternative if when passing "assetKey" (applications id), it can return the users with the roles for that application. However, while it does return the users with directly assigned end-user roles, it omitted users where their end-user roles were only inherited from a group. To work around this limitation, we must now: Call Get User Groups for each user For each group, call Get Group Roles Merge and dedupe results in-memory This multi‐step approach leads to an exponential number of calls when you have many users and groups, causing unacceptable latency and resource consumption. Why This Matters Performance Degradation N users × O groups per user + P roles per group Dramatic increase in response times and network traffic Increased Complexity & Maintenance Custom merging logic Higher risk of bugs, especially around pagination, retries, and deduplication Business Impact Current workaround severely degrades performance Enhancement & Expected Behavior Extend the Get /users endpoint so it returns each user’s full set of roles, direct and inherited in one call. We can also add backward compatibility by adding new parameter such as "includeInherited" to identify whether to continues to return only direct assigned roles.

To simplify the process of adding new languages, it would be highly beneficial to incorporate AI-powered translation as a feature. When a developer adds a new language, the system could automatically generate initial translations using AI. This would provide developers with a solid starting point for localization, which they could then review and modify as needed. By integrating AI translation, developers could save time, reduce manual effort, and accelerate the process of expanding their application into new languages, while still maintaining control over the final translations.

in case use drag table into the flow , outsystems create list & details page in pages , mendix for example allow user to select the style of create and update in popup or in new page

In web (reactive & traditional) we can create screens/ web blocks, mark them public and reuse them in other application/ modules by adding its depedency.In mobile application also we can do the same for blocks but not with screens.So mobile application projects should also have capability to mark screen as public and reuse them in other application/ modules by adding its depedency.