If we want to inspect or edit the value of the external_id attribute of a user, we always need to do this via direct access to the database. It would be much cleaner to have this attribute available in the User_Show and User_Edit screens of the Users Application.

Here is our scenario: We have setup a corporate theme and we want to make our internal applications follow same theme. We have created an application template which has our theme already implemented in the template. When we create a new module using our template, the new Application widgets asks to select a color (okay for the application icon), however, when we create the first module it automatically adds the theme editor to the module. Most of our developers are entry level and don't think to remove the theme editor styles to that our master theme will always apply. When a new module is created from a template, Service Studio shouldn't be adding back its own code.

Enable users to dynamically adjust the number of column controls (e.g., 2, 3, 4, etc.) directly by clicking on the column control itself.

I find it very useful to have "Previous Screen" as destination on Mobile. But why don't we make it level? Make it available on Web too.

When using the AddDays() function on an object of type Date, it will return an object of type Date Time. I would expect it to return a Date here since that's what I was working with and AddDays() does not impact that (unlike AddHours(), AddMinutes()). For example: AddDays(CurrDate(), 1) Will return a Date Time, while I'm only trying to obtain tomorrow's date.

A "Service Studio Lite" that runs in the browser for quick logic fixes and metadata reviews, offloading the heavy rendering to the cloud and reducing the dependency on a high-spec Windows/Mac desktop client.

Previously suggested more than 10 years ago, here https://www.outsystems.com/ideas/123/different-service-center-colors-for-different-environments/Was marked as "Implemented" however the implementation was just adding a text label, rather than more prominent coloring or theme. Moreover, the "improvement" seems to have been removed in OS11.Now that the top-menu has a white background, it should be easier to implement different colored backgrounds for different environments, either as a text-box accepting a hex-color value, drop-down selection, or pre-configured colors, for instance:This would provide more differentiation between different environments and help prevent configuration mistakes, e.g. configuring mistakes on production, or incorrectly deleting modules

Right now the pattern is to put a hidden link on the screen and use "Widget Click" to trigger it. That's kind of ugly and we have the need often enough that this is a hassle. There should just be an Action to make a popup occur, have it work like the "go to this page" does, but as a popup.

Service Studio SDK with some kind of API that enables programers to develop plugins that generate OutSystems "Code" and extend the IDE

Although the website design is responsive, it doesn't have that great of a user experience in mobile. It would be great to have an Android/Iphone application where you can easily participate in the forum, as well as do quick searches for information.