The server seems to be storing all date/time in UTC format. However while reading the errors/logs and other details in Service Center, the UTC format makes it difficult to comprehend (if the user is in different timezone than UTC). May be we can convert to user's local timezone and display the date (how it happens in react client side).

When working with popup's in service studio for a reactive application, they overlap with the screen they are used in. On the forum is a great solution for this problem -> https://www.outsystems.com/forums/discussion/55208/zoom-in-or-out-feature-on-interface-outsystems-service-studio-11/ Why not make it part of a next version of outsystems ui, so everyone has this solution at start ?

Hi,MABS Version has become an important aspect that need's to be clear while anyone of forge comes & download the Mobile Plugin.Most of the developers has been started to struggle on MABS version as of the plugins are not yet been upgraded.To address the issue, at least outsystem can give a way by which a Plugin Owner can specify the supported MABS version. Same like it highlight the supported Outsystems version.Please provide a separate field to mention the MABS version while uploading the plugin.

Premise: When projects and team dynamics become complex, people end up having to maintain reverse-engineer code, often with little or no documentation. Idea: Any action in ODC Studio would have an "AI Summarize" option. This will do an AI Analysis of the action, including analysis of all of the consumers of that action, and produce a human-readable summary of the action. Target: This could transform the 'maintainability' category of AI Mentor into a mostly automated feature.

In multiple enterprise conversations, a recurring concern I encounter is around long-term platform dependency and source code ownership. Prospective clients often ask whether, in a worst-case scenario or strategic pivot, they would have the ability to access and operationalize their application source code independently of the platform. To address this more effectively during pre-sales and architecture discussions, it would be extremely valuable to have a feature in the trial or demo environment that allows export of the application source code in a structured .NET format that can be deployed in a standard .NET setup. Having the ability to demonstrate this live would: Instantly reduce perceived vendor lock-in concerns Increase architectural confidence among CTOs and enterprise architects Accelerate decision cycles during evaluation Strengthen positioning against traditional custom development arguments In many cases, the hesitation is not about capability; it is about control and reversibility. If we can showcase that portability exists in a tangible way, it materially improves conversion confidence. This capability would significantly enhance enterprise adoption conversations.

When utilising forge components in a project, these modules can add to the project's overall technical debt, particularly in security and performance. Sometimes, modifications may be required for these modules if issues arise in these areas before they can be released to higher environments. It would be beneficial if the forge could display each component's AI Mentor Dashboard score (level of tech debt). This would assist in identifying high-quality components, especially when similar components are available. Additionally, it would incentivise component authors to improve their components.

At the moment the maximum length of an action name is 50 characters. This is way too small for having effective and readable names.You end up truncating names which has a negative impact of readability, maintainability.So please increase them by a lot. at least 255 characters.

When perfform a release via LifeTime, in case dependent applications need to be published. But you don't always want this.In large factories, it's a lot of work to unselect all dependent applications.As select/deselect all button would be a nice feature.

Currently "da - Danish" is missing from the OutSystems UI library. As mentioned in this thread https://www.outsystems.com/forums/discussion/57768/outsystems-ui-allows-for-translations-on-outsystems-ui-widgets/ we can not add this ourselves, so we hope this can be resolved by the OutSystems team.

Hi,It's not easy to see how many OutSystems accounts are associated with my Architecture Dashboard. As a new infrastructure admin, I want to be able to see who was added in the past. For security, I need to know which users have access to my Architecture Dashboard, when they were created, and by who. Then I can decide how to clean-up the IT Users in LifeTime.This Associated Users list could be shown on the Maintenance screen.Example UI attached: