Hi, There aren't proper descriptions or steps on how to get certain badges. For example, the badge "Interoperability O11 and ODC" says "Complete the “Future-Proofing your OutSystems Factory with O11 and ODC” Training program" but searching for “Future-Proofing your OutSystems Factory with O11 and ODC” there isn't any item in the list. Also, the filter in the "https://learn.outsystems.com/training/catalog" page only allows 50 characters.

As AI and Large Language Model (LLM) integrations become more common in OutSystems applications, developers need better ways to monitor and manage how these services are used. Currently, when calling APIs like OpenAI or Azure OpenAI, developers must manually track important metrics such as token usage, latency, errors, and estimated costs. This is repetitive and usually implemented differently in each project. This idea proposes a Forge component called AI Observability Toolkit for OutSystems that provides a standardized way to execute LLM calls while automatically capturing key metrics such as: Prompt and completion tokens Total token usage Response latency Model and provider used Estimated request cost Execution status and errors The component could optionally store this information for monitoring purposes and include a ready-to-use Screen Template (AI Observability Dashboard) that developers can select when creating a new screen. This dashboard would display metrics like AI request volume, token usage, latency trends, and estimated costs. This would allow developers to quickly add AI monitoring and observability to any OutSystems application, helping teams better control costs, troubleshoot issues, and manage AI-powered features.

To prevent the population included in the group most vulnerable to contagion by the new coronavirus leaving home, namely the elderly and people with chronic diseases, the Municipality of Proença-a-Nova and the Parish Councils and Unions created a solidarity network for situations of emergency, namely for the purchase of medicines or essential goods, among others.In each village, an interlocutor between the population and the Parish Councils is being defined to communicate needs, and the Municipality is responsible for the subsequent delivery of orders.To facilitate all the communication between the interlocutors and the Municipality, volunteers developed a web and a mobile app during the weekend using OutSystems and made available to Municipality employees to use, tracking the daily requests with the necessary details.

Like one can move a single statement down in the Assign node, it would be very helpful to add the ability to move a node up or down in the logic flow.E.g. if I have an Assign node and then an Aggregate node and I want to move the Assign to rather be after the Aggregate - it would be a time saver to be able to click on the Assign and use some shortcut to make it move to after the Aggregate immediately rather than disconnecting it and moving it manually.

Quite often I go through some modules to clean it from elements that are not used anymore. It would be great if there was a way to know all the components that are not used inside a module and maybe delete them similar to the remove unused dependencies instead of going through every element and clicking find usages in all modules and then deleting it manually if not used

We use SolarWinds for database performance analysis which just shows the raw SQL executed and often it is very hard to work out where it was called from.If the platform could insert an SQL comment with the name of the Aggregate/SQL it would be extremely helpful!We also use Lifetime analytics, but tools like SolarWinds can provide alternative insights.

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

Create the possibility of folders in the CSS editor.This way we can better organize the components and make it easier to update them.

Hi Outsystems Team, I'm currently facing an issue where Service Actions do not receive the full set of client cookies , while Server Actions do. This limitation prevents the use of HTTPRequestHandler.GetCookie / SetCookie inside Service Actions in real scenarios. 📌 Problem When a request reaches a Screen Action or Server Action, all browser cookies are forwarded to the action's execution context. However, when calling a Service Action, only a small subset of platform‑managed cookies (e.g., UserId, TenantId, etc.) is available. This means: Custom cookies created by the application never reach the Service Action. HTTPRequestHandler inside a Service Action cannot read or modify these cookies. Some patterns related to authentication, tracking, and user context become difficult or impossible. 🔍 Expected Behavior Ideally, a Service Action should be able to: Receive the same full cookie set that Server Actions receive. Support HTTPRequestHandler.GetCookie and SetCookie. Allow more advanced use cases such as: Authentication extensions Cross-app user context sharing Tracking / analytics A/B testing Custom session or preference handling 🎯 Why This Matters Many modern architectures rely on Service Actions as: Shared reusable service layers Abstraction layers across multiple applications Integration or cross‑module processing points Centralized logic for authentication, tracking, and user context Without access to client cookies, these Service Actions become: Harder to design Less reusable Less aligned with real-world requirements This directly affects large-scale multi-app environments. ❓ Questions for OutSystems Is there a recommended way to forward all cookies to a Service Actio Is this a platform limitation or an intentional design restriction? Is there any roadmap to allow Service Actions to access the full cookie context? For now, we rely on a Server Action to read the cookies and pass them as input parameters. Is there a better official workaround? 💡 Additional Notes We do not need to modify platform-managed cookie. We only need to access custom cookies generated by the application. Everything works perfectly in Server Actions — the limitation occurs only at the Service Action layer. 🙏 Conclusion I would like to propose a feature that allows Service Actions to: Receive all client cookies, or Optionally specify which custom cookies should be forwarded This would make Service Actions far more flexible and suitable for real-world multi-application use cases. Any insights, confirmations, or guidance from the community or OutSystems staff would be greatly appreciated. Thanks in advance!

Will be helpful to have a build-in fuction to remove duplicates from a listExampleList {A, B, C, A, B }Result list {C}