It would be nice to have a way, in ServiceStudio, to select two actions at a time and compare the code like we have in the merge eSpace at the action's level.This could be a useful feature for code cleaning and reusability (easier to track duplicated code).

 Issue: The Table Grid component in OutSystems is currently missing several helpful features found in the Data Grid, including the column picker. As a result, developers frequently resort to the Data Grid solely for offering column customization features, even though the Table Grid would be more suitable for less complex scenarios. Moreover, the Table Grid lacks a native feature to establish row gaps (spacing between rows), which would enhance readability and visual aesthetics in numerous situations. Concept: Upgrade the Table Grid feature by incorporating: A column selection tool enabling users to dynamically display or conceal columns. A row gap feature to manage spacing between rows for improved visual appeal and readability. Advantages: Lowers the necessity to utilize Data Grid for straightforward use cases. Enhances user experience via personalization and improved layout management. Maintains lighter pages that are simpler to manage while providing increased flexibility.

Hi team,It would be good if we could have any certification for Testers in Outsystems as we already have a course for tester: https://www.outsystems.com/training/paths/10/becoming-a-tester-in-outsystems/This will give the sense of confidence to client as they have capable and aligned team with respect to low code.Thanks,Preeti Kumari

Hi, I have an idea to simplify email development in OutSystems a screen to preview email's HTML with dynamic data directly in the browser. the goal will be, Allow us developers to see the final rendered email (with parameters) in a browser during development. Benefits: Speeds up email design & testing. Easy debugging of layout/data issues. Can be reused as a live “View in Browser” link if needed. Best Regards, Faiz Khan

A no-brainer: having the possibillity in the Expression Editor to click on a true or false button to have the text.Just like you have now with the null identifiers.Yes, its lazy but that's the common thread with developers :)

When I see some courses that I would like to take but at that time I don't have time. I can save or book that course[fig1] and then when I go to see the courses [fig2] to be taken you could find a checkbox of the courses that I also marked Fig1 Fig2

Add a field Timeout on the tab Integrations on Service Center, this way I don't need to publish by Service Studio and Deploy the module to another environment.

Currently, the Service Studio CSS editor does not recognize "@layer" directives (notice the warning and the missing syntax highlighting on my ".test" class. Layers are a part of CSS and already mostly supported in all browsers. Althought this does not impact atual usage, it would be nice for it to be supported in the code editor. This could be as easy to implement as updating the underlying editor (I think it's Monaco Editor )

In the version Version 11.54.82 / Build 63748 there is a new warning, Unused Resource, Resource 'Resource' is never used. Consider deleting it. and the warning points to Resources->MyResources.zip. This resource is part of a mobile application, and the zip file contains all the icons (logos) used by the app. I recommend removing this warning, as an inexperienced developer might mistakenly delete it, causing future compilations to generate the application without its logos.

What do you need?Retry options for REST integrations. They should includeThe number of times a retry should be performed before failing.A duration of time (in seconds) to wait between each retry.Specify which status codes to perform retries on. For instance, you may want to fail immediately on 400 (Bad Request) or 401 (Unauthorized) but would like to retry on codes such as 408 (Request Timeout), 429 (Too Many Requests), 503 (Service Unavailable), 504 (Gateway Timeout) etc. This should be a list of status codes that can be specified at the developer's discretion. Potential Stretch Option - Callback for OnBeforeRetryAttempt to allow the request to fix a potential expected failure or log additional details for troubleshooting.What could it improve?It would increase the stability of REST communication and reduce application errors caused by transient errors on a REST API that the OutSystems developer may not have control over.Who would benefit from that?Anyone that uses REST integrations could benefit from this additional control.