Since OutSystems recommends a separation of deployment and release by using Feature Toggles, I think it makes sense for this feature to be available in the unified ODC Portal and more integrated with the deployment process.

It would be nice if we could cancel the publishing solution process on service center.

Currently, OutSystems developers cloud (ODC) is only available as paid service but it would be great if it is made available to the general developer community as well to experience and explore it. 1. We may be able to suggest some additional ideas and improvements needed for the portal. 2. Will make us gain practical experience in it. Which can also help us plan to include it in upcoming projects.

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.

I see this feature as a must-have on the concept of Build It Fast, Right, and For the Future!So I would like to start with an example:Imagine you need to create an action/function that given certain parameters it will return you a text, this action/function can be done in a client-side action/function (does not require server logic), but you need to use the same action in an asynchronous logic which will require a server-side action/function.With this, at the moment, you need to decide on two approaches, both with pros and cons:1 - You go for the code reusability approach, which is you implement a server-side action/function, and on the client-side, when needed you make a request to the server using this server-side action/function. So the benefit of this approach is that you have a centralized place to manage this action/function, however, you will perform server requests when they could be avoided.2 - You go for the more performant approach, which is, you implement a client-side action/function and you implement the same logic on a server-side action/function. The benefit of this one is that you will spare the requests towards the server when you are using the action/function in the client-side logic, but you will always have to maintain the logic in two places. The idea would be to create a folder in between Client Actions and Server Actions that could be called Hybrid Actions, and these actions could be used both as Client and Server actions, when it was used on the Client side it would behave as a client-side action and in server-side it would run as a server-action.I know that the code generated under the hoods is different, but it is there where OutSystems brings its maximum value by abstracting the developers of the high code layer :)

Service Studio and Service Center should show the Forge application version.If I install an application from Forge, the version should be visible in Service Studio and Service Center. This way we can easilly compare the version we have installed with the latest versions from Forge.In Service Studio it could be visible in the apllication screen (see attached print screen)

Hello, we have thousand of fake references between espaces, created by unused references, that are created wrong outdated espaces.Also are creating false positive architecture violations, and we suspect that can affect solution publish time.We have more that 400 publish per day, so asking developers to click on remove unused references on each publish does not make any sense.If we think that most of these references come from invisible actions, like copy paste between espaces, on add references with multiple other references, these should be and automatic action, on Service Studio publish, or on Service Center solution publish, like publish with full compilations one.In my opinion, in Service Center, its mandatory, specially when you have huge factory like ours with 1500 espaces, and you want to clean up legacy code.

I see a lot of spam posts in the forum. Add a button so we can report this.

Many customers continue to use OutSystems 11 and have no near-term plans to migrate to ODC. Bringing agentic development capabilities to OS11 would allow these customers to benefit from AI-driven development, productivity gains, and application modernization.

I love the free personal environments that OutSystems offers the community free of charge! It offers a lot of freedom to develop and test applications without the burden of contaminating your own business environments.On various circumstances I had problems with my personal environment. It was offline for days and had to raise a ticket with support. It would be great if I have the option to reset my personal environment to the initial state. Meaning that all customizations and configurations on my personal environment are wiped.