Currently, it's only possible to sort and filter in the ViewData Editor in Service Studio, and it shows the top X rows. Please add pagination to this view.

Add something similar to "Export Action To Image" but with the actions objects numbered and a section below listing the parameters for each one . Also, a way to generate these in bulk , with it generating a zip file with them all inside, named appropriately, or as a PDF file.

As part of our ongoing effort to follow OutSystems best‑practice architecture, we have restructured our application landscape to clearly separate business logic from front‑end applications. While this approach improves modularity and maintainability, these applications still have interdependencies, which we group and manage as a logical Suite. When deploying to another environment using Lifetime, all module dependencies are automatically validated and republished as needed, and we are proactively notified of any breaking changes across dependent applications. This capability significantly reduces deployment risk and ensures consistency across the suite. It would be extremely valuable to have a comparable feature in Lifetime that allows us to publish a Deployment Plan within the same environment, while still performing full dependency validation. Ideally, this process would identify broken dependencies, prompt corrective action, and automatically republish all dependent applications as required. Implementing this capability would result in substantial time savings for developers. Today, deploying changes within the same environment often requires manually opening and publishing multiple modules in the correct order, with limited validation feedback and a high risk of human error. A unified, dependency‑aware deployment mechanism would both streamline this process and strengthen application stability. While we have implemented a workaround using Solutions in Service Center, it does not provide the same level of validation and dependency checks that Lifetime performs during cross‑environment deployments. Closing this gap would significantly improve deployment efficiency, reduce rework, and enhance overall application dependency management.

 Problem: Even after years of development, maintaining consistent code quality across large teams is a persistent challenge. Despite the existence of best-practice documentation, junior and even senior developers frequently bypass critical standards—such as proper documentation, naming conventions, Max. Records settings, or inefficient operations like lists within loops. Currently, code review is a manual, reactive process that happens too late in the development lifecycle. Proposed Solution: I propose a new "Governance Gatekeeper" feature for Service Studio, powered by existing AI Mentor capabilities, that moves code quality from "suggestion" to "enforcement." Policy-Driven Publishing: Allow Admins to configure a set of "Strict Quality Rules" for specific modules. If the modified code fails to meet these pre-defined standards (e.g., missing descriptions, non-compliant naming, or performance anti-patterns), the 1-Click Publish button is disabled, preventing the deployment of substandard code. Granular Control: Provide the ability to toggle these restrictions on or off per module or application. This allows organizations to apply strict "Production-Level" enforcement on core systems while maintaining flexibility in "Sandbox," "Learning," or "PoC" modules. AI-Powered Feedback: Integrate the AI Mentor to not only block the publish action but to provide a clear, real-time "Action Plan" telling the developer exactly what needs to be fixed to unlock the publish button. Impact: By integrating automated enforcement into the development loop, we can: Guarantee Technical Debt Reduction: Prevent bad patterns from entering the codebase at the source. Scale Mentorship: Use the platform to train developers in real-time, effectively automating the role of a lead developer in enforcing standards. Elevate Enterprise Reliability: Ensure that all production-bound code meets a uniform level of quality, documentation, and performance before it ever hits the server. Thanks

We work on projects we don't always have time to work on our own stuff and what does OutSystems do? You punish us for working hard and promoting YOUR product by deleting our personal environments. STOP IT. Why don't you figure out a way to determine if we are high-end enterprise users? If we are LEAVE our personal environments alone.

Currently in OutSystems, developers often need to wrap widgets inside a Container or an If widget just to control their visibility. This makes the UI tree more complex and adds unnecessary nodes. Proposed Solution Add a “Visible ” property directly on all widgets. Accepts a Boolean expression No need to wrap the widget inside Containers or If widgets Works for all widget types (Text, Input, Button, List, etc.) Automatically hides/shows the widget based on the expression Example Visible : User.IsAdmin = True The widget is only visible if the expression is true — without adding a Container.

I think there should be a reset button that allows users to reset questions to default, remove the answers so that users can try answering the quiz questions again after coming back to review the material.First time i made some small mistakes, and now after 3 months i want to test my knowledge and i can't do it because the questions are already answered. Do i have to make a new account?

Rank the badges on the certificates, instead of just showing them by date. Put the expert/Professional badges at the top, making them bigger, possible with a line under that section, and don't show the lower "Associate" certifications that they supersede, or put them smaller at the bottom: (They are only at the bottom in this example because I passed them first.) Thus:

Today is only possible to search an application by name. But would be nice to have some kind of filtering too. Today I missed a way of filtering by type (web, mobile, service). Also for example hide the applications that came from forge. But for sure there is a lot more filtering that we can use. Would be nice to discuss around this topicAnd image to be clear the screen I'm talking about:

I am suggesting the addition of an IsAsynchronous parameter ( non-mandatory, set to False by default ) on the Refresh Data UI Flow Screen action, to tell the Refresh Data block to run the given Data Source in either an asynchronous or synchronous way, depending on the value of that input. This will spare the work of creating dedicated screen actions to refresh the Data Sources separately in a Screen Action to conceive a pure asynchronous Data Source Refresh, when applicable. Best regards!