A module in Service Studio will register a "change" when viewing data from an entity in some contexts, requiring the developer to either re-publish or to click "Don't Save" when closing the module: If a developer is only viewing data, no changes have really been made, right? I would prefer not to have to click this "Don't Save" button. Below are the different contexts I tested and whether a "change" occurred as a result. Option 1: "View Data" on a static entity on element defined in the module Result: no "change" Option 2: "View or Edit Data" on a regular entity on element defined in the module Result: no "change" Option 3: "View Data" on a static entity that is being consumed from another module Result: a "change" occurs Option 4: "View Data" on a regular entity that is being consumed from another module Result: a "change" occurs

I'm not sure if there is already an existing idea like this, the search didn't provide me with a match so I'm creating one...We have the ability to import a swagger 2.0 rest services already, but unlike its SOAP counterpart we lack the ability to do this locally from a fileThis should be added IMHOBest regards,PC

I would like to see an accelerator in SS (and ODCS) where we could choose to create a timer based on the below template according to the best practices to ensure Data Integrity, Timeout Prevention, Completeness and Doesn't Repeat Work. One could customize it afterwards to his needs or simply choose the current option to create a timer with an empty canvas. The accelerator should also include a "KillTimer" Site Property in the flow to ensure there's always a way to stop a timer when needed.

Greetings, I noticed it is possible to post questions on the OutSystems forum with just 3 characters in the title and description. This often leads to unclear posts that lack enough detail for the folks to answer. Having a rule like a minimum of 15 characters for the title and 30 for the description would encourage users to write clearer questions. It’s a small enhancement , but it could make a big difference in the overall quality of discussions. Addtionally the same could applied for discussion & Idea secion :) Best Regards, Assif

Similar to when I drag a screen action to the screen and OutSystems automatically creates a button on the screen, it would be nice to drag a client action and have OutSystems create a wrapper screen action (that calls that client action) and a button on the screen

An AI agent that acts as a "Guardian" for our Data Fabric. When a developer changes an entity (like changing a User_ID from a LongInteger to Text), the AI scans not just the OutSystems code, but also the "Contracts" with external tools like Power BI, Snowflake, and external APIs. It warns the developer before they publish: "Stop! This change will break the 'Sales Dashboard' in Power BI." Real-World Example Imagine we have an OutSystems app for Order Management. We decide to change the Price field from a Decimal to a Text (maybe to support currency symbols). The Internal Impact: OutSystems tells us to fix the math formulas in the app. We fix them. 0 Errors. Happy! The Hidden External Impact: * Power BI: A "Revenue Chart" was pulling that Price field. Now it crashes because it can't "Sum" text. Snowflake: An automated data pipeline was expecting a Number. Now it rejects every new record. The AI Sentry Solution: Before we click "1-Click Publish," the AI pops up with a - "⚠️ External Impact Detected: The Price attribute is consumed by Snowflake Pipeline 'Orders_Sync' and Power BI Report 'Global_Sales'. These systems expect a Decimal. Changing this to Text will cause 2 downstream failures. Do you want to notify those teams?" Low code tools that already address this issue - Atlan - Automatically maps how a change in a database affects a dashboard in real-time. Informatica (CLAIRE AI) - Uses AI to predict the "blast radius" of a metadata change across different systems. Collibra - "Harvests" metadata from different tools (SQL, APIs, BI) to show a visual map of dependencies.

I'd love to have a ListSplit System Action, that performs a ListFilter, but also outputs all the other elements in a second list. So say I have a List with an Attribute "Value" and the input to ListSplit is "Value > 1000", I'd get two lists, one with all Values upto 1000, and one with all Values above 1000.

The ODC was stupendous!!! Good Job OutSystems CrewBut I propose that Outsystems make the presentations available  to the comunity.Besides that it is not possible to attend to all presentations due to the parallel sessions

right click on "output structure" >> Create the output structure (in advanced queries) based on the select statement

Outsystems portal need to add some loaders, I click on buttons it takes much time to see any interaction in system that causes I click many times on it. it's given me negative imprecision and bad UX. also in create Case Screen error raised Twice, one during writing case details other after clicking next