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

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.

In some scenarios, we receive the Id from an API as a text data type, and we need to use it to filter records in an Aggregate. To handle this, we convert the text to a long integer using TextToLongInteger() and then to an identifier using LongIntegerToIdentifier() to match against Table.Id. However, this conversion occasionally fails, especially in the production environment . In such cases, the Aggregate filter fails to return the expected results, likely due to type mismatches or runtime issues with the conversion process. This inconsistency makes it challenging to filter data accurately when dealing with dynamic or external data sources Please consider improving this feature by adding native support for safe and consistent type conversion within Aggregates. This would help ensure reliable filtering, especially when working with dynamic or external data sources, and reduce unexpected issues in production environments.

In O11 , when you copy logic, screens, or any other elements from one ( source ) module and paste them into another ( destination ) module, any external references used by the copied elements of the source module are automatically added to the destination module. This is quite helpful sometimes, especially when you are trying to copy screens/logic from one application to another (I had to do this a bunch of times in the past, for various reasons). However, in ODC , this is not the case. Once some elements (referencing some dependencies) are copied from one module to another, none of the references are automatically added (unlike in O11 ). This results in hundreds of errors sometimes, which could be reduced to just a few if automatic dependency referencing worked like in O11 . It would be great if this automatic dependency referencing is added to ODC as well, unless there's a valid reason for excluding this feature in ODC . Thanks in advance, looking forward to hearing about others' experiences and feedback :)

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.

Add the "show password" icon in the password field for admin users only

When an input parameter is removed from an action in OutSystems, the platform should automatically remove all references and assignments of that parameter throughout the application to maintain consistency and prevent warning.

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