I would find it very handy to be able to duplicate any action within Service Studio instead of using 'Copy' which would populate the clipboard, while duplicate would preserve the value in the clipboard.

The proposal is to introduce a real-time warning mechanism in OutSystems Service Studio to alert developers when creating public actions or public action inputs without providing descriptions. While the AI Mentor feature in OutSystems already detects missing descriptions, it does so in retrospect, during a later analysis phase. Real-time warnings offer immediate feedback during the development process, ensuring that developers address documentation gaps as they occur. Benefits: Immediate Feedback and Correction: Real-time warnings provide developers with immediate feedback as they create public actions or inputs without descriptions. This proactive approach allows developers to rectify missing documentation promptly, minimizing the likelihood of overlooking descriptions and ensuring comprehensive documentation coverage. Preservation of Developer Context and Workflow: By alerting developers to missing descriptions in real time, the warning mechanism helps maintain developers' cognitive context and workflow. Developers can address documentation gaps as they occur, without the need to revisit or reanalyze code later, thus preventing disruptions to their thought process and ensuring consistent focus on development tasks. Developer Accountability and Ownership: Real-time warnings reinforce developer accountability for documenting code by prompting them to provide descriptions during the development process. By integrating documentation responsibilities directly into the development workflow, developers are actively reminded of the importance of documentation as a best practice, fostering a culture of ownership and accountability for code quality. Enhanced Code Understandability and Maintainability: Including descriptions for public elements enhances code understandability and maintainability. Real-time warnings encourage developers to adopt good documentation practices from the outset, resulting in codebases that are easier to comprehend, navigate, and maintain over time. This ultimately leads to improved collaboration and efficiency within development teams. Overall, the implementation of a real-time warning mechanism for missing descriptions in OutSystems Service Studio complements the existing capabilities of the AI Mentor feature by providing immediate feedback and guidance to developers. By promoting proactive documentation practices, this enhancement contributes to the creation of high-quality, well-documented applications on the OutSystems platform.

Whenever we have multiple errors (or performance issues) in both ODC Studio and Service Studio, we may want to evaluate the impact of the issues (number of occurrences) and according to that, we will work on strategies to solve them. In the print below, for instance, it would add a lot of value if we could apply an order by Error Description on the records. In the scope of the image, we have 5 different errors but one of them happens more frequently than the other ones so I would tackle this one first. Although, that might have a different outcome if we take into consideration all the issues listed and, the priority might change.

As a developer,I would like to have a built in timeout exception,So that I can do logic related to this specific exception.Imagine a scenario where I am implementing a circuit breaker pattern so that I can stop calling an external service if it times out X amount of times.In the server context, to know if the service has timed out, we need to have an "All Exception" handler and check for the message"The operation has timed out"Checking for an hardcoded string is obviously not great, and could be easily solved by adding a built in exception

It already happened to me a couple of times - since I have the habit of setting the assign labels, sometimes I forget the assign itself. An empty assign has no logic at all, and therefore should display a True-Change warning to developers.

I think it would be nice when debugging an application to have a way of copying the runtime values to the query input parameters (test fields). This is very boring and time consuming for advance query with many input parameters for example. On top of that it would be nice to have a way to save these test values, and of course share them along with all development team. Check screen shot below.

The  Community Leaderboard page would be a great place to convert into a Community Dashboard and extend it with more community statistics like:Top Solution Contributors of the month + of all timeTop Forge Contributors of the month + of all timeTop Cheerful (likes given) Community Members of the month + of all timeTop Celebrated (likes received) Community Members of the month + of all timeAnd more...Let give this amazing OutSystems Community its own Wall of Fame!More discussion going on here: https://www.outsystems.com/forums/discussion/64456/community-recognition-top-solution-contributors/

Add a warning on Service Studio if a non-public Structure is not in use.This can help developers to identify non necessary data on service studio and make the code more clean.

Integrate Oauth 2.0 as a feature. Oauth 2.0 has become the API authentication standard. While their are options to extend this functionality they are not super simple to integrate and using things like OKTA for a lot of companies gets expensive. OutSystems could aggregate this functionality into a standard function that just gets configured and allow clients to set this up from their own Service Studio/Service Center. This might be a challenge for On-Prem clients, but seems very feasible for cloud based clients. It might even be something that you charge for or use as a value add to drive clients to your cloud instead of On-Prem hosting.

Add a warning on ServiceStudio when you have situations like these:Because when your try to access the webscreen as expected: https://<ServerName>/<eSpaceName>/WebScreen1.aspxYou get this message on ServiceCenter: The file '/<eSpaceName>WebScreen1.aspx' does not exist.Sometimes, it's not easy to understand that ,by some reason, you have 2 WebScreens with the same name (specially on big and complex Espaces) on different WebFlows.Credits for this idea also to Edgar Ramos and Vítor Rosário that I found "digging" a bug that was found on a eSpace related to this problem