Currently, when using an Input widget with Type = Number, it is not possible to set a Max Length for the field. This forces developers to switch the input type to Text and implement additional JavaScript, masks, or custom validations just to control the number of digits — which increases complexity, reduces maintainability, and removes the native numeric keyboard on mobile. Adding a Max Length property (similar to text inputs) would allow developers to: Prevent users from entering more digits than required Avoid using JavaScript workarounds Keep the input type as Number Improve UI validation consistency Increase development speed This enhancement would significantly reduce unnecessary logic and provide more control over numeric inputs without losing native browser behavior

Hello everyone Basically I'm sugesting an identical wizard such as those that already connect to SQL Server or Oracle Cheers Francis

Problem: Currently OutSystems ODC provides the User and access management API and Portfolio API to access the platform functionalities from code. However, connection is done via a custom consume REST Connectors, and they consume quite a lot of AOs to one's license (15+). This also Proposal: Connectors, that do not count towards the total AO count of a license. This could be achieved via a couple of alternative options: -an OutSystems-provided official connectors, that similarly to the System's libraries do not count towards the total AO consumption -unsupported custom Forge Connectors (like now), that have the option to be reviewed and aaproved by the OutSystems team, and they do not count towards the AO consumption -out-of-the-box way of consuming the APIs as part of the platform (inside System library Actions or similar)

As a Developer i want full insight in where my code is used. Right now it is not shown when my ServiceActions, Events or Screen are used in ODC Workflow. I would like to have this info added to my usages to get complete info on where my code is used.

A mobile application that allows developers to join User Group events anytime, even when they don’t have their laptop. This makes event participation easier, increases accessibility, and encourages more developers to attend and learn from OutSystems community sessions.

Hi, Just published an app in O11 after undoing some steps. Then noticed that Service Studio automatically undid my undone and published a latest version without my changes and even without giving me a warning or an option to select. Please: Don't try to automate things that should not be automated. The developer should be the one in control at all times. Also, every time I publish, the laptop gets a bit unresponsive till it finishes. I don't know what was changed in this version but has some issues. Note that issues in copy-paste are on-going for several versions now. This might be because of some background processing for automations but are impacting when we need to copy text inside Service Studio (that doesn't get copied). Best regards, Miguel Garcia

When changing locale of a screen, in multi-lingual applications, everything is translated, except validation messages. The validation message is displayed in the right locale when triggered, however, if the validation message was already added, and then the locale changes, the validation messages are not translated to match the new locale. To translate the validation messages, the user has to trigger the form validation again.

Remove the GetUserId() in Client Actions and Screens to prevent client-side tampering. When developers use GetUserId() on the client side (Reactive/Mobile), that value is compiled into JavaScript. Anyone can open the browser developer tools, manipulate that ID, and potentially spoof another user. AI Mentor Studio already flags client-side GetUserId() as a security vulnerability because browser JavaScript can be manipulated. Instead of detecting this flaw later, OutSystems should remove GetUserId() from Client Actions and Screens entirely. By making it unavailable on the client side, new developers will be forced to use secure server-side session checks from day one. This shifts the platform from detecting vulnerabilities to preventing them, saving time on refactoring and ensuring apps are secure by design.

The same way we can filter members from staff and Champions/MVPs, it would be great if we were able to find those who are willing to be mentors. Now that there are almost 100 people with that "job", it is hard to keep up. Specially because the OutSystems filter on ADPList is not great. And since you are at it, please add a filter for those who have been speakers. This is helpful for User Group organizers looking for speakers, and the both combined would help potential speakers to find guidance and overcome their fears. In short: every time you add a tag to the profiles, add a filter to it.

The currently used Icon Library - Font Awesome - is an outdated version, no longer supported or mantained. Updating it to the the current library would allow for an easier frontend development process as developers wouldn't need to use any aditional libraries, plugins or forge components.