There are people in the OutSystems community that regularly produce high quality content (forge assets, ideas, forum posts, etc.). It would be nice to have an option to follow community members so that I can get notified when that person posts / uploads / etc.

It would be great to have the possibility to comment on a group of elements.And make it visually clear in the interface, which elements the comment effects.In this way it's more clear which elements are part of the comment and as a bonus you can easier comment on large pieces of code.In the same way comments are usually done in traditional coding, like (e.g. in javascript): //Start of function / piece of code /* Initialize and invoke a the greetUser function to assign user's name to a constant and print out a greeting. */ function   greetUser () {     const name = prompt("What is your name?");     console.log("Hello ," + name + "! How are you?"); } greetUser(); //Start of another function / piece of code /* Initialize and invoke a the sayGoodbyeUser function to print out a goodbye. */ ......Visual idea:

Add support for string formatting in Expressions like python code.In Outsystems we have something like this:"My name is " + Name +" and I'm from  "+CityMy ideia is to implemenmt something like this:"My name is %s and I'm from %s " % (Name, City)

All widgets in OutSystemsUI have "ExtendedClass" property, which can be used to apply changes to the style of the widget. However, some widgets inject a secondary element to the body of the HTML page. These elements do not inherit the "ExtendedClass", thus if a developer wants to style the element, he/she must apply a change to all said elements. For example, a timepicker adds the popover time select menu in the body, not inside the timepicker tag in the HTML tree. If the popover element has the added "ExtendedClass", the specific element related to the selected widget, can be targeted, and only it be affected by the new style.

When completing a Course, a wild quiz appears... I believe that if the number of questions and its complexity increases, the user acquires a bigger knowledge about the platform and its best practices.I would suggest that training official partners and MVPs group can help on that matter, making the community stronger in terms of knowledge.

By default OutSystems parameters are by value, but there are few exceptions. These exceptions should be visible at Service Studio.Example currently:Following would be better, when actually it is by reference.

In Service Center logs, add a “Quick Explain” button that suggests why the error might have happened (e.g., DB connection timeout, invalid entity reference).

Hello there,It would be nice to have inside Service Studio a way that we could check inside the module what size does it actually occupies each Flow, Server Actions, All the images all at once, etc...Best Regards,Edgar Ramos

The main idea is simple:- You could limit the modules that consume this module, this would mean that no modules outside that set of modules could ever reference anything from this module.This means the module owner(s) can in effect limit the consumers modules.I believe this would greatly help some medium/big factories.

The idea is simple, so we can define events in a webblock and the idea is that when we put the webblock in a screen we need to assign some action to those events and the idea is have the possibility of define the order that those events should run when the screen is rendered. Regards Miguel Grilo