OutSystems works wonders when the API schema is stable, but many modern APIs return dynamic keys or partially populated objects, especially in integration-heavy and AI-driven scenarios. This creates friction because developers end up relying on custom JavaScript or complex workarounds just to render data cleanly in UI. What developers do today (pain): Build custom logic to extract unique keys Normalize JSON manually (fill missing attributes) Use JS to reshape payloads before JSONDeserialize Manage fragile UI rendering patterns for dynamic columns What I’d love to see improved in the platform: A native Dictionary/Map type for both client and server JSON tooling that supports deserialization into Maps for unknown keys A standard UI binding pattern (even without Data Grid) that allows dynamic columns safely This would reduce dependency on custom code and make OutSystems a stronger fit for modern API patterns. Curious, how are others handling dynamic keys today, and where do you see the biggest friction?

If this is possible, I'm not seeing it. In O11 you can download a forge component without having to install it. In ODC this seems impossible. Why? I want to see what's in a forge component before committing to installing it in my environment. I have done this for as long as the forge exists. Why would you take away this option?

To put it simply and directly: It would be great to be able to provide Mentor with a screenshot of a screen built in Figma. Who knows, maybe the Mentor can help create amazing projects with that.

Implement an active Artificial Intelligence prompt directly integrated into Service Studio / ODC Studio, capable of analyzing OML files to detect issues, suggest improvements, and propose corrections , both automatically and through clear, detailed explanations of the proposed solutions . The idea is to allow developers to select a module or a set of elements (Actions, Aggregates, Entities, UI, integrations, etc.) and request an intelligent analysis that can: Identify logic, performance, security, and best-practice issues Suggest architectural and code readability improvements Clearly explain the root cause of each issue and the recommended solution Optionally apply automatic fixes or generate assisted refactoring suggestions An initial approach could involve exporting the OML for analysis by an external AI model (such as ChatGPT or Claude). However, the key differentiator would be having this capability natively embedded within the Studio , removing friction from the development workflow and improving application quality directly during development. Modern development tools already leverage AI for code review, refactoring, and optimization , delivering measurable gains in productivity and code quality. Bringing this capability deeply into the OutSystems platform would deliver significant value to developers , reinforcing OutSystems’ position as a leader in intelligent, AI-assisted low-code development.

Hi, I've run into this a few times. I would like to have the ability to do a simple query with an IN clause, without having to rely on advanced queries. It should accept a list of Identifier. Today we do ( from an aggregate perspective): SELECT * FROM {TASKS} WHERE id = 1 or id = 2 or id = 3 But it would be really awesome if we could do SELECT * FROM {Tasks} WHERE id in (1,2,3) This allows us to do some pretty cool stuff with Lists setc ( eg you can now shim some of the more advanced sql functionality without writing advanced queries). An example would be: myList = SELECT id from People WHERE OrganisationId = 2 SELECT * FROM {Tasks} WHERE personId = myList Which would be 2 actions, and somewhat faster/cleaner than the current way Writing an advanced query ( frowned up by my companies' best practices guide - and I've also found advanced queries tend to be annoying to manage ) Looping through myList and putting the outputs into another list, which is then passed around (this also has a few nasties - lots of DB hits (albeit small ones), and refreshing this with paging is a pain

Hi, ODC PE navigation and functionalities have bugs and logic isn't user friendly. 1.1. Cannot login with the username and password from the owner of the environment in an app. 1.2. Cannot edit created users or add a password to them. Name keeps as "Unnamed user". 1.3. Result: without proper setting up the users, we cannot use the apps that we test before implementing them in the client. 2. Remember Me in ODC login doesn't work. After several minutes we need to insert credentials again. 3. Login in ODC Studio should be available inside the app, without needing to do it in the browser. Browser login should act independently, specially if we want to login in apps with other users. 4. Make available Login action in server side so that a system user can be added 5. There isn't a button to open ODC Studio without opening an app. 6. Add more logs to the Logs, like we have in O11 Service Center. Just published an app and gave an error and nothing appear in the logs. We need to have more in-depth information in the logs. 7. Messages used in "LogMessage" action don't appear in the logs. 8. Add sort in apps in ODC for Created Date. 9. Add details in ODC in each functionality. 10. Add details in Platform Updates to know the impact of updating. Note: A Developer should have control at all times of what he is doing. For that, more information is needed and ODC doesn't provide enough control on performed actions or in logs. There are several O11 features that should be implemented in ODC. Simple is not always better, specially in an enterprise platform, as control should be the drive in this case.

Currently, ODC does not provide a mechanism to extract or automatically generate documentation for applications. In previous versions, such as OS11, tools like OutDoc and direct access to OutSystems metadata allowed teams to generate technical documentation more easily. The proposal is to introduce an AI-powered capability that can analyze an existing application or library within ODC and automatically generate technical documentation, such as: application architecture overview dependencies and libraries used module and component structure APIs and integrations main functional flows This feature would significantly reduce the manual effort required to create documentation, improve knowledge sharing across teams, and ensure that documentation remains up-to-date with the evolution of the codebase.

When working in environments with many apps and modules, finding the ones we use daily can take unnecessary time. It would be useful to have a "Mark as Favorite" option for modules in Service Studio. This would allow developers to quickly access their most frequently used modules when opening the environment. For example: A star icon next to the module name; A "Favorites" section on the home screen; A filter to show only favorite modules.

Hi Outsystem Team, I believe that OutSystems Table Grid should also have some features like Data Grid such as column picker. Sometimes we have to use Data Grid just for the column picker type features. Thanks, Vijay M.

As we are now having folders everywhere, please do the same for service studio main screen. This way applications can be grouped by context.