In the Dropdown Search component, it would be beneficial to enhance the OnChange event by allowing it to include additional attributes. Currently, OnChange only provides five default attributes from the DropdownOption structure: Value, Label, ImageUrlOrIconClass, GroupName, and Description. It would be helpful to introduce a JSON attribute where developers can pass extra information about the selected item. This enhancement would reduce the need for additional local variables and data aggregations, streamlining the retrieval of supplementary details within the component. Currently: Ideally:

I don't know if there is somewhere else for this... https://learn.outsystems.com/training/journeys/web-developer-exam-2993/best-practices-for-building-screens/odc/6729 There's explicit instruction elsewhere in the training NOT to use Check###Role() on the enabled button, but to only use it on the visible property, because you can just hit F12 and enable the button.

I have noticed, and confirmed, that submitted Forge components in ODC Forge do not currently contribute to the community ranking. Additionally, it appears that there are no planned updates to address this issue. In my opinion, addressing this functionality is important to maintain the significance and value of both ODC and O11 when it's about the community ranking.

Currently, supermarkets limit the number of people inside the space, but there is a problem outside the commercial space, with the cluster of people waiting for their turn to be able to enter and purchase the goods they need.The idea is to create an application that performs the virtual queue management in which people can schedule their place in the queue before leaving home. The application generates a number in the virtual queue and will indicate to the user what time is most likely for him to enter the supermarket. In addition to the information in the application, the user receives an SMS indicating the place in the queue and the estimated time of entry. The information is updated with time intervals to be defined (5m, 10m, 15m, etc.). It will be necessary that each of the participating stores use the application and agree to create a specific virtual queue for the users of this application.The application can be applied to othet type of stores than supermarkets. Stores that use the application will be helping to reduce the risk of contagion, as there are clusters of people outside the commercial space.

With REST services, we can open the documentation from the context menu. With SOAP web services, we have to type the URL (which is not easy to find) to get there. It would be great if we had a context menu option "Show Documentation" for SOAP as well.

 Add a possibility to do a Distinct Select from a field on a Simple Query.

It's good if we have option to share our achieved badges to social media like LinkedIn. Whenever we achieved a badge in mail as well as the profile page , it's good to have a share action. By showing it to outer world, it's showing our achievement as well as it will create enthusiasm among others who watching this post in social media. So I think it will be better to have this feature in OutSystems. Regards Murali

Hi Team, As having more dependencies increases the size of your Module and increases the duration of 1-Click Publish.It would be great if user get warnings in TrueChange to remove all unnecessary dependencies of module.As of now i don't get any clue that no of unused dependency in module has increased to  a large number.Thanks,Preeti Kumari

The debate about the null values is still alive and kicking in the OutSystems community. This shouldn't be a "war" between team No Null Values and team Null Values. Null values do exist in other platforms and they can't simple be ignored. It's not the first time since I work with OutSystems that I need to differentiate between a 0 and null values. Of course there are some workarounds, but are they the best approach? I don't think so. What if we could settle this "battle" once and for all? I propose giving developers the power to decide if null values should be the default for an attribute when creating it. Attribute per attribute. There could be an extra option in the attribute property, bellow "Default value", a checkbox with the label "allow null values". Always unselected by default. Simple right? And this is a common option in other platforms. It sounds reasonable to me and may solve the "war", as everyone can have their predilect choice.

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.