When tagging someone in the OutSystems Forum using @, multiple people with the same display name can appear. This makes it unclear which person you are actually replying to. To improve clarity and avoid confusion, I suggest these options: Enforce unique usernames that each user can set for themselves. Display this unique username with name consistently across the forum (profile, comments, and mentions). In the mention dropdown, show both name + unique username so members can easily identify the right person. Or We can also go with an easy step, which in the forum email should be displayed with the name, and also in the mention dropdown This will make communication smoother and ensure that members always tag the correct person in forum discussions.

We should be able to define the names of the fields we are exporting to excel.

While creating Agentic App. the models on the ODC portal are available for every developer without restriction. this could hinder with governance policies while dealing with multiple teams. Suggesting to add Management layer similar to OS 11 lifetime teams to manage development teams more effectively enabling governance of apps and AI Models.

Propose the development of a robust server-side CAPTCHA validation component to enhance security and prevent automated bot submissions, as currently we don't have any OutSystems-supported CAPTCHA component available. Most existing CAPTCHA implementations rely on client-side validation, which can be bypassed, leaving applications vulnerable to spam and malicious activity. A server-side approach would ensure secure verification, improve application integrity, and provide stronger protection against automated attacks. This component should validate CAPTCHA responses on the server, integrate seamlessly with popular CAPTCHA services, and offer easy configuration through a developer-friendly interface and reusable blocks. Additionally, it should support accessibility standards and multi-language options for global deployments. Benefits: Enhanced security against bots and spam Protect sensitive forms and transactions, boosting confidence in the platform Developer-friendly implementation with reusable components

As the Agentic AI badge course suggests to set default values with Settings for SystemPrompt and UserPrompt, I think this will be done more often by Developers in the future. So for ODC Studio there is a popup window for the Settings description but not for the default value. So I think it is a good idea to also provide an addional popup window for the Settings default value, to see clearly the whole default value.

It would be great if we could integrate with Git directly (out of the box) with Service Studio to manage Javascript/JQuery/React/.. and CSS projects.With Git being one of the most popular and powerful Source Control providers, harnessing its power from within Service Studio would just be icing on the cake.

Events in ODC is a great step towards an event driven architecture. In the current implementation, it only allows for server side consumers and I'd like to see that expanded to client side consumers as well. Imagine I'm building a real time application with OutSystems and I want my UI to be refreshed as soon as some backend process is done. Currently, I need to manually integrate with some web socket / server sent event service to achieve this functionality. From my experience this is a convoluted process that requires a lot of time and the purchase of third party services. This is not the low code way. Since now OutSystems has the Event primitive, it's the perfect time to add this capability.

I realize that often company logos on their websites are in SVG format and I need to convert them to PNG to use as an application icon.

The new JavaScript editor for mobile apps, is great, but the autocomplete could use some work :)The feature catches comments and strings at the moment, see below.

As developers building localized applications (like marketplace apps for regional users), managing multiple languages manually in OutSystems can be time-consuming. Currently, we need to export, translate, and re-import resources or manually edit translations. The Proposal: I suggest introducing an Enhanced Localization Tool within Service Studio that leverages AI and modern automation to streamline this process. Key Features: AI Auto-Translate: An option to automatically translate text strings into regional languages (like Malayalam, Hindi, Tamil, etc.) using integrated AI services during development. Context-Aware Translation: The tool should understand the context of a UI label or message to provide more accurate translations rather than literal word-to-word conversions. Visual Translation Preview: A feature to preview how different languages affect the UI layout directly in Service Studio, helping to manage "text swelling" (where some languages take up more space). Centralized Translation Dashboard: A dedicated dashboard within Service Center to manage and update translations for published apps without needing a full redeployment. Why it matters: This will significantly reduce development time for global and regional apps, improve the quality of localized user experiences, and make OutSystems a more powerful choice for building diverse, community-centric applications.