Developers often forget to add a Prompt for Input fields, even when a Label exists. This leads to inconsistent UI and lower usability. Proposed Solution: If the Prompt is empty, OutSystems automatically sets it to match the Label text. Developers can still override it manually. Works for single-line and multi-line text inputs, across Web, Reactive, and Mobile apps. Example: Label: Email Prompt: (empty)→ Automatically set to: "Email"

It would be useful to search inside advanced queries across the factory.When profiling SQL Queries in production, using profiling tools like solar winds or SQL profiler, it's difficult to map back to where the query is being used.

In ODC "Add Public Elements" should be similar to O11 "Manage Dependencies". Or, at least, the user should be able to choose between using the new "Add Public Elements" and "Manage Dependencies" with the O11 like visuals and functionalities. In ODC the information provided and selection of Public Elements it's time consuming and developers cannot have proper control on the overall picture. In O11 developers have more control when using Manage Dependencies and can quickly understand what is happening. ODC: O11:

Hello,In several organizations there is a need to perform periodic access reviews because of regulatory requirements, and for doing this it implies to extract the list of users and roles with the permissions peer environment. So having this in consideration my sugestion is that in LifeTime Users List (/lifetime/Users_List.aspx) and Roles List (/lifetime/Roles_List.aspx), the Administrator would be allowed to export this information to Excel or/and pdf.Thanks,Miguel Oliveira

Hi everyone, I would like to propose the creation of an official training path and a specialization certification focused on Digital Accessibility, covering both OutSystems 11 and OutSystems Developer Cloud (ODC). As Low-Code developers, we have the responsibility to ensure that applications are inclusive by deeply applying WCAG standards within Service Studio and ODC Studio. My suggestion is for OutSystems to offer: Accessibility Guided Path: A comprehensive training focused on using OutSystems UI accessibly, handling ARIA roles, managing focus, keyboard navigation, and testing with screen readers. Specialization Exam: A technical validation for developers who have mastered the implementation of accessible interfaces in Reactive and ODC applications. Profile Badge: An official badge on the community profile, allowing partners and clients to easily identify developers capable of delivering high-quality, inclusive projects. Why is this important? Market Differentiation: Accessibility-certified professionals are rare and highly valued by large enterprises. Product Quality: It reduces technical debt and ensures that "High Performance Low-Code" also means "High Inclusion." Platform Strength: It demonstrates that OutSystems leads the market not only in speed but also in social and technical responsibility. I believe an "Accessibility Specialist" badge would elevate the technical level of our community and help build a digital world for everyone. #Accessibility #Certification

I would like to propose the inclusion of a logging capability for the SOAP requests sent and received from any WebService in the scope of an eSpace.Meaningful information to be included:-Server and port-Date + time-SOAP messages sent and received-User-Originator (process, flow, ...)And a log viewer that enables the search for Web Services invocations based on:-Service name-Date-Originator-UserThe Soap messages (sent and received) should be presented in XML.What we gain:-easy way of detecting configuration errors (wrong server, ...)-easy way of validating the input sent, for user input errors-easy way of validating the output sent from the back-end system via the web serviceThanks,Francisco Vasco

In Q1 2022, I used SAP BAPIs to connect to SAP. However, I tried the ODC trial and there were no SAP BAPIs available. It would take a lot of effort from an ABAP developer to convert BAPIs to APIs. Can ODC have BAPI connectivity?

Sometimes we need to navigate through the module, when merging. I think that is a good idea to allow to navigate through the module while doing the merge, without the need to close the merge popup. This is usefull to check the code on other actions (not on the merge)

Sometimes we are publishing an eSpace and we start working in another eSpace (which perhaps needs something from the other eSpace being published) and we have to keep switching tabs to check if the publish is already done.If we could have that information on the tab we wouldn't need to keep switching between eSpaces.Please see an example in the attachments

 CSS Variables (aka Custom Properties ) makes it possible to organize and refactor stylesheets. They are already supported by every major browser, except for Edge, which will add it soon.You can already use CSS variables in OutSystems applications. But Service Studio doesn't understand them, and the design-time preview will have low fidelity.With this CSS module, you can declare custom variables, and then use them throughout the stylesheet. For example::root {     --primary-color: #9E0616; } a {     color: var(--primary-color); } /* ... and many other styles could use var(--primary-color) */In such a stylesheet, changing the primary color requires only changing one line.This would greatly simplify the instantiation of a theme, because the variable can be declared with a default value on the theme, and when a consumer inherits the theme, it simply overrides the variable value:/* On the theme (e.g. LisbonTheme stylesheet): */ :root {     --primary-color: /* default */ #000; } a {     color: var(--primary-color); } /* On the application theme (e.g. MyApp stylesheet): */ :root {     --primary-color: #9E0616; }