Inside an aggregate comparing the same variable (inside a filter) should trigger a warning. If an aggregate filter says user.id=user.id it should trigger a warning clearly this will always be true. the user would have likely meant user.id=userid

First off, the "Create Action Wrappers" feature is really useful. When you right-click an Entity and generate the Create and CreateOrUpdate server actions, the platform already checks for Mandatory attributes. If a developer misses assigning a value to a mandatory field, an exception is thrown at the application level. That's a nice touch and saves a lot of headaches. One thing I noticed though is that for Text attributes, there is no validation on the defined Length. So if a developer passes a string that is longer than the max length set on the attribute, the value still goes through to the database and you get the classic "String or binary data would be truncated" error. That's a database level error, not an application level one, and it gives the developer zero context on which attribute caused the problem. Since the platform already knows the Length property of each Text attribute (in the Entity definition), it would be great if the generated wrapper could also validate against it. Same pattern as the Mandatory check, just extending it to include a Length check for Text attributes and throw a meaningful exception before it hits the database. This could help by: Making the generated wrappers more complete and consistent Giving developers clearer error messages during development and runtime Reducing unnecessary database round trips for data that was never going to be accepted anyway Really appreciate how the platform already handles the Mandatory side of things. This would just be a nice extension of that same thinking. Would be great to have this for both O11 and ODC. Thanks for considering!

I observe that the people who are new in Outsystems they complete the course but when it comes to certification exams they found question in exam confusing and they perform poor in exams.  I think there should be at least one mock test before certification.

ODC forge components are NOT included in you "Asset Count" on your profile, only OS11 force components. They should be included.

Whenever you create a new object in service studio, please put the focus immediately on the name property of this object, so you can start typing the name without having to select it explicitely. You never need a nameless object, so you always have to make this extra click, which is really annoying. This applies to (but not only to) new actions, parameters and variables. On top of that, this feature is already there for roles, entities and site properties for example, so please make it consistent for everything.

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.

An app where developers can create AI Agents using Mentor inside ODC, guided, structured, and production-ready. A lightweight app that helps developers: Define an Agent purpose Generate the System Prompt Suggest Actions Recommend Grounding strategy Propose Memory configuration All using AI guidance with Mentor.

It would be great to have a Start Index  property in Aggregates so that I can have pagination patterns even without UI. This way, I could state that I want 50 records starting from record 50 (e.g. to display them in the second page of a table).

In the new Service Studio alert that shows the forge components that have new updates, there could be an "update all" option or checkboxes and and an "update selected" option.

Looking at the authorizations offered while creating the connection to MCP (Model Context Protocol), all the options related to (OAuth) ask for a client secret as a mandatory field. While searching on MCP Documentation, the client side must implement a PKCE (Proof Key of Code Exchange) flow, with this flow its not mandatory to have a client secret to get Authorization to interact with the MCP Server. Making a lot of MCP Servers impossible to connect to OutSystems. Where is the link for the documentation where they explain why PKCE flow should be mandatory: https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization#authorization-code-protection My suggestion here is to make client secret not mandatory.