Problem: Validations are hard, time-consuming and error-prone. Currently, OutSystems structures only define shape, not validity. A lot of projects end up lacking validations because of the effort involved in developing and maintaining them across client and server side. Proposed Solution: Introduce a Schema primitive (similar to Zod and Valibot ) that would define the shape (fields) and also the rules (declarative validation definitions that validate the field contents at runtime ). It would be defined in Service Studio and have an IsValid runtime field that developers can check to assert the validity of the data. An Issues field (list of Issue ) would identify which fields are invalid and the reason. The Schema should be universal, meaning it could be used to validate data both on the client and on the server side based on the same declarative rules. I think this would greatly improve developer speed and application security in our OutSystems applications.

Just like the option to export/download certificates, it would be great to have the same functionality available in the Achievements section as well. The exported file will give information about all the achievements under the achievements section.

If there are any advance queries, replace that by aggregateDon't use foreach Loop in preparationDon't use if conditions in preparationi.e try to avoid if conditions in aggregateApply pagination on list pageDon't show more than 100 records on single pageMove JavaScript webblocks to bottom of pageDon't use preparation aggregates directly in screen actionsBefore using them in screen actions refresh themSuggested by  Suraj.

I would like to have a sort of a screen in the Service Center where all this information would be centralized and displayed, and where it would be possible to list all APIs and to navigate to the API edit screen from there.It is not the first time where I am in a project where it is used a middleware for APIs management inside the organization. And a problem that always happens when, for some reason, the middleware changes its DNS, so from xyz.whatever to azurexyz.whatever, is that to make the changes in all the currently used APIs I need to go espace by espace (or module by module) in Service Center, assuming that I don't need to go into SS to see where all APIs are located and I don't miss any of them and change one by one.I know it is possible to have this kind of list looking into the system entities, but I believe this should be part of the product because it seems to be commonly necessary.This would also help, in cases like the example, I described above, to make sure that we don't forget any API where the URL basis needed to be changed.

Hi,My suggestion is that modules could reference a particular version of another module.This would allow teams to keep developing and evolving their modules and not being concerned about apps that are not currently being worked on becoming broken or needing someone to manually update them.This is a very common scenario in larger factories and even with proper architecture it will happen.The way I see this working in practice is tagging module versions as "stable" and any consumer could choose to reference "current version", which would be the same as it is now, or one of the "stable version".This extra concept of "stable version" might be needed otherwise we would always be selecting from a list of hundreds or thousands of versions.From a platform perspective I believe this is quite doable! We can already just clone any module and reference that one (thus creating a kind of stable version), the platform could do this behind the scenes and have that "hidden clone" as the Stable version.The biggest difference from what we can do now is that these clones MUST use the same physical tables of the main module! (as in: not creating new ones)It goes without saying that what I'm suggesting here is also the way most "traditional" languages work!Cheers,Hermínio

I often find myself pressing the "eSpace management" button in Service Studio just so I can start a timer. It would be useful if we could just right click a timer on the Processes tab and have a "Run Now" to instantly schedule the timer.

 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.

I would like to suggest improving the loading animation in the Service Center when applying filters or performing actions. Currently, the indicator is barely visible and only appears if you scroll down, which makes it difficult to know whether the system is processing, still loading the filters, or if the action failed. At the moment, there is only a small loading bar that becomes visible when scrolling. A clearer solution could be to add a button‑loading or a loading indicator next to the filter button, so devs have immediate feedback that an operation is in progress. Filtering: Loading not visible The red loading bar at the top only becomes visible when you scroll down.

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.

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