Maintaining accurate, up-to-date documentation remains a challenge in enterprise environments — especially as applications evolve and team members change. While tools such as OutDoc provide valuable metadata-based documentation (e.g., structural elements, entities, modules, dependencies), there is an opportunity to extend documentation capabilities further using AI within the platform itself. I would like to propose native AI-generated documentation that goes beyond structural metadata and instead leverages the platform’s understanding of: Application logic flows Business rules and decision paths Integration intent and usage patterns Architectural layering Cross-module interactions Rather than simply listing components, the AI could generate contextual explanations such as: What the application does functionally How key processes are orchestrated Which integrations are critical and why How data flows across modules Where architectural boundaries exist This could live within the application overview, Service Studio, or a dedicated Documentation view — refreshable on demand and editable as needed. Importantly, this would add value not only for future platform directions, but also for the large base of existing OutSystems 11 (O11) applications running in production today. Documentation drift and knowledge loss are challenges that exist now, and having AI-assisted documentation available in O11 would provide immediate impact for enterprise teams. Many teams already experiment with exporting artifacts and using external AI tools to generate higher-level documentation. I recently explored this approach externally as a proof of concept: 👉 https://www.acceleratedfocus.com/post/bringing-clarity-to-undocumented-outsystems-code-with-ai Embedding this capability directly into the platform would: Improve developer onboarding Reduce knowledge loss Support governance and compliance Accelerate modernization initiatives Strengthen long-term maintainability This would not replace structured metadata documentation tools like OutDoc, but would complement them with AI-driven contextual understanding.

Currently, the OutSystems UI stylesheet applies a box-shadow effect through :focus when accessibility features are enabled. As a result, the focus indicator is shown both for keyboard navigation and mouse interaction. It would be preferable to use :focus-visible instead, so the focus indicator is only displayed when it is relevant, namely when users are navigating with the keyboard or using assistive technologies. This would provide a more appropriate default behaviour, improving the experience for mouse users while preserving a clear and accessible focus state for keyboard navigation.

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?

OutSystems provides a very useful feature for Entities, where developers can quickly generate wrapper actions like Create, CreateOrUpdate, and Delete via right-click. However, this convenience is missing for Roles. Currently, when a Role is Public and reused across applications, developers still need to manually create server/service actions to: Grant Role to User Revoke Role from User Proposed Solution: Add a right-click option on Roles to auto-generate: Grant wrapper Revoke wrapper (similar to how Entity action wrappers are generated) Why This Matters: Speeds up development Eliminates repetitive logic Improves consistency across applications Enhances developer experience in ODC & O11 Real Impact: In multi-application architectures where Roles are shared, this feature would significantly reduce effort and standardize role management. Even if a role is marked as Public, in ODC we can only check the role in other applications, and we still need to manually create actions to grant or revoke roles every time.

Add an option in the Service Studio settings to disable automatic joins when adding new entities to aggregates. This is useful when there are multiple possible automatic joins. In many cases, fixing an incorrect join requires more effort than benefiting from the automatic behavior. Additionally, in more complex aggregates with many joins, it becomes harder to manage and verify which joins were automatically added and whether other entities were also included automatically.

An often-occuring issue is that user click on an action twice, which causes an action to run twice. This leads to very nasty issues where data is created and/or processed twice. One way to prevent this, is to wrap your Button into a 'Button Loading' widget, and adding an IsLoading widget to the page. It would be nice to support this in an easier way, either by: Adding a property to the button that adds 'IsLoading' behaviour to it Add ButtonLoading widgets around all your button widgets in your apps Any other ideas to achieve the same result?

I would like to see a built in midnight/dark theme for service studio. Something that is a little easier on the eyes when working the night shift.Looked around but couldn't find anything to suggest this is a duplicate, but let me know if it is.

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.

Currently, we have Service Studio on Windows and Apple machines. We always have to update it and it's not possible e.g. to use it on Linux. Other Low Code and No Code providers have have it web based. Please investigate it you can make Service Studio web based.

I would like to be able to configure Mentor AI so he behaves like a true member of our team. I want to give him our coding guidelines so he always codes the way we do. Example: always adding comments to every function, combining variables into records to reduce clutter, or using PascalCase for naming. On top of that, I want to control how he communicates. Sometimes I just want him to do the work with as few words as possible, and other times I want a detailed explanation of every decision he makes.