Enable the use of blocks in reactive emails. Currently all that is able to configure inside reactive emails is shown below. It would however be very helpfull if we could use also use blocks

 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.

 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.

Expose the data in your Outsystems application via an OData service (RESTful API). Just rightclick on the entity and the rest is done for you, including security, streaming and paging. The data is queryable from the outside. The data can be used in Excel, LinqPad, PowerBI, Tableau, and a number of other BI solutions.

It would be great if I could expand an assignment to some structure like is already possible for parameters of an action.

The accelerator should allow developers to easily configure the behavior of the Delete action, providing the option to choose between hard delete and soft delete based on project requirements. This enhancement would: Improve data integrity: Prevent accidental data loss by allowing for easy recovery of "deleted" records. Enhance auditing capabilities: Maintain a historical record of deleted entities for analysis and compliance purposes. Increase flexibility: Provide developers with the choice of deletion behavior based on project needs. Reduce development effort: Eliminate the need to manually implement soft delete logic for each entity. Additionally for the existing feature, enhance the OutSystems Entity Action Wrappers Accelerator to include a built-in option for soft delete. By default, the generated Delete action should mark the entity's 'IsActive' flag as 'False' instead of performing a hard delete. This will improve data integrity and provide greater flexibility for data recovery and auditing purposes. By incorporating this feature, OutSystems can further streamline the development process and provide developers with more robust and flexible data management capabilities.

I think that the line number where an error ocurrs, could be useful.

Current CSPs rely on allow-listing domains which is difficult to secure, and vulnerable to attackers bypassing the CSP. As an example, it is currently impossible to implement Google Tag Manager without compromising an Outsystems Content Security Policy, as it requires both the unsafe-inline directive. It also requires allow-listing the www.googletabmanager.com domain which is found to host JSONP endpoints, which also can be used to bypass the CSP. See: https://csp-evaluator.withgoogle.com/ for a report The recommended approach is to use server generated nonce tokens in the CSP, and also in the scripts that are allowed to load. These scripts are considered trusted and may in-turn safely load script from other, cross domain sources. For tag manager, a recommended setup is here https://developers.google.com/tag-platform/security/guides/csp My suggestion is for Outsystems to support generation of nonces in the CSP headers returned to the client, and allow the front end to load a developer defined script with the same nonce tag. From there we could load any other cross domain resources without needing to weaken the CSP. For more information, see https://web.dev/articles/strict-csp

please add auto adjust action flow

Introduce a unique icon for private actions in OutSystems to visually distinguish them from public actions. This improves clarity, reduces accidental misuse and supports better encapsulation of logic. A key benefit is that it eliminates the need to reorganize code into folders or rename actions. Observation: I could not find this exact idea already proposed. If anyone knows, please let me know. Attached a example.