Ideas
10869ideas
Created 13 days ago
2024-07-05 14-16-55
Daniël Kuhlmann
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.
164
Views
1
Comments
On our RadarOn our Radar
Community
Created on 18 Dec 2024
2025-12-04 09-01-03
Kiet Phan
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 :)
3234
Views
48
Comments
New
Licensing
Created on 04 Jan 2019
2023-02-20 18-02-29
Nuno Baptista
Be able to create a unit test for a Server / Service / Client (?) / Screen (?) action that shall be executed without developer intervention, for regression purposes.
10873
Views
96
Comments
On our RadarOn our Radar
Backend
Created on 17 Apr
2026-01-23 11-38-55
Dinesh Murugan
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.
515
Views
3
Comments
New
Documentation
Created 6 days ago
2025-03-19 01-45-51
Sandeep Kumar Kolli
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
67
Views
1
Comments
New
Lifetime
Created 2 days ago
2021-06-21 11-43-23
Carlos César Jorge Marques
 Use-case: I have an app with many screens and tons of CSS classes defined in the style sheet; I decide I no longer need one or more screens, so I delete it/them; now, I have a bunch of CSS classes defined in the style sheet that are no longer used anywhere in the app. Problem: I don't want unused CCS classes in the style sheet, so now I'm forced to search for each class in the app to check if it's used or not before safely deleting its definition. Solution: there should be an easy way to "Removed All Unused CSS Definitions", just like there's a "Remove unused elements" (see image), and/or a visual cue on the Style Sheet, next to each unused CSS definition, to make it easy for thee developer to see that that particular definition is not being used (that way the developer can manually delete only the ones they're sure they'll never use again).
18
Views
0
Comments
New
Frontend (App Interfaces)
Created on 04 May
2025-08-11 01-24-41
Azli Amirul Ehsan Bin Razali
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.
215
Views
6
Comments
New
1CP
Created 5 days ago
2026-03-06 09-21-20
Rahul Chavan
 Problem : Right now, the platform lets us right-click an Entity and select "Create Action Wrapper" to instantly generate a secure CRUD wrapper. However, we don't have this option for Consumed REST APIs. Developers must manually create a Server Action, recreate the inputs/outputs, and add error handling for every single API endpoint. For large APIs, this takes a lot of time and involves repetitive boilerplate work. Solution : Add a "Create Action Wrapper" option when you right-click a Consumed REST API or its individual methods. When clicked, Service Studio should automatically generate a Server/Service Action that: Copies all input and output parameters. Calls the REST API method inside it. Includes a standard Exception Handler block. Why this helps: Saves Time: Speeds up integration development by cutting out repetitive manual mapping. Best Practices: Makes it effortless for teams to follow clean architecture guidelines by abstracting integration layers.
55
Views
0
Comments
New
Service Studio
Created 8 days ago
UserImage.jpg
Timothy Gregory
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
83
Views
6
Comments
Out of scope
Service Studio
Created 1 day ago
2026-01-20 02-55-29
Ahmad Fadhil Arif Baharudin
Sometimes I do development in my 4K monitor and its hard for me to do development in the studio because everything is small. If the studio has UI Scaling feature then I can scale the studio's UI to make it everything in the studio (texts & buttons) bigger
19
Views
0
Comments
New
Service Studio
1 to 10 of 10869 records
previous12...next
Top Idea Creators
High Five to the top 5 idea creators in the last 30 days
2026-03-13 16-36-56
5 ideas
5
2019-02-27 17-48-20
1 ideas
Top Brainstormers
High Five to the top 5 brainstormers in the last 30 days
2018-07-06 11-13-55
13 comments
2
2021-09-06 15-09-53
9 comments
3
2024-07-05 14-16-55
7 comments
5
UserImage.jpg
3 comments
Code of Conduct 
The guidelines we live by that make
this Community amazing!
Code of Conduct
Stay Up-To-Date
Keep on top of what's happening in the Developer Community.
Forum, Forge, Training, Documentation, and more!