There should be ability to add unit tests automatically for any actions. Also a unit tests should be automatically added to a Core Modiules.

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.

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.

Currently, We have the option to add new Entities and attributes and similar UI screens from the ODC portal. A enhancement to ODC AI mentor that enabled extension of existing applications by automatically identifying and reusing dependencies within the same/different ODC environment / integrations. Enhance ODC AI Mentor to support the following flow: Allow the developer to upload a BRD /FRD or provide promt describing the required extension. AI mentor analyzes the input and automatically refers the existing app in th ODC environment. AI mentor identifies and fetches relevant dependencies, such as Entities, Server actions, Integrations, Business rules, UI components if applicable based on this , AI mentor generates a new module and links it with the existing app dependencies. Sample example: If an existing lets say Movie Booking App doesnot have a ratings and feedback module , the developer can, either upload a BRD describing the feature or provide a prompt to refer existing app from this AI mentor identifies existing entities like Movies,Users,Bookings etc... AI Mentor creates a new module for ratings & feedback and links it to the existing entities This feature would be very useful for developers and make it efficient to build and extend applications in ODC. Thank you

To prevent the population included in the group most vulnerable to contagion by the new coronavirus leaving home, namely the elderly and people with chronic diseases, the Municipality of Proença-a-Nova and the Parish Councils and Unions created a solidarity network for situations of emergency, namely for the purchase of medicines or essential goods, among others.In each village, an interlocutor between the population and the Parish Councils is being defined to communicate needs, and the Municipality is responsible for the subsequent delivery of orders.To facilitate all the communication between the interlocutors and the Municipality, volunteers developed a web and a mobile app during the weekend using OutSystems and made available to Municipality employees to use, tracking the daily requests with the necessary details.

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.

I suggest that to truly win 2026 Outsystems should position Service Studio not as a tool for developers but as a" command center for AI Agents ." The goal should be to make the one-click publish feel like a one-click Delegate, where the platform handles the complexity and the human provides the strategic "vibe."

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.

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

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.