In ODC - we should have the option to add a folder to app applications into it. Then when deploying you just select that folder with the multiple applications in it and that folder will then queue each application one by one to deploy. If there are warnings or errors on the deployment then it should warn the user. But the whole process of deploying single applications at a time is not very friendly. I do not think that by having the folder you will change the architecture. It is just automating a process

The AI Mentor Studio is already very powerful but we always look for new ways to make it even more helpful. Currently, alerts are assigned to the last person who modified an element. However, in some cases, the alert is triggered due to changes made by someone else. Adding an option to manually reassign alerts would help ensure they are directed to the most relevant person. Hopefully these suggestions will be taken into consideration :) Cheers, Vanessa Espírito Santo

I would like to suggest an improvement to the "Apply Settings to the Factory" notification displayed in the Service Center when there are pending configurations. Currently, this notification only informs that changes need to be applied, without specifying who made the modification or what configuration was changed . This creates a lack of traceability, especially in collaborative environments where multiple people manage configurations, making it unclear who performed the last modification. Suggested Solution: Display the User – Add the name of the user who made the last pending change to the notification. Detail the Modified Configurations – Include a summary of the changes made or provide a link to a change history screen. This improvement would enhance transparency, security, and efficiency in platform management, preventing conflicts or unintended configuration applications. Best regards, Valdemiro Veigas

In O11 we can end other debugging sessions by republishing the module. However, this does not work in ODC. It would be nice if there is a button next to each "active session" in the Users section of the Debugger tab in ODC Studio. With the click of the button, the debug session of the other account would end. This way, we can make sure that the app continues running normally without hitting the debugger activated by other accounts, in case the other users are unable to end their session. Security-wise it would be nice to give this option only to organizational accounts with elevated roles, e.g. the tech lead role.

If a developer uploads a forge component, that has dependencies for other forge component, and that component is owned by another developer. When changes is applied to the dependencies like: discontinuing the consumed version, uploading a new version to fix issues, ... etc. Let the consumer know that changes had been made, to upload new version of their asset if needed.

It would be good to have CRUD Wrappers for Local Entities as we have for Server entities

Ultimate Goal: This application has the ultimate goal to reduce chaos through the population and help sort who should and who shouldn’t go to the hospitals.Drivers:On March 16th, 2020, in Portugal, there were 331 confirmed cases. From these, only 29 had breathing difficulties, therefore, only 29 persons needed hospital assistance.Doctors and nurses are among the most infected segment and as time goes by, less and less will be available to help people at the hospitalsHospitals are running out of tests, therefore the screening is increasingly importantHospitals are already overloaded and as people are getting more worried, and with the exponential growth that is happening, hospitals tend to be even more overloaded.Linha de saúde 24 is getting overloaded and it won't be enough to answer all the calls.This app would be a mobile one, where every family would be able to insert:Family member detailsMeasurements (pain/no pain, body temperature, etc.)Medication takenEach family member should be able to add some measurement records. According to that, and following the Saúde 24 script, they would be suggested to:Do nothing as everything looks OKTake some medicineSend an email do Saúde 24Make a phone call to Saúde 24Online chat with a doctor or nurse that can help themMore information (details and risks shared in the attachment)

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

In service studio versions prior to version 9 it was possible to select/deselect all differences to merge at once, by clicking on the top checkbox in the list of the Foreign eSpace. That checkbox is no longer present in version 9.It would be great to have this feature back.

Propose the development of a robust server-side CAPTCHA validation component to enhance security and prevent automated bot submissions, as currently we don't have any OutSystems-supported CAPTCHA component available. Most existing CAPTCHA implementations rely on client-side validation, which can be bypassed, leaving applications vulnerable to spam and malicious activity. A server-side approach would ensure secure verification, improve application integrity, and provide stronger protection against automated attacks. This component should validate CAPTCHA responses on the server, integrate seamlessly with popular CAPTCHA services, and offer easy configuration through a developer-friendly interface and reusable blocks. Additionally, it should support accessibility standards and multi-language options for global deployments. Benefits: Enhanced security against bots and spam Protect sensitive forms and transactions, boosting confidence in the platform Developer-friendly implementation with reusable components