Most of the screenshots provided on the forge components are hard to ready because they are too small. It would be great if we could click and see a larger version of the screenshot.

Removing unused references is a great piece of functionality.It is a little blatant in its execution though. It would be nice to be able to view the unused references and then select/unselect the ones you do not want removed yet.As an alternative, in the Manage Dependencies window, show which selected references are not currently used by way of some indicator.The second option might be slighlty easier to implement and also would exist in precisely the place where teh developer is busy making choices about these things.The existing Remove Unused References would then remain as a reference cleanup tool rather than a reference management tool.

I suggest adding an arrow to collapse or expand code ranges in the JavaScript Editor, similar to the functionality already available in the CSS Editor. It would improve the usability when working with large blocks of 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.

Currently, the 'HTML element' widget does not allow de 'dialog' tag, which is valid HTML. The dialog tag is very useful to create modals, so it should be allowed. See Dialog Tag

History of changes to site Properties, having the possibility to know who and when changed the site property and consult previous values.

Service Studio, at this moment, only supports debugging using Chrome browser (Chromium base). The ("new") Edge, which is based on Chromium, could be another supporting browser to use the [Service Studio] debugger.

Some site properties represent passwords, it would be good to have their values masked in Service Center. There should be a checkbox on the Site Property in Service Studio to mark this option. J.Ja

Quality of Life Improvements in the ODC Deployment Cycle Dependency Overview, when deploying an end-user application, it’s helpful to see a detailed overview of dependencies that might compromise the deployment. While this is a valuable feature, it could be even more effective if it allowed direct interaction with those dependencies—such as clicking on them to initiate their deployment or making the process more seamless. Currently, if multiple core applications (e.g., 8 or more) must also be deployed, you need to manually track and list them, which can be cumbersome. Navigation During Deployment, if you decide not to proceed with deploying a specific application after selecting a revision, it would be useful to have an option to navigate directly back to the application selection screen via the left-side menu. At present, the process involves either restarting by going back to the “Deployments” screen or clicking "Back" multiple times, which is not ideal for efficiency. Improving Feature Toggle, managementFeature toggles are essential for enabling parallel development and hotfixes, aligning with best practices recommended by OutSystems. While it's possible to organize feature toggles using folders in the development studio, this structure doesn’t carry over to the cloud interface, where you manage toggle values. Improving toggle management in the cloud would significantly enhance deployment workflows, as it directly impacts the flexibility and control required during deployments. A last one that also goes hand in hand with the deployments are the secret settings that you might need for API's (just an example). Whenever you make use of a new settings or app that uses an existing api you will need to fill in the setting its value. Because they're secret and always filled in with a default prompt you can not tell that its value is already filled in and if it's filled in that it's correct. Obviously this is intended but it can make big deploys with multiple applications hard to manage. An easy way to fix this could be an 'updated on' field that shows when the value was changed if changed at all so you can easily see if you have already updated the value. Thanks in advance for all already made improvements. Kr, Owen

The exam application for Outsystems certifications doesn't have a time countdown.Since it's made inside the ProctorU's "SecureBrowser", you never know when it will end, because the application hides the system clock.Since you're not allowed to use a smartphone, you either have a watch or you're on your own figuring it out by the sun position.This greatly increases anxiety, examinees easily loose track of time.