Currently, when viewing the version history of an item, selecting a specific version opens it in the current tab. To compare different versions, users need to first open the latest version and then manually navigate to the desired version. It would be helpful to add a context menu option (right-click) on a version entry, such as "Open in New Tab", allowing users to directly open the selected version in a separate tab. Benefits: Faster access to specific versions. Easier side-by-side comparison between versions. Improved user experience for reviewing changes and audit activities. Reduces the number of clicks required to navigate between versions.

For many times we need to check the history of changes to an action or screen, it is also interesting to compare with an earlier version. It would work with the following steps:1 - Click the right mouse button2 - Select the option to view the history3 - View the history with the name, modification date and an option to compare with the current version.Images1 - Option to view history2 - History window with the option to compare with previous versions

Create a Edit Button in this space for changing the Idea Title. In this moment if we make an error when we create a new idea we don't have the opportunity to correct. Its my new suggestion. Best Regards, Paulo Russo.

Just as all other elements, the custom exception could be public so that on consumer espaces you can have error handling for specific custom exceptions of the producer espaces. Showing what kind of exceptions are thrown in the tooltip of a user action would also be a good improvement

While learning and working with JavaScript inside OutSystems, I experienced a situation where an error in my JavaScript code was not indicated while I was writing it. For example, I declared an array using const and later tried to assign a new value to the array variable. I was not aware that this was an error, and the JavaScript editor did not provide any indication while I was writing the code. I only encountered the error when I tried to publish the application. As a developer who is learning JavaScript, it was difficult to identify the mistake without immediate feedback. My suggestion: It would be very helpful if the JavaScript editor in Service Studio could detect common JavaScript errors while the code is being written and indicate them visually, for example with a red underline or error marker. Hovering over the marked code could also display a short explanation of the error. This would allow developers to identify and correct JavaScript errors immediately instead of discovering them only during publishing. I believe this would improve the development experience, particularly for developers who do not have extensive JavaScript experience.

The availability of the Trace API download functionality, currently supported in OutSystems 11, should be extended to OutSystems Developer Cloud (ODC). We already have "Traces" at ODC portal that contains useful information when API fails , however doesn't have the request and response payload. This level of detail is a critical asset for development and troubleshooting. It enables faster debugging of API issues by allowing developers to verify payload correctness, understand provider errors, and ensure that the application complies with contract expectations (all of which are hard to validate without full trace access) Additionally, since OutSystems 11 already offers this functionality, bringing it to ODC would ensure consistency for teams migrating or working across both platforms, improving developer experience and efficiency.

It's been years since dark mode was introduced, yet the icons in the list are still barely visible in Traditional. Could we make the icons the same color as the text or change the widget for the one in react? Previous image is traditional icon selection. previous image is react icon selection.

Allow changing variable values while debugging

Our profile page has an Achievements section. While it is OK for regular users, some community members are too active in the forum for that to be searchable. That page becomes useless after a hundred entries. Can we have a filter like in Activity tab?

 Current Situation When working on an application with multiple developers and multiple published versions, it can sometimes be difficult to understand exactly what changed between a previous version and the currently published version. OutSystems already provides version comparison capabilities, which are useful for inspecting differences. However, when a module contains many changes, developers may still need to manually go through different elements to understand the overall scope of the changes. I would like to suggest adding a “ View Changes ” option when opening a previous version of a module. For example, when selecting a previous version from “ Open Other Version ”, there could be an option such as: View Changes This would automatically compare the selected version with the currently published version and provide a clear, consolidated summary of all the changes between those versions. What Should Be Included? The change summary could cover different levels of the module, for example: UI / Screens Screens added, removed, or renamed Containers/widgets added or removed Container/widget names changed CSS classes changed Widget properties modified Screen Actions/Event Handlers added, removed, or modified Client Actions Client Actions added, removed, or renamed Logic modified Input/output parameters added, removed, or changed Variables added, removed, or modified Dependencies/references changed Server Actions Server Actions added, removed, or renamed Logic modified Input/output parameters changed Variables added, removed, or modified Dependencies/references changed Data / Entities Entities added or removed Attributes added, removed, or modified Data types changed Relationships or other relevant properties modified Module-Level Changes Module properties changed Public elements changed References added, removed, or updated Dependencies changed Other relevant module-level configuration changes Example If the current published version is Version 100 and a developer opens Version 95, clicking “View Changes” could display something like: Changes from Version 95 → Version 100 Screens ✓ HomeScreen - Container "MainContainer" renamed to "DashboardContainer" - CSS Class changed - New Button added Client Actions ✓ RefreshData - Logic modified - New input parameter added Server Actions ✓ GetCustomers - Aggregate modified - New filter condition added Entities ✓ Customer - Attribute "Status" added - Attribute "IsActive" changed References ✓ CustomerAPI - Reference updated Ideally, each change could be clickable so that the developer can directly navigate to the affected element and inspect the detailed difference. Why Would This Be Useful? This would be particularly useful when: Debugging : Developers can quickly identify what changed between two versions instead of manually inspecting the entire module. Code reviews : It provides a quick overview of the actual changes introduced between versions. Maintenance : Developers can easily understand when and where a particular change was introduced. Troubleshooting : If an issue appears after a particular publish, developers can quickly identify the relevant changes. Team collaboration : It becomes easier to understand changes made by other developers. Large applications : It reduces the effort required to inspect changes across complex modules. Overwritten changes : Sometimes a developer may unintentionally overwrite or replace existing code/logic while making changes. In such cases, being able to quickly see what was changed compared with an earlier version would be extremely helpful as a reference for identifying what was overwritten or modified. Rollback decisions : Before reverting to an older version, developers can clearly understand what changes would be affected. Related Existing Ideas / Clarification Before posting this idea, I searched the OutSystems Community to make sure there wasn't already an existing idea covering the same requirement. I found the existing idea “ History of change in Actions and Screens and compare with previous versions ”, which focuses mainly on maintaining history and comparing changes for individual Actions and Screens. There are also existing discussions around comparing a module with a previous published version, as well as functionality related to publish/change comments. However, my understanding is that the proposed idea is slightly different: The goal is not simply to compare two versions, but to provide an automatically generated, consolidated “View Changes” summary covering the entire module. This could include Screens, UI elements, Client Actions, Server Actions, Entities, References, Dependencies, and module-level changes , all in one easy-to-understand list. The existing comparison functionality could still remain available for developers who need detailed inspection. The proposed “ View Changes ” feature would act as a high-level summary layer on top of that , making it much easier to understand the overall changes between two versions. This is why I believe this could complement the existing version comparison/history capabilities rather than duplicate them.