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.

Many times, when developing an application, I have an action within a block that I need to trigger from the screen that uses it. I had many cases where this happens. For instance, let's say I have a button that will validate the the form within a block in the parent screen. I want to handle the validation just inside the block, and will need to perform the validations within it. Or when you want two blocks to react with eachother, but don't want to join them on a single block. Or even when I just want a button to perform an action that is inside the block. Currently, there are indeed some workarounds for it: Creating a dummy variable on the screen, that works as block parameter that will trigger the OnParametersChanged. This one gets complicated when you already have an OnParametersChanged set, but want to run just a single action; Handle all the data from the parent screen using events; Create an invisible button within the block, and set the onclick event to an external from the class or Id of the button - similar to this documentation page: https://success.outsystems.com/documentation/how_to_guides/front_end/how_to_call_a_block_action_in_a_mobile_screen/ But things get complicated when you have many blocks inside the screen, and this end with many "dummy" screen variables, too many screen actions just to perform an action that is already inside the block, or refactoring the screen/block to join them against your own will, and increasing development time. In blocks, the communication between the block and the consumer screen block are triggered by Events. It would be nice if we had the possibility to consume a screen action from the block, like setting it to "public" so you can run it from the parent. And would be way easier to manage this actions from blocks inside a list, so you would only need the row number to trigger the action. This issue brings many questions on the forum as well, like: https://www.outsystems.com/forums/discussion/73627/how-to-run-action-block-from-main-screen/ https://www.outsystems.com/forums/discussion/102238/triggering-save-action-from-block-using-a-button-on-screen-in-outsystems/ It would make the development cleaner, easier to follow good-practices and follow the low-code philosophy.

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?

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.

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.

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?

Hi, this is just an idea for a developer's perspective, it would be nice to have the ODC workflow builder in ODC Studio itself instead of going back and forth from ODC studio to ODC Portal when developing for the workflow.

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.

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.

Working with multiple environments simultaneously is a standard practice, but Service Studio makes it hard to distinguish between them at a glance. Currently, a developer must check the status bar to know if they are in Dev, QA, or Prod. Introduce an "Environment Theme" feature where we can assign a specific color to each infrastructure. If I'm in Production, the Service Studio UI (or at least the tab bar) should have a distinct color (e.g., Red). Add the environment name as a prefix to the tab title (e.g., "[PROD] MyModule"). This would prevent accidental changes in the wrong environment and significantly improve the UX for developers managing complex lifecycles.