I think there should be a reset button that allows users to reset questions to default, remove the answers so that users can try answering the quiz questions again after coming back to review the material.First time i made some small mistakes, and now after 3 months i want to test my knowledge and i can't do it because the questions are already answered. Do i have to make a new account?

I would like to suggest having option to enable or disable logging for each service action by adding optional parameter to service action "Enable Logging" by default true but developer can change it to false. Something similar to log email content. I understand service action has same behavior as Rest API so it has 3 logging options (Default, troubleshoot, Full) but this option used per module so its affecting all service actions into the module but sometimes I need to change logging for one of service actions only. We faced a case that we have service action that has too much traffic calling it so it log every hit to API log table into OutSystems Log database which causing a huge increase into size of table although our logging level is default. It is not important or no business need for us to log this action so we stopped logging for service actions into this module to avoid this increase. As another workaround we replaced this service action with server action. We are using O11

Greetings, Exposed SOAP web services requests and response logging feature is missing. It is important to have logging capabilities to troubleshoot integration issues. Currently it is only possible to change default logging level and set Troubleshoot or Full logging level only for Consumed SOAP, Exposed and Consumed REST web services. So, logging levels feature is missing for Exposed SOAP. There was an idea Logging web services requests and responses which was implemented long time ago but looks like Exposed SOAP was missing. I have checked the documentation and confirmed with support, there is not out of the box solution to change logging levels for Exposed SOAP web services and log Requests and Reponses. Thank you. Mikheil Osipov

Currently, developers receive community points for submitting Forge components from OutSystems 11, but no points are awarded when submitting from ODC. It would be great to align this with O11 and grant points for ODC submissions as well. This enhancement would motivate developers to contribute more reusable Forge assets in ODC, fostering greater community engagement and innovation.

Today is only possible to search an application by name. But would be nice to have some kind of filtering too. Today I missed a way of filtering by type (web, mobile, service). Also for example hide the applications that came from forge. But for sure there is a lot more filtering that we can use. Would be nice to discuss around this topicAnd image to be clear the screen I'm talking about:

Currently, the only way to share Outsystems code with LLMs or to show to a person on the forums, etc, is with a Screenshots, but a Screenshot cannot display everything at once: for example Input/Output parameters for several Actions in an Action flow in a single Screenshot. A single one side Service Studio -> Text Editor would open new doors, if you can Copy/Paste Service Studio elements in a text form to paste into LLMs or other text editors for AI code generations , context, creation of documentation, etc. It doesn't have to be perfect, it can be an imperfect, incomplete and invalid machine generated code (JSON, XML or any other text form, that is easier for the Service Studio team to implement), LLMs nowadays can quickly reformat it in a better form according to use case and extract whatever needed. It can help by virtually all of a module/application elements inside Service Studio, but among the most beneficial would be StaticEntities and Entities + attributes, Structures + attributes, Action in a flow (names + input/output parameters), etc.) in a text form. It is not the same as, but it would implicitly provide some solution for the problem from this idea: https://www.outsystems.com/ideas/11114/copy-multiple-property-names/

I observe that the people who are new in Outsystems they complete the course but when it comes to certification exams they found question in exam confusing and they perform poor in exams.  I think there should be at least one mock test before certification.

We've seen a lot of discussion around Static Entities lately, for example, this idea . While Static Entities provide some value for enumeration use cases, they fall short in a lot of ways: They are stored in the database. They are expensive compute wise (more than they should be) to retrieve. They cost AOs. To use them on client side (other than the ID), they need to be manually synced. Developers need to understand the aforementioned details to use them correctly. Traditional Enums in high code languages are much better. They are directly in the code, making them available at no cost to the caller. Since OutSystems is a giant compiler, Enums should be a first-class construct that: Are compiled into constants rather than stored in the database. Are accessible both server-side and client-side without requiring manual synchronization. Do not consume AOs. Can be used in Service Studio like a variable. Maintain type safety like a Static Entity ID. Static Entities are an old primitive of the platform. I don't believe changing them at this stage is a good move, so I propose creating a new primitive—Enums—that align with modern best practices while keeping the low-code philosophy.

It would be incredible if we would be able to add the cache_control header in the messages we are sending to the LLMs using the new AI Workbench. This feature is available at least on Claude with more info here: https://docs.claude.com/en/docs/build-with-claude/prompt-caching This approach, and I quote, "significantly reduces processing time and costs for repetitive tasks or prompts with consistent elements." This allows companies substancial savings on token usage! Looking at the documentation they clame that this is especially useful for: Prompts with many examples Large amounts of context or background information Repetitive tasks with consistent instructions Long multi-turn conversations where I would underline the repetitive tasks, which is one of the advantages of using agentic AI, where it can call the same tools again and again, with the same system prompt. In the documentation the example they give is to cache an entire book. In our case, these could be large documents with company details, or a quite big system prompt.

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.