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!

When tagging someone in the OutSystems Forum using @, multiple people with the same display name can appear. This makes it unclear which person you are actually replying to. To improve clarity and avoid confusion, I suggest these options: Enforce unique usernames that each user can set for themselves. Display this unique username with name consistently across the forum (profile, comments, and mentions). In the mention dropdown, show both name + unique username so members can easily identify the right person. Or We can also go with an easy step, which in the forum email should be displayed with the name, and also in the mention dropdown This will make communication smoother and ensure that members always tag the correct person in forum discussions.

We should be able to define the names of the fields we are exporting to excel.

While creating Agentic App. the models on the ODC portal are available for every developer without restriction. this could hinder with governance policies while dealing with multiple teams. Suggesting to add Management layer similar to OS 11 lifetime teams to manage development teams more effectively enabling governance of apps and AI Models.

Propose the development of a robust server-side CAPTCHA validation component to enhance security and prevent automated bot submissions, as currently we don't have any OutSystems-supported CAPTCHA component available. Most existing CAPTCHA implementations rely on client-side validation, which can be bypassed, leaving applications vulnerable to spam and malicious activity. A server-side approach would ensure secure verification, improve application integrity, and provide stronger protection against automated attacks. This component should validate CAPTCHA responses on the server, integrate seamlessly with popular CAPTCHA services, and offer easy configuration through a developer-friendly interface and reusable blocks. Additionally, it should support accessibility standards and multi-language options for global deployments. Benefits: Enhanced security against bots and spam Protect sensitive forms and transactions, boosting confidence in the platform Developer-friendly implementation with reusable components

As the Agentic AI badge course suggests to set default values with Settings for SystemPrompt and UserPrompt, I think this will be done more often by Developers in the future. So for ODC Studio there is a popup window for the Settings description but not for the default value. So I think it is a good idea to also provide an addional popup window for the Settings default value, to see clearly the whole default value.

It would be great if we could integrate with Git directly (out of the box) with Service Studio to manage Javascript/JQuery/React/.. and CSS projects.With Git being one of the most popular and powerful Source Control providers, harnessing its power from within Service Studio would just be icing on the cake.

Events in ODC is a great step towards an event driven architecture. In the current implementation, it only allows for server side consumers and I'd like to see that expanded to client side consumers as well. Imagine I'm building a real time application with OutSystems and I want my UI to be refreshed as soon as some backend process is done. Currently, I need to manually integrate with some web socket / server sent event service to achieve this functionality. From my experience this is a convoluted process that requires a lot of time and the purchase of third party services. This is not the low code way. Since now OutSystems has the Event primitive, it's the perfect time to add this capability.

I realize that often company logos on their websites are in SVG format and I need to convert them to PNG to use as an application icon.

The new JavaScript editor for mobile apps, is great, but the autocomplete could use some work :)The feature catches comments and strings at the moment, see below.