If Solutions also saved effective value of site properties for current version rollbacks would be much easier.

Enhance security by adding a property on screens to encrypt input parameters. This will eliminate the exposure of sensitive data, like IDs, in query parameters, mitigating security vulnerabilities and promoting best practices. Additionally, this feature will save developers time and effort by automating a task that currently must be done programmatically.

On OutSystems website there are certain documents to which normal users don't have access. For instance the ODC One Shot Migration document. I understand there must be genuine reasons for not making the content public, however, in that case I would expect the navigation or embedded links also be hidden from users who don't have access. This would help to avoid unnecessary confusion or any assumptions being made.

It will be nice, if WhatsApp and mail sharing options included in forge asset actions.If an outsystems developing friend or colleague wants some sort of assets for their learning or work, then if we find the similar asset , we can easily share them via whatsapp or business mails.So kindly add this feature for faster reachability of Outsystem Assets.

Although we can change properties to multiple elements selected in Service Studio (like Description, Public, Function properties and Cache in Minutes for Service Actions), it would be nice and way more efficient if we could also change the icon for multiple selected elements rather than one by one.Below we can see how we have the Change icon option in a single service action:But when we select multiple service actions, the option is no longer available.

OutSystems' support for null values has been a topic since at least 2010. (See https://www.outsystems.com/ideas/213/null-values/ ) Since OutSystems has not provided a solution to this problem, they should at least provide comprehensive documentation, best practices and forge examples for handling nulls. Documentation for handling nulls for both APIs (integrating with external systems) and Databases should be provided. OutSystems' implementation of nulls can impact OutSystems applications significantly . Proper handling will reflect positively on the OutSystems platform. Improper handling will reflect poorly on the OutSystems Platform and will limit the use of OutSystems for more technical applications. If OutSystems chooses to provide this much needed documentation and needs input or review, I would be happy to help. Please contact me. Thanks to all who have posted solutions in the forums. Thanks OutSystems for a forum where we can make requests, share solutions and ideas.

The extensibility configurations used on the mobile application, should have a possibility to change per environment (dev, qa, production) without having to open the module in the environment and publishing a new version.This situation causes the espace to have a different version/change on this environments (which in certain cases only means that the setting in this environment is different).This type of changes are very common with mobile plugins that require a setting for non production environments and another to production ones.I would suggest that this could be changed either on lifetime or service center when defining the mobile generation of the app. This setting will then override the one default one defined on the espace. Something similar with the effective url settings that exist on the Soap/Rest integrations in service center.

Create a single, global collaboration platform exclusively for OutSystems User Group Organizers to connect, share, and co-create. This platform would act as a community backbone, enabling organizers worldwide to: 🌍 Discover upcoming and past User Group sessions globally 📚 Share session decks, recordings, notes, quizzes, and formats 💬 Discuss ideas, challenges, and best practices 🤝 Call for collaboration on joint sessions, meetups, or masterclasses 🧠 Brainstorm unique, proactive, and high-impact session ideas 📣 Invite other organizers or speakers for cross-region events

Since array functions are usually 'quicker' than database functions, I'd really like to see some additions like:- ListSort(List,"Fields") ; QuickSort on chosen Array fields- ListInvert(List) ; Invert the order of the Listed items

As a developer or Dba-er, I want to be able to- change the default sort order of indexcolumns (default true) - create function based indexes- specify the index type- turn on and define table partitioning.I would like to have the platform to create columns using a column order which normally gives the best performance. (based on mandatory, datatype and length of the attribute)