OutSystems could introduce a feature where the platform automatically optimizes entities based on usage patterns. For example, when an entity is used in high-traffic applications, the system could dynamically adjust indexing, caching, and query execution strategies without manual intervention. This would allow developers to focus more on business logic rather than worrying about performance optimization.

Would be great if we could see progress of publishing into taskbar just like it happens in chrome when we download some file.

In Service Studio, Allow double-click to toggle entity attribute property values. e.g., "Is Mandatory" = "No" (by default). Double-click the "No" to toggle it to "Yes". Double-clicking the wide "yes" bar background is faster and easier than locating the drop-down arrow, and then selecting the other value. Also, when navigating via tab, consider allowing the "space" key to toggle the value. This is also faster than having to find the Y or N key. For property values with more than two options, just iterate through the options. PS: As a new user to Service Studio, double-click and space were the first options I tried in both navigation scenarios.

Libraries always seemed to me like a good place to upload some resources like images and fonts. When trying to place fonts, I ran into a problem of not being able to set the deploy action to "Deploy to Target Directory", as the option is blocked. Could this restriction be lifted?

I find my self many times in a scenario that I have to find an specific list element and delete it... or have to do a for each to check some condition to delete or not that element. So will be very hand an action(client and sever) that delete list elements that matchs a condition. ListDeleteByCriteria

 Problem:If there is a suspicion of infection, old and young must quarantine themselves so that the virus does not spread further. This is where the first problems often arise. Who is going with the dog? Who can bring me food? How can I keep my child busy with schoolwork?It is particularly difficult for older, but also very young people to bear this isolation. SolutionThe solution could be an application that connects neighbors and helps to manage these everyday things.features:1. neighbors nearby offering help like walking the dog or shopping.2. calendar to arrange appointments with the neighbours3. payment system with which these small services can be implemented for little money (with the dog go 0.30 cent for example)4. video chat for children in the same class, so that they can do homework together, or just chat.5. webshop for food, where affected people can put together their food and the supermarket packs it up and hands it to the helpers who then take it home.

Recommended and filtering enhancements can improve the current OutSystems Forge search experience. Smart Search Using AI: Based on the user's query, leverage Natural Language Processing (NLP) to propose suitable components. For instance, searching for “email service” should fetch SMTP, SendGrid, or Mailchimp connectors to be used. User-Based Component Suggestions: Based on app type and previous developer usage, suggest recommended components relevant to the user's previous actions. As an illustration, other fintech tools can be suggested to a developer who has previously used a payment gateway module.

It would be helpful to be able to import/export OML data about a module to a structured plain text file. This would allow developers to use git for storing code changes. Using git could solve branching/merging and code review concerns for changes to modules in the platform without having to build those features in Service Studio or other management tools. Features that would be helpful related to this Export an OML to structured plain text (xml, json, yaml, other). Import from plain text into service studio. Deploy using this format (ties into using third party CICD to deploy to various environments. Ideally, branching/merging, code reviews, unit testing would be more fully implemented in OutSystems but this feature would allow a "quick win" for teams trying to achieve this functionality.

Guys,If the "Manage Dependencies" window only shows the used dependencies by default, It would be more time saving when I just want to refresh dependencies that I already have.Even with the performance revision you made recently on this screen.  On a recent dev environment it takes sometimes 2-5 sec do show ALL modules I have, to create new dependencies, and almost all the time I just want to refresh the ones I already have.I know that there is a button to strict the collection, BUT the data was already loaded and the time has already taken.Please consider this.

When working in lager factories or those with a lot of references so some modules it would really help to sort the publish list where incompatible messages are shown last. This would help a lot with notifing the user that is publishing that module  there are incompatibles that needs some 'work'. A warning message would also do this trick.See this screenshot for example: