I'm not sure if there is already an existing idea like this, the search didn't provide me with a match so I'm creating one...We have the ability to import a swagger 2.0 rest services already, but unlike its SOAP counterpart we lack the ability to do this locally from a fileThis should be added IMHOBest regards,PC

It would be great to have a visual feedback when we have dependencies to update or even when they are outdated and need some action to validate and update them.A preview of what could be to help us.This could be validated when opening the module (as it is already being done) but it would give a visual feedback even when we don't have breaking dependencies. It could also be checked after publishing for example.As this would only validate the used dependencies, probably wouldn't take as much time/effort like when we open the popup itself.

It would be great if OutSystems could collaborate with partner companies to offer internship opportunities for newcomers in the community. While the OutSystems Developer School already helps many beginners learn the platform, having a structured internship program would give them valuable real-world experience and a chance to apply their knowledge in live projects. Through this initiative, OutSystems could also recommend top-performing learners or certified developers to partner companies, helping new talents get recognized and boosting their confidence to grow further in their OutSystems careers.

It would be great if OutSystems could provide its own AI solution, similar to Neo, to help developers implement AI-driven features securely within the platform. Relying on third-party AI integrations often raises concerns about data privacy and security. By offering a native OutSystems AI, customers would gain greater confidence that their data remains protected while still benefiting from AI capabilities such as automation, prediction, and chat-based assistance all managed securely within the OutSystems ecosystem.

The ability to clone an extension would be a really really nice-to-have. :-)

I'd love to have a ListSplit System Action, that performs a ListFilter, but also outputs all the other elements in a second list. So say I have a List with an Attribute "Value" and the input to ListSplit is "Value > 1000", I'd get two lists, one with all Values upto 1000, and one with all Values above 1000.

It whould be nice to have an overview of all available actions and webservices in Service Center, something like a 4GL dictionary. This would give an overview of Built-in actions all public actions in Sollutions all webservices references of all eSpaces / Extensions and its function (UI / Business layer / Integration Layer) This is also the place to functionaly describe these actions/services

The implemented solution retrieves the full organizational hierarchy using a recursive depth-first traversal approach. The logic is based on a function that accepts: A parent organization ID A collection used to accumulate child nodes The function performs the following steps: It retrieves all direct child organizations for the given parent. Each child is added to the output collection. For every child, the same function is called recursively, passing: The child as the new parent The updated collection of results This process continues until all levels of the hierarchy are explored. This approach ensures that: The hierarchy is traversed depth-first All descendants of a node are retrieved before moving to the next sibling The final output contains the complete organizational tree under the initial parent

OutSystems now supports storing settings as secrets in both OutSystems 11 (Site Properties as Secrets) and OutSystems ODC. However, secrets often have an expiration date, and without proper tracking, they can expire unnoticed, causing disruptions. Proposed ideas : Optional Expiration Date for Secrets – Allow users to set an expiration date for secrets stored in Site Properties (OutSystems 11) and Secrets (OutSystems ODC). Reminder Notifications – Enable reminders to be sent before expiration to a specified role so they can take action. This feature would help OutSystems 11 / ODC users proactively manage secrets and avoid unexpected failures due to expired credentials.

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