Currently, OutSystems documentation provides a list of compatible browsers for generated applications. However, verifying this compatibility at runtime requires developers to manually implement logic using functions like GetBrowser or GetUserAgent from the HTTPRequestHandler extension. This approach has drawbacks: Manual Maintenance: Developers must update their code whenever the official compatibility list changes, risking outdated implementations. Difficult Diagnosis: Identifying issues caused by unsupported browsers can be time-consuming, as seen in a real case where support intervention was required. Suggestion:Introduce a built-in Action in the platform to automatically verify browser compatibility using OutSystems’ maintained compatibility list. Benefits: Simplifies development by removing the need for custom maintenance. Speeds up issue diagnosis related to browser compatibility. Enhances user experience by providing immediate feedback if an unsupported browser is detected. IsBrowserCompatible() -> Boolean The Action would return True for compatible browsers and False otherwise. Additional functionality could provide details about the detected browser and compatibility issues.

When creating an entity diagram, have the ability to hide the attributes. This would make it easy to see the relation between entities easily.

 The Problem: The current badges page feels "heavy" because it treats every year, every event, and every status as a separate icon. This creates visual noise rather than meaningful recognition. Suggestions: First Milestones – Rename Getting Started section Member Onboarding – Merge Welcome and Autobiographer First Post First Idea First Asset Agentic AI Ready Online Community Answer Marked as Solution Idea Implemented Referral Program – Move to Community Growth Developer Survey OS Research Program Participant OS Research Program Pioneer OS Research Program Contributor OS Research Program Rock Star Knowledge Become an AI Developer OutSystems Developer School Publication – Move to Community Growth Top Technical Content Contributor Online Review – Move to Community Growth Certification Attained Project Finished Interoperability O11 and ODC Development First Asset – Move to First Milestones OS Component Contributor – Break them into multiple badges: Forge Contributor ODC Components Contributor AI Agents Contributor GitHub Pull Contributor 2021 Neo’s Odyssey – Move to Gamifications Interoperability O11 and ODC - Move to Knowldege Agentic AI ready – Move to First Milestones OutSystems Hackathon – Move to Gamifications OS Research Program Participant - Move to Online Community OS Research Program Pioneer - Move to Online Community OS Research Program Contributor - Move to Online Community OS Research Program Rock Star - Move to Online Community 2025 Agents vs Zombies contest – Move to Gamifications Events Speaker – Renamed to Global Speaker and introduce USG Speaker Webinar Led – Move to Community Growth User Group Organizer – Move to Community Growth Event Organizer – Move to Community Growth Award Attended ODC 2018 – Can be deprecated Spoke at ODC 2018 - Can be deprecated, Merged with Global Speaker Spoke at OSDC 2021 - Can be deprecated, Merged with Global Speaker Attended OSDC 2021 - Can be deprecated Challenges/ Gamifications 2021 Neo’s Odyssey OutSystems Hackathon 2025 Agents vs Zombies contest Groundhog Day Challenge Community Growth Referral Program Publication Online Review Webinar Led User Group Organizer Event Organizer Mentor – Introduce this Superusers MVP Champion MVP Alumni Champion Alumni Remove badges counts. Eg, in Superusers the member can have either of the badge - having 1/4 badges is irrelevant.

Add the ability to post an idea with a tag ot O11 or ODC or both with a way to filter with the same as in forums.

The SortRecordList extension allowed to have multiple sort criterias. The ListSort should have feature parity with that extension, at least.Having this built-in on the platform would be useful for sorting third-party datasources. For example, imagine that a web service returns financial transactions, and has two distinct columns: Date and Time. We would need to sort on both columns to be able to present data in chronological order.

Would it be possible to add a Test input at the beginning of any logic flow, or within an expression. Similar to the Test feature within aggregates or SQL. For expressions it could be helpful when there is data processing or functions involved. For logic flows it would be great to be able to enter a test value at the beginning or somewhere in the middle of the flow and see how it behaves through the logic. Doing this via debugger is not always as direct to test, and sometimes logic is only triggered at certain instances which can be challenging to trigger during debugging. It could be similar to having a debug option to start from a location within the code, with a data input set. Rather than having to trigger the logic from the front end.

It is difficult to track down a version of a forge component once you have installed it in your environment and the component receives new updates from the community.It should be easier to check how far behind I am in adopting a newer version of a particular forge component by just going to Service Center or best in LifeTime itself.Based on a trustable hashing algorigthm, why can OutSystems not determine if the package hash for the version of Forge component is matching with a signature with a published component and if so flag it to me easily. If the match does not happen then tell me that I have customized the copy of forge component so it is not possible to track it against the public repository.

Currently, the Default Value field in Site Properties is limited to a single-line input with no option to expand the editing area. This makes it cumbersome to view and edit longer values clearly. An expandable or multi-line editor, similar to the one used for editing Expressions, would greatly improve readability and usability.

Sometimes we need to navigate through the module, when merging. I think that is a good idea to allow to navigate through the module while doing the merge, without the need to close the merge popup. This is usefull to check the code on other actions (not on the merge)

It does not take up any backend processing power, neither does it take up any storage space in the servers. It's all frontend. Why the cost of AO for using Local Storage?