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

In each training video on the OutSystems learning platform, include a “Schedule Call with Mentor” button (as shown in the attached image). When clicked, it can redirect learners to the ADP mentor list, allowing them to easily schedule a mentorship session. For freshers, this feature would be extremely helpful to learn faster, clarify doubts instantly, and gain confidence in their learning journey. Currently, many newcomers know about the forum, but not about the mentorship program. By placing this button directly within the training page, it encourages them to explore and connect with mentors proactively.

Problem: Personal Environments cost OutSystems unnecessary AWS compute time, but deleting them frustrates developers who lose their apps unless they manually export them. Idea: Make Personal Environments ephemeral but with automatic daily app snapshots, so they can be safely deleted sooner without hurting the developer experience. How it works 1. Daily App Snapshots Automatically snapshot all apps/modules once per day. Store snapshots in cheap object storage. Only snapshot OML + metadata (default: no DB data). Developer never loses their apps again. 2. Faster Environment Recycling Only do this if needed to offbalance the data usage in point 1 Reduce always-on uptime from 7 days to 4 days. After 4 days of inactivity: Kill the AWS compute Keep the daily snapshots 3. Auto-Restore on Spin-Up When a user requests a new Personal Environment: OutSystems spins up new infra Automatically reinstalls the most recent snapshot Developer resumes instantly with their apps already there Benefits For OutSystems AWS savings (compute reduced from 7 to 4 days). Storage cost minimal vs. compute cost. Personal Environments become fully elastic. For Developers Apps are never lost. Personal Environment deletion becomes painless. Better trust, better onboarding, better learning experience.

I would like to propose the development of an API that allows integration with CI/CD tools to check for unused dependencies in an application. This API would provide a boolean value indicating whether there are any unused dependencies, enabling automatic detection during the CI/CD pipeline. By integrating this API into the CI/CD workflow, developers can easily identify and remove unnecessary dependencies, improving application performance and reducing resource consumption early in the development process.

A ranking system for the Mentor Program where mentors earn points based on sessions they conduct. As their points increase, their ranking improves, helping us easily identify and connect with the most active mentors.

Allow changing variable values while debugging

 The Problem: Currently, when a module is deleted, moved, or a developer's access permissions are removed, that module still appears in the "Recent Modules" left panel in Service Studio. When you inadvertently click on it, the platform tries to open it and throws an annoying error stating that you are not allowed to access the module (or that it doesn't exist). This litters the recent items list with "dead links" and creates friction in the daily workflow. Proposed Solution: Service Studio should automatically refresh or validate the "Recent Modules" list. If a module is removed from the environment or if the user no longer has permissions to access it, it should immediately disappear from the recent modules panel. Alternatively, clicking it could trigger a silent validation that removes the shortcut if the module is no longer accessible, instead of opening a dead end and throwing an error popup. Benefits: Cleaner UI: Keeps the Service Studio workspace organized and relevant. Better UX: Prevents frustrating and useless error messages. Efficiency: Saves developers time by ensuring every click in the "Recent" panel actually leads to a valid module.

When working in environments with many apps and modules, finding the ones we use daily can take unnecessary time. It would be useful to have a "Mark as Favorite" option for modules in Service Studio. This would allow developers to quickly access their most frequently used modules when opening the environment. For example: A star icon next to the module name; A "Favorites" section on the home screen; A filter to show only favorite modules.

Upgrade the standard File Upload widget to a comprehensive "File Manager" component. Beyond just uploading, this widget should natively support: Removal: Easily delete a file before submission. Review: Integrated Preview and Download actions for subsequent users in a workflow. This eliminates the need for developers to build custom "Download/Preview" patterns every time they create an approval-based form, providing a seamless experience for both the uploader and the reviewer.

Many REST services implement sending files, documents etc. by having a body with multipart/form-data. There are many questions on the forum about this, e.g. here , here and here . Unfortunately, the OutSystems Platform lacks native support for this, leading to workarounds like this Forge Component or "manually" modifying the request data in the OnBeforeRequest, which leads to things ugly code like this:(Yeah, that's mine :).)So it would be a great addition to the Platform if it had native support for multipart/form-data for REST services, at the very least for consuming them. That would make our lives just a tad bit easier!