Considering the fact that the cloud version does not support internal network for IP white listing, I think adding an extra layer of security to secure service center  with Two factor authentication should be a standard in the Outsystems platform.

Hey guys,I think it would be really helpful to have a new tab besides the TrueChange tab that shows the Architecture Dashboard report for the specific module we're seeing.Apart from being more accessible, developers can easily look at the report in the module scope and more proactively reduce technical debt.

OutSystems provides strong local debugging (breakpoints, step‑through execution) and logs, and in ODC it already supports distributed traces at a technical level. However, from a developer’s point of view, there is still a significant gap between raw observability data and actionable troubleshooting. I’m proposing a developer‑centric, end‑to‑end request trace experience that makes it easy to understand what happened for a single user action: from the UI event, through server logic, to database operations and external integrations, without manual correlation. Service Studio debugging works well within a module, but once a request crosses: UI → Server Actions Aggregates → Integrations Async flows / Timers developers must manually jump between: Debugger Logs Integration error screens External system logs This fragmentation slows down root‑cause analysis and increases support effort, especially for intermittent or environment‑specific issues. Logs show facts / data, but not context. Logs record events, but: Developers must manually infer which UI action triggered which server/integration call Correlating logs across layers requires custom correlation IDs or naming conventions Performance issues often require guesswork to identify the slow component Traces technically capture request lifecycles, but developers don’t yet have a single, intuitive “story view” of a request that ties everything together in a one‑click request trace view that: Starts from a user action (e.g., button click, screen load) Shows the full execution chain across: UI action Server actions Aggregates / queries Integration calls Async operations (where applicable) Presents timing, failures, and context in a single timeline This is not about adding more logs, but about connecting existing observability data into a developer‑friendly narrative.

Allow server actions and integrations (e.g. AI use cases) to stream text to the UI instead of waiting for the full response. This is standard on any AI powered app and since OutSystems is pushing AI features, I think this is a must have. We don't want our users to have to wait for the full LLM response before having some feedback. A way to implement this is to allow Server Sent Events which would even facilitate other use cases, especially in ODC with Event Driven Architectures.

Hello, It's completely fundamental to have a way/tool to migrate App/modules from Reactive to ODC. Right now it's a big bottleneck as we can't open modules created in Service Studio in ODC studio. Will be impossible to convince customers to migrate Apps from Reactive to ODC if the process is no simple and quite fast. Thanks, Paulo Torres

Aggregate should have an option to remove duplicates. I see this as a new tab like "Sorting" where you could select the column you want to remove duplicates.

I think it would be great if there were a way to point co-workers to a specific part of the code, for example as Architecture Dashboard does. This would be super helpful to have because we could show directly what part of the code we are talking about with a co-worker.

To monitor errors in Service Center, having the kind of exceptions that have been raised could be very helpful. The exceptions are already on the error log but not their Type, for example, "Database Exception", "Security Exception" and for User Exceptions, it would be very helpful. Should have filters / categorized.

Inside an aggregate comparing the same variable (inside a filter) should trigger a warning. If an aggregate filter says user.id=user.id it should trigger a warning clearly this will always be true. the user would have likely meant user.id=userid

Would be great to have a simple option to set the destination as a new tab rather than existing tab (maybe a dropdown as the image below). This is particularly useful in client actions, there are work arounds to solve this but require actions to check environment or current domain and these are always harcoded in some way.