Currently, the Default Value field in Site Properties is limited to a single-line input with no option to expand the editing area. This makes it cumbersome to view and edit longer values clearly. An expandable or multi-line editor, similar to the one used for editing Expressions, would greatly improve readability and usability.

The OS Traditional Time Picker UI Pattern has the option to set an Interval The OS Reactive Time Picker UI Pattern does not have this option and defaults the Interval to 5 minutes. Adding in the 'Interval'-input to the Reactive UI Pattern as well will give us more control over the functionality of the pattern so that we can tailor it to our needs.

The OutSystems UI should provide a moveable popup element. It could be the same existing element, but with the following features:A placeholder for the title and a placeholder for the main contentBeing able to change the position of the popup by clicking on the title and draggingOption to have or not a close button in the upper right corner (with customizable icon)Option to close on click out of the popup

It would be great to have a test at the end of each "path" to verify if you miss something important. Also it would be great if that question will be at the same format as on the certifications exams.

As NextStep 2012 says 'Simplicity'.A switch widget on a webscreen will make the web screens more simple to understand!

Currently, when we send emails using OutSystems, it doesn’t return the email ID after sending. This makes it very difficult to track/identify which emails were sent successfully and which ones failed. For example, if we are send 100 emails every day, we have to rely only on the system entity to check their status. But there is no provision to link this system entity to our application's transactional entity, so it’s hard to identify emails with their purpose or origin. It would be very helpful if the SendEmail action could return the email ID as output. This way, we could link the sent email with our business entity and easily track delivery status for each transaction.

Currently all comments have the same color. In Dark Theme they appear black and in Light Theme they appear gray. This makes it difficult to distinguish important notes or identify who added them. The proposed idea is to allow users to define the color of their own comments so that in action flows it becomes easier to see who contributed. If full customization is not feasible an alternative would be to provide three predefined colors such as normal yellow and red to indicate severity or importance. This would help draw attention to critical comments and prevent them from being overlooked.

In Service studio, when we manage dependencies, we have an option to show only dependencies which are in use. However, in ODC studio, this option is not available. It will be great to have it there, as this is a very useful feature.

Currently, the "OutSystems Mentor" title on member profile pages is static text. To better bridge our community with the global mentoring ecosystem, I propose making this title a clickable link. If a member is a verified mentor, clicking their title should redirect users directly to their ADPList mentor page. This streamlines the process for mentees to book sessions and view the mentor's full coaching credentials without manual searching.

As a developer, I find myself constantly using properties of lists and data actions like `. Empty ` and `. IsDataFetched `. When assigning to a boolean variable, Service Studio could suggest this properties. See in the following example that I wanted the `Tickets.Empty` property, but it was not suggested.