In OutSystems Platform publishing is like comitting your changes to Version Management. It would be extremely helpful to be able to add comments on the 1 Click Publish process. This would be even more flexible if one could drill down these comments by changed object (webscreen, webblock, action, webreference action, etc)

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

 Problem Debugging Reactive screens can be difficult when developers need to understand the current state of local variables, client variables, input parameters, screen data, and browser storage. How this suggestion can help A dedicated Reactive Debug Panel would give developers a centralized view of the screen state during runtime, reducing the need for temporary labels, console logs, or manual debugging workarounds. Implementation example Add a debug panel available during preview/debug mode showing: Current Screen: RequestDetail Local Variables Client Variables Input Parameters Data Actions Local Storage Session Storage The panel could allow developers to inspect values in real time and optionally copy them as JSON.

 Problem In large modules, unused local variables, input parameters, output parameters, and assignments can accumulate over time. This makes the code harder to maintain and can confuse developers during debugging. How this suggestion can help A better unused element detector would improve code quality, reduce technical debt, and help teams clean modules before publishing. Implementation example Service Studio could show warnings such as: Local variable 'TempStatus' is never used. Input parameter 'RequestId' is not referenced. Output parameter 'SuccessMessage' is never assigned. It could also provide a quick action: Remove unused variable

Currently, when a developer enables a breakpoint in a shared environment (like Dev or Test), all active sessions hit that breakpoint. This disrupts other developers and interrupts their work. Introduce a "Debug My Session Only" toggle within Service Studio. When enabled, breakpoints would only trigger if the request originates from the developer’s own authenticated user session or specific IP address.

Mentor is outstanding for developing components when you can explain your vision with language — although at times an image truly conveys more than words. His works well for pictures of current user interfaces (from other apps, or even other parts of your own app), images of whiteboard drawings, or any additional visual aid. That translation step is where things get lost. The idea is let us submit a photo alongside the Mentor chat, and give Mentor the task to examine it and generate the OutSystems component that matches it. This would work for captures of current user interfaces (from other apps, or even other parts of your own app), photos of whiteboard sketches, or any other pictorial reference. The value here is huge for teams that work fast. Instead of taking time writing detailed prompts, you just insert a screenshot and let Mentor figure it out. This might turn Mentor effectively advantageous for a wider range of daily development scenarios, beyond merely assisting people experienced in formulating prompts.

To add a link or a way to quickly open the Event Handler Action from Properties / Events of UI Widget. This can be extended to On After Fetch of Fetch Data From Server or UI Aggregrate. This will improve the developer experience to quickly open the Client/ Screen Action that assigned as Event Handler or After Fetch Event rather than scroll up and down Elements Tree For Button and link, we can quickly double click the Element in the canvas to quickly access the OnClick Event Handler already, however, this should be good if there's a similar way for other Widget like Dropdown, Switch, Custom WebBlock with Events, Data Fetch Aggregate...

 The Problem Most OutSystems developers learn best practices by reading documentation or watching tutorials. That's fine, but there's a gap between knowing what best practices are and actually applying them under pressure on real code. There's no structured, hands-on way to practice refactoring, security hardening, or architecture fixes within the OutSystems ecosystem. You either learn on production apps (risky) or you don't get to practice at all. The Idea Extend AI Mentor to include a "Practice Mode", a generator that deliberately creates imperfect OutSystems applications for developers to find and fix. AI Mentor already understands OutSystems best practices deeply. The idea is to flip that knowledge: instead of pointing out what's wrong in your app, it builds a training app that already has the problems baked in, and challenges the developer to find and resolve them. This is not about AI completing the work. It's about AI leaving the right kind of mess, on purpose. How It Works — Three Stages Stage 1 — Foundations (5 issues) Easiest tier. Designed for developers new to OutSystems best practices. Typical issues: unused variables, missing indexes on foreign keys, hardcoded values that should be site properties, public actions that should be internal, missing NullIdentifier() checks. Stage 2 — Intermediate (10 issues) Mid-tier. Developers need to think about architecture and maintainability. Typical issues: logic inside Preparation that belongs in a Server Action, missing input validation, exposed sensitive data in REST APIs, poor naming conventions, N+1 query patterns, missing error handling in integrations. Stage 3 — Advanced (15–20 issues) Senior-level challenge. Security, performance, and architectural decisions. Typical issues: SQL injection surface areas, missing role checks on screens and actions, exposed system entities, broken session handling, unoptimized aggregate fetching, tight coupling between modules, missing audit trail logic, improper use of client-side vs server-side logic (maybe bpt and tenant optimization and error handling too). Goal is simple do that changes remove error, remove warning and publish the application. Why This Works The value isn't in the generated app itself — it's in the deliberate, structured imperfection. Developers get a realistic codebase with real OutSystems patterns, real module structures, and real antipatterns to hunt down. AI Mentor can then serve as the referee: once the developer believes they've fixed the issues, AI Mentor reviews the app and confirms whether each problem has been correctly resolved — closing the feedback loop without giving away the answers upfront. Expected Outcomes - Developers build muscle memory for catching common OutSystems antipatterns - Junior developers have a safe, structured environment to level up - Teams can use Stage 3 as a pre-promotion or onboarding assessment - OutSystems certifications could eventually reference this as a practical preparation tool Summary AI Mentor already knows everything that's wrong with your app. Let it build an app that's wrong on purpose — and teach developers by making them fix it. Stage 1: find 5. Stage 2: find 10. Stage 3: find 15–20. Learn by doing, not by reading.

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.

 Problem Debugging layout issues in Reactive Web apps can be time-consuming. Developers often need to inspect CSS, containers, flex behavior, spacing, width, and alignment directly in the browser, but Service Studio does not provide a clear visual way to understand why a layout is breaking. How this suggestion can help A built-in Layout Inspector would help developers quickly identify spacing, alignment, overflow, flex/grid behavior, and responsive issues without switching constantly between Service Studio and browser DevTools. Implementation example Add a right-click option on widgets: Inspect Layout It could show: Widget: Container_Main Display: Flex Direction: Row Gap: 16px Width: 100% Padding: 24px Overflow: Hidden Parent Container: Section_Content It could also highlight margins, padding, and parent-child relationships visually inside Service Studio.