Like we set the Site properties using Service center, there should also be a provision where we can update the Multi language from service center also. One more Tab should be Added in service center as per module, which should have the list of uploaded versions of Translations. User can download the Template and upload it.

Just like O11 Service Studio, it would be great to have an auto-update feature in ODC Studio as well under preferences. This would streamline the upgrade process and ensure consistency across tools.

It is already possible to create a structure from JSON.It would be useful to get the opposite: the JSON for a given structure.The feature would be something as: right click on a structure -> see in JSON format. Or something similar.Sometimes it is useful to pass a serialized structure to parse in Javascript, for instance...

It would be great if OutSystems exposed REST APIs supported multiple response types, instead of just one type (structure).In swagger, you can set a response type for each status code and have different structures for each one and all the different outputs are then properly documented.Something like this:responses:        200:          description: An array of products          schema:            type: array            items:              $ref: '#/definitions/Product'        default:          description: Unexpected error          schema:            $ref: '#/definitions/Error'This would give:- more flexibility when creating exposed REST APIs;- multiple response types support in the "OutSystems way";- better documentation, including all the response types available;

My idea is to improve current List Navigation widget, which imho is not intuitive neither informative and takes too much valuable space for redundant or no use functionality.Why a button with (...) that has no action?Or page numbers for Prev/Next pages when we already have Previous and Next buttons?How do we know how many pages are there?How can we get back to first page? Existing List Navigation widget:My idea is to keep Previous and Next, add a First and Last Page button, highlight the current page and in between have a (...) button to enable navigation to one of those pages in between.This could apply only to lists with >= 10 pages. Up to 9 pages just buttons with page numbers would be enough.Suggestions to improve on this are welcome.

Ability to input an expression while the debugger is running and have it evaluate it and display the results.

Hi,In Outsystems we have a concept called Applications that are a group of modules that are grouped.To be compliant with Outsystems architecture it's normal to have 2/3 applications that refer to the same business application (as you can see in the image).To allow better governance I suggest creating a new concept called cluster that will improve:Log analysis by business applicationDependencies by business applicationData flow by business applicationTechnical debt (AD) analysisArchitecture reading

Enable developers to upload a JSON file in OutSystems to automatically generate a REST API consumer, including methods, structures, and data types. This feature simplifies integration setup, reduces manual configuration, and accelerates API onboarding.

Idea Summary: Enhance the resilience of the OutSystems UI Date Picker widget initialization, specifically when testing mobile views using Chrome DevTools' device simulation. Currently, the widget does not always reinitialize properly after a hard refresh in this environment, potentially leading to confusion during development and QA. Issue Description: When simulating a mobile device in Chrome DevTools and performing a hard refresh, the Date Picker widget occasionally fails to initialize correctly. This behavior appears to be due to: JavaScript/UI libraries not consistently re-triggering widget initialization in simulated environments. The use of dynamic selectors (e.g., .active, input.form-control.OSFillParent.input.active ) in the widget’s initialization logic, which may not be immediately available after a refresh. Key Observations: On actual mobile devices (e.g., Safari on iOS), the widget functions reliably, even after refreshes. In Chrome DevTools mobile simulation, the widget behaves correctly on initial load or when toggling to mobile view but fails after a hard refresh. Impact: Creates confusion during testing and QA phases. May mislead developers into thinking the widget is broken. Increases friction when debugging using browser tools. Suggested Improvements: Make initialization more robust in simulated environments. Avoid dependency on dynamic class-based selectors that may not exist immediately on load. Implement fallback logic or explicit reinitialization to handle DevTools mobile simulation scenarios. Thanks, Senthil

It would be highly beneficial if OutSystems could provide a readable, structured summary of code changes between two versions of a module or between two deployments across all modules in an application. This feature would significantly streamline the code review process by clearly highlighting what has changed and where to focus attention. Building on the existing comparison capabilities in Service Studio, this enhancement could present the findings in a logical, human-readable format—making it easier for developers, reviewers, and stakeholders to understand the scope and impact of changes. Furthermore, by leveraging AI, the platform could generate context-aware summaries. For example, if a deployment includes a new report, timer, or transaction flow, the system could automatically detect and describe the functional changes, and optionally generate a flow diagram to visualize the logic. This would not only aid in code reviews but also support documentation, onboarding, and audit processes. Such a feature would promote efficient code management, better collaboration, and faster quality assurance cycles.