The ODC was stupendous!!! Good Job OutSystems CrewBut I propose that Outsystems make the presentations available  to the comunity.Besides that it is not possible to attend to all presentations due to the parallel sessions

OutSystems deployments always include all actions and resources, even when some are: Debug or experimental Environment‑specific Not intended for higher environments This increases deployment risk and forces developers to use workarounds (deleting, cloning modules, or manual discipline). Proposed Solution Introduce a way to exclude specific artifacts from deployment, similar to .gitignore. Examples Mark Actions / Files / Folders as “Exclude from Deployment” Or define ignore rules per app/module (e.g. /Debug/*, /Resources/MockData.json) Optional: environment‑specific rules (Dev vs Prod) Benefits Safer deployments Cleaner production environments Better DevOps and CI/CD workflows Less technical debt This feature aligns with modern development practices and would greatly improve developer experience in OutSystems.

Extend the platform's JavaScript Node and Client Action invocation contract to include a fifth built-in parameter: $event, exposing the native browser Event object alongside the existing $parameters, $actions, $roles, and $public. The change would be additive and non-breaking - I assume. Use case : implement an OnKeyUp handler that runs logic only when Enter is pressed, without manually wiring addEventListener/removeEventListener — the platform already manages the event listener, it just needs to forward what it receives.

Hi If I'm using Data Fabric connector for O11, I get a Private Gateway out-of-the-box, creating a secure, encrypted tunnel between my ODC tenant and my O11 environment. If I'm doing REST API O11 ODC, I still have to design connectivity myself. OutSystems provides coexistence capabilities between: -OutSystems 11 (O11) -OutSystems Developer Cloud (ODC) These allow to: -Expose APIs/services from O11 to ODC Consume O11 logic from ODC apps (and vice versa) However: This is based on standard integration mechanisms (REST APIs, networking configuration, identity setup), not on an automatically provisioned “private gateway”. For this situations where the services are on O11 set the REST API property API Consumer to ODC and on ODC are set to REST API property API Producer to O11 it would be useful to have a Private Gateway out-of-the-box. Regards

As a developer, I find myself constantly using properties of lists and data actions like `. Empty ` and `. IsDataFetched `. When assigning to a boolean variable, Service Studio could suggest this properties. See in the following example that I wanted the `Tickets.Empty` property, but it was not suggested.

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

Very basic and simple ideia, just what the title says: Reminders could have a different color than regular comments (orange?)Some complex logic often gets several comments on it and this would help to rapidly identify the reminders/todo/WIP from the "documentation"

please add auto adjust action flow

Support datatype of jsonb, feature of Similarity Search, pgvector as vector database for LLM embedding storage.

In ODC, account creation and recover password already support 2FA. Introduce a 2FA state between credential validation and session creation, exposed through CreateAuthenticationChallenge() and CompleteLogin() APIs. CreateAuthenticationChallenge( Username, Password ) Returns OTP CompleteLogin( Username, Password, ChallengeToken ) This would allow support for several 2FA flows with the built-in IdP.