It would be highly beneficial if the Espace_Versions table included an additional column/attribute to store the publish/deployment comment that is currently supported through the recently added deployment comment option. Additionally, exposing the same information through the LifeTime APIs would greatly help customers build custom audit, monitoring, and deployment tracking solutions. This enhancement would provide better traceability of deployments, improve release governance, and help teams understand the intent/context behind each deployment without depending solely on external communication channels or manual documentation. Potential Use Cases: Custom deployment audit dashboards Release traceability and governance Tracking hotfix/business deployment reasons Displaying deployment comments in internal monitoring consoles Easier PROD publishes analysis and reporting Kind Regards, Sandeep

Using OutSystems Semantic Search for community pages such as Forums, Ideas, and Forge brings a step change in how community members discover knowledge and reusable assets across the ecosystem. Traditional keyword search relies on exact matches, which often leads to incomplete or irrelevant results, especially in large content bases like community discussions, ideas and Forge components. Semantic Search, by contrast, understands intent and context, allowing users to find relevant answers even when terminology differs from how content was originally written. For the OutSystems community, this has a few clear benefits. First, it significantly improves discoverability. Community members can find the right forum threads, idea submissions, or Forge components without needing to know the exact naming or tags used by the author. This reduces friction and increases successful self-service. Second, it increases reuse and reduces duplication. Better search results mean developers are more likely to find existing Forge components instead of rebuilding similar functionality, and more likely to engage with existing Ideas rather than creating duplicates. Third, it improves community engagement quality. When users quickly find relevant discussions or solutions, they are more likely to contribute back, vote on Ideas, or refine existing answers instead of starting new fragmented threads. Finally, it future-proofs the community knowledge base. As content volume grows, semantic understanding scales far better than keyword-based approaches, ensuring that search quality does not degrade over time. In short, Semantic Search turns the community from a static repository into an intelligent discovery layer, making knowledge, ideas, and reusable components easier to access, reuse, and extend.

Hi, I am new and I am being currently trained for the new ODC studio. While working with the ODC Data Grid and more so with the dropdown Column I notice something and asked the ODC AI and looked in documentation and found this... Build a list of dropdown options for a Data Grid DropdownColumn (type DropdownOption2.List). Populate it in the Aggregate’s On After Fetch client action. Include a synthetic first option like “Select genre” (so users can leave the value empty), then add one option per record returned by GetGenres. Normally the flow looks like: Start with an empty list (TmpOptions) Create a DropdownOption2 record for “Select genre” Append/Add it to TmpOptions Loop genres, create DropdownOption2 for each, append/add Assign GenreOptions = TmpOptions Bind DropdownOptionList = GenreOptions Why you couldn’t finish it: In your ODC environment, the client action toolbox did not expose any list-manipulation nodes/functions (like ListAppend/Add/Insert/Clear). Without an “append/add” capability, you can’t programmatically build a DropdownOption2.List row-by-row in that action. That specifically blocks the “prepend a default option” pattern, because you have no way to insert one extra item ahead of the real data. What that means in practice: You can still bind the dropdown to a list that already exists (for example, an aggregate result mapped into dropdown options, if the component supports that mapping). But you cannot “manufacture” a new list with an extra first item inside the action unless list add/append is available. So I think it would be helpful to bring that tool and probably many others to the over to ODC to improve the work flow to match what was able to be done it seems in OS11 and if not then this should be created so that I can be done in a no code way. Thanks Tim

Hi Outsystems teams, Since the OS charing static entity for 1 AO, to save some cost for clients, in many projects, we hardly use static-entity even though it should use Static-entity for many purposes. We need to use alternative ways to implement the static concept, like using structure, hardcode... This led the development become more complex in design, implement, and more hard-code used, but we can't spend 1 AO for just 5 records stored in static-entity like status, type, etc... Actually many projects opened just to Delete all static entity from the code to save cost. From begining we've learnt how to use Static entity, and in real project we need to learn how to not use Static entity to save AO, this make static entity very dead. Can Outsystems consider to lower the price of AO somehow like count it 1 AO = 3 or 4 static entity, or consider make it free if there are < 10 record store in static entity, this would be a great thing for Outsystems developers and clients. Thanks :)

Be able to create a unit test for a Server / Service / Client (?) / Screen (?) action that shall be executed without developer intervention, for regression purposes.

A centralized Developer Cheat Sheet for OutSystems Developer Cloud (ODC) would greatly help both new and experienced developers quickly understand and adopt the platform. Similar to the existing O11 cheat sheet, this should provide a concise overview of key ODC concepts, architecture, development flow, best practices, and differences from O11. It would serve as a quick reference guide to help developers ramp up faster and become productive in ODC projects with minimal learning curve. This resource would be especially useful for: New developers getting started with ODC Experienced O11 developers transitioning to ODC Teams looking for a quick refresher on core concepts Providing such a cheat sheet would improve onboarding efficiency, reduce confusion, and accelerate project delivery within the ODC ecosystem.

Since we have the 1-Click Publish with Message, it would be great if we can set by default in settings, where Mentor to generate the message for us based on the changes made from previously published version.

Hi OS team, can we also have a IntelliSense looks alike whenever we use alias in advance SQL can be helpful when too many join/sub queries sample auto popuplate from the user table currenly this is the behaviour whenever i use alias on my tables -no suggestion

I propose the development of the Outsystems Advisor , a tool designed to ensure adherence to Outsystems best practices. This solution will provide personalized recommendations to optimize deployments across five key pillars : Cost , Security, Reliability, Operational Excellence, and Performance.

 Problem When working with complex structures, lists, aggregates, or data actions, developers often need to reuse a full variable path. Today, this usually requires manually navigating the data tree and rewriting the reference. How this suggestion can help A simple “Copy Full Reference” option would improve productivity and reduce typing mistakes, especially in large Reactive applications with complex data models. Implementation example Right-click on any variable, attribute, or structure field and select: Copy Full Reference Example output: GetRequestById.List.Current.Request.Approver.Name This could work inside Assigns, Expressions, Conditions, Client Actions, and Server Actions.