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

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

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.

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.

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.

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.

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.

If a developer uploads a forge component, that has dependencies for other forge component, and that component is owned by another developer. When changes is applied to the dependencies like: discontinuing the consumed version, uploading a new version to fix issues, ... etc. Let the consumer know that changes had been made, to upload new version of their asset if needed.

The Forge component page should include more details, that allows one to judge the impact on and OutSystems factory without needed to install it first:Number of Application Objects (AO's)Number of integrationsPaid license required for a third party integrationExternal integrations overview (some components have APIs just to collect usage, this should be more visible.If it bootstraps data on publish (some components generate users, etc.)If applicable version of OutSystems UI used (OutSystems UI has a high rate of updates and deprecated functionality/breaking changes)Regards,Daniel