The ability to clone an extension would be a really really nice-to-have. :-)

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

I think that the line number where an error ocurrs, could be useful.

It whould be nice to have an overview of all available actions and webservices in Service Center, something like a 4GL dictionary. This would give an overview of Built-in actions all public actions in Sollutions all webservices references of all eSpaces / Extensions and its function (UI / Business layer / Integration Layer) This is also the place to functionaly describe these actions/services

It would be nice to configure the header color of Service Center.This way, it would be possible to have a different color for each environment.As a suggestion, this could be set in "Administration -> Environment Configuration" and accept a hexadecimal code or named color.This is how it would look like: Development Environment Test Environment User acceptance testing Environment Configuration

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.

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.

Show who are the users online and currently working in this shared environmentThis future will be really useful to improve joint working culture.If the user is publishing then it will show their status as publishing.If they just working on it then it will show their status as online.If the user is not using the environment then it shows his status as Offline.It will help other users in the shared environment to avoid publishing at the same time.

Very basic and simple ideia, just what the title says: Reminders could have a different color than regular comments (orange?)Some complex logic often gets several comments on it and this would help to rapidly identify the reminders/todo/WIP from the "documentation"

Hi OutSystems Team, In the OutSystems Support channel , implement a time tracking rule based on SLAs , as some clients use this metric and end up counting elapsed time, which is incorrect. When the issue remains on the client's side, the SLA should not count, or if the client "disappears" and does not close the ticket, this time should also not be counted. This helps OutSystems protect itself from misunderstandings and potential penalties (fines) from the client, which could lead to misinterpretations. The current view considers tickets as either open or closed. Time tracking helps with OutSystems' resolution metrics and protects the company from other interpretations and metrics. It would be beneficial if this data were exported along with the ticket ( spreadsheet generation ).