The Problem Currently, the "Create Entity Actions Wrappers" (CRUD actions) feature in Service Studio follows a static, hard-coded template. While this is helpful for rapid prototyping, most professional enterprise projects require specific architectural patterns that the default scaffolding doesn’t support. As a result, developers must manually wrap every generated action to include: Audit Trails: Automatically filling CreatedBy or ChangedAt attributes. Standardized Exception Handling: Ensuring specific UI or Log messages are triggered. Validation Logic: Checking for business rules before execution. Naming Conventions: Adhering to specific project-wide naming standards for wrappers. This leads to a significant amount of repetitive, manual work every time a new entity is created, increasing the risk of human error and architectural inconsistency across the team. The Proposal The introduction of a Custom CRUD Pattern configuration within Service Studio (at the Application or Environment level). This feature would allow architects to define a "Blueprint" or "Template" for CRUD generation. When a developer right-clicks an entity and selects the option to generate actions, Service Studio would check for a defined custom pattern. If found, it would generate the actions based on that template instead of the default OutSystems standard. Key Capabilities: T emplate Definition : Define a standard flow for Create, Update, and Delete actions. For Validation actions as well, for example would automatically check if the mandatory attributes are not empty. Placeholder Support : Use variables for Entity names or attributes within the template. Boilerplate Logic : Automatically include logic like "GetUserId()" or "LogRecord" in every generated action. Architecture Alignment : Ensure all entities immediately follow the project's "Good Practices" without manual intervention. The Goal The goal is to move from "Standard Scaffolding" to "Architectural Scaffolding." This would significantly speed up the development of new entities, ensure the entire team follows the same patterns from day one, and reduce the technical debt caused by inconsistently wrapped CRUD Actions. Ultimately, both options would exist simultaneously. The idea is not to replace, but simply to add a new option.

I have a scenario where I need to search multiple modules so each time I search I open the module and then search and option so its time taking, my suggestion is if I search module Camera I select it and search another module like Common so it open only Common module. This would be solved by simply keeping like multi select user search for the module and selects the module he wants to open and then there a list presented below the selected modules with search box open until user done with selection and when user clicks on open then all selected modules should open. I think that would be a much easier UX, both to implement and to present to the user.

I propose the development of the Outsystems Advisor , a tool designed to ensure adherence to Outsystems best practices. This solution will provide personalized recommendations to optimize deployments across five key pillars : Cost , Security, Reliability, Operational Excellence, and Performance.

Hello everyone Basically I'm sugesting an identical wizard such as those that already connect to SQL Server or Oracle Cheers Francis

A mobile application that allows developers to join User Group events anytime, even when they don’t have their laptop. This makes event participation easier, increases accessibility, and encourages more developers to attend and learn from OutSystems community sessions.

Problem: Currently OutSystems ODC provides the User and access management API and Portfolio API to access the platform functionalities from code. However, connection is done via a custom consume REST Connectors, and they consume quite a lot of AOs to one's license (15+). This also Proposal: Connectors, that do not count towards the total AO count of a license. This could be achieved via a couple of alternative options: -an OutSystems-provided official connectors, that similarly to the System's libraries do not count towards the total AO consumption -unsupported custom Forge Connectors (like now), that have the option to be reviewed and aaproved by the OutSystems team, and they do not count towards the AO consumption -out-of-the-box way of consuming the APIs as part of the platform (inside System library Actions or similar)

As a Developer i want full insight in where my code is used. Right now it is not shown when my ServiceActions, Events or Screen are used in ODC Workflow. I would like to have this info added to my usages to get complete info on where my code is used.

When changing locale of a screen, in multi-lingual applications, everything is translated, except validation messages. The validation message is displayed in the right locale when triggered, however, if the validation message was already added, and then the locale changes, the validation messages are not translated to match the new locale. To translate the validation messages, the user has to trigger the form validation again.

Hi, Just published an app in O11 after undoing some steps. Then noticed that Service Studio automatically undid my undone and published a latest version without my changes and even without giving me a warning or an option to select. Please: Don't try to automate things that should not be automated. The developer should be the one in control at all times. Also, every time I publish, the laptop gets a bit unresponsive till it finishes. I don't know what was changed in this version but has some issues. Note that issues in copy-paste are on-going for several versions now. This might be because of some background processing for automations but are impacting when we need to copy text inside Service Studio (that doesn't get copied). Best regards, Miguel Garcia

Remove the GetUserId() in Client Actions and Screens to prevent client-side tampering. When developers use GetUserId() on the client side (Reactive/Mobile), that value is compiled into JavaScript. Anyone can open the browser developer tools, manipulate that ID, and potentially spoof another user. AI Mentor Studio already flags client-side GetUserId() as a security vulnerability because browser JavaScript can be manipulated. Instead of detecting this flaw later, OutSystems should remove GetUserId() from Client Actions and Screens entirely. By making it unavailable on the client side, new developers will be forced to use secure server-side session checks from day one. This shifts the platform from detecting vulnerabilities to preventing them, saving time on refactoring and ensuring apps are secure by design.