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.

When I edit or look up data during development with 'View Data' in my entity, the order of the attributes are so random. I'm getting pretty crazy of scrolling and searching for my attribute and it's value. (Especially in my 225 attribute entity! Yes, I could optimize) Why are the attributes not ordered by the way you ordered them in the entity? or at least on alfabatical order? Seems like an easy fix. Also what decides if a attribute is collapsed or expanded? seems random also.

We would like to request the implementation of a Drag and Drop File Upload widget within the OutSystems platform. This feature would significantly improve the user experience by allowing users to easily drag files from their local system and drop them into a designated area for upload. It should support multiple file types and sizes, offer visual feedback during the upload process, and integrate smoothly with existing workflows. Adding this functionality would modernize the platform and align it with current best practices for user interface design

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.

Service Studio should provide more built-in icons for actions. Upload icons is a pain process and allowing developer to upload any kind of images polutes the code readability. If Service Studio could provide some icon options this could standalize the code flow. I would suggest icons for Private actions like: If this could be done automatically, it would be great.

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

We have a scenario where we set the default value of a structure attribute which is displayed on the UI. These default values are not picked up by the translation editor. Idea: add structure default values to the translation editor.

We work on projects we don't always have time to work on our own stuff and what does OutSystems do? You punish us for working hard and promoting YOUR product by deleting our personal environments. STOP IT. Why don't you figure out a way to determine if we are high-end enterprise users? If we are LEAVE our personal environments alone.

There is a limitation in mapping two structures with different types and one element is a list of any type. Service Studio doesn't shows the mapping function.We're only able to Map 1 level, as shown in the example below:The mapping should also work for inner lists elements of a structure.

 Problem Statement In ODC, a Client Secret is required in virtually every scenario where an app communicates with external systems or calls ODC Management APIs programmatically: UsersManagement (Forge) → ODC User & Access Management API External IdP integration (OIDC) → Azure AD, Okta, etc. ODC REST API calls → Portfolio API, and others External service integrations → Salesforce, MS Graph, etc. The current behavior is that Client Secrets expire every 90 days by default (maximum 2 years), and renewal is only possible manually through the ODC Portal. Root Cause of the Issue This is not merely an inconvenience — it is a structural constraint that breaks the promise of full automation in ODC-based services. Here is why: ① No programmatic renewal path exists There is currently no Management API endpoint to rotate or renew a Client Secret. This means that no matter how well-automated your app logic is (e.g., a Timer-based user management flow), the secret renewal step always requires direct developer intervention. ② Expiry creates operational risk at scale In production SaaS or B2C environments running on ODC, a missed secret expiry means: All features depending on that secret stop working silently or with cryptic errors End-users are impacted before the team is even aware Recovery requires Portal access by a developer with the right permissions — not something an end-user Admin can resolve ③ The expiry cycle creates recurring developer toil Even with the maximum 2-year expiry configured, and even with calendar reminders or monitoring in place, this is manual, recurring, high-risk maintenance. It runs counter to the Low-Code philosophy of ODC: reducing developer toil and enabling reliable, autonomous operation. Requested Feature(s) Please implement one or more of the following: Option A — Programmatic Secret Renewal via Management API Add a Management API endpoint that allows an authorized app to rotate or renew a Client Secret before expiry. This would enable a Timer-based auto-renewal flow entirely within ODC, with zero developer intervention. POST /api/v1/clients/{clientId}/secrets/rotate→ Returns: new_secret, valid_from, expires_at Option B — No-Expiry Secret Option Allow trusted, internal service accounts to opt into a non-expiring Client Secret, similar to how other platforms (e.g., Azure App Registrations, AWS IAM long-term credentials) provide this option with explicit acknowledgment of the security trade-off. Option C — Secret Rotation with Overlap Window Support a dual-secret validity window during rotation — where both the old and new secrets remain valid for a configurable overlap period (e.g., 24–72 hours). This enables zero-downtime secret rotation in production environments.