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.

I would like to suggest a feature that allows developers to navigate directly from a UI element in the running application to the corresponding element in OutSystems Service Studio. Current Challenge When debugging or making changes to an application, developers often need to identify which screen, container, widget, text, button, or other UI element is responsible for a particular part of the application. Currently, developers may need to manually search through screens and UI hierarchies in Service Studio to locate the corresponding element. This can be time-consuming, especially in large applications with complex screen structures. Proposed Solution Introduce a “Open in Service Studio” / “Go to Source” option for UI elements. For example: Run the application. Select or right-click on a UI element, such as a Text, Button, Container, or Input. Select “Open in Service Studio” or “Go to Source.” Service Studio opens the corresponding application and screen. The selected UI element is automatically highlighted in the widget tree. Example If I see a text on the application: “Customer Details” I should be able to select that text and choose: Go to Service Studio → Service Studio would then open the relevant Screen and automatically select the corresponding Text widget. Additional Possibility This could potentially be implemented through a debug/developer mode, so the feature would only be available to authorized developers and would not expose development information to normal end users. It could also work for: Text Buttons Links Containers Inputs Images Lists Forms Other UI widgets Benefits Significantly reduces debugging and navigation time Makes it easier to understand existing applications Helps developers quickly identify the source of a UI element Particularly useful for large and complex applications Improves the overall developer experience in Service Studio Makes UI troubleshooting much faster Suggested Feature Name “Go to Source” – Navigate from UI Element to Service Studio I believe this could be a very useful productivity feature for OutSystems developers, especially when working with large applications and complex screen hierarchies.

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?