Enable users to dynamically adjust the number of column controls (e.g., 2, 3, 4, etc.) directly by clicking on the column control itself.

When creating a new app I would like to have descriptions whereever possible. Some are currently set, some ar not, e. g. see screenshot.

Please can you provide an option to use the uploaded Demo as a Try Now option, hosted on the forge server. Currently, if you don't have a corporate account/server you are willing to make publicly available, you have to use you personal account for the Try Now , but that expires and gets deleted every week or so, causing the Try Now to die.

The help page you are given a link to when publishing from ODC to the Forge is completely blank. Can someone add some details please?

Cache is great in some situations, but it could be used in many more if we could invalidate specific records of the cache, instead of the whole tenant. A simple example: I have an action that returns a user's teams. I'm always calling this action and the teams change very seldom, so caching this action greatly improves performance. I know that the cache for this action is only invalid if someone changes the user's teams, so, if I could invalidate the cache when the user's team are saved I could potentialy run that code only once per user, after an update. At the moment I don't dare to cache that information because it's not acceptable for a user's teams not to change after a save and invalidating the whole tenant's cache will cause scalability problems if the application gets enough users for team changes to be relatively frequent.

For improving WCAG compatibility we need OS to include a couple of additions when it generates an error message. For a screenreader to pick up the warnings/exception messages the platform should include a ARIA role like: role="alert". I see no reason why these shouldn't always be included. ( also when de accessibility feature is disabled ) Additionally, it should be possible to tab to the message so that it can be dismissed; currently the keyboard-focussable is off, but it should be on. We are now reverting to popups as these are requirements for a successful implementation of WCAG compatibility.

I have two suggestions to enhance the private messaging feature on the OutSystems platform ( https://www.outsystems.com/profile-messages ): 1. Add Edit Option for Sent Messages Currently, there is no option to edit a message after it's sent. It would be helpful to have an edit icon or option to quickly fix typos or update the message content without sending a follow-up message. 2. Allow .OAP/.OML File Uploads in Private Messages As of now, only image files can be attached in private messages. It would be very useful to support attaching .oap or .oml files as well, especially when discussing technical issues or sharing modules privately. Please consider allowing these file types or increasing the file size limit to support them. ⚠️ While the forum allows these files, private messaging is preferred when sharing sensitive or internal information.

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.

To make OutSystems more powerful, the Forge should integrate with third-party platforms like: AWS, Azure, and Google Cloud: One-click deployable AI models, APIs, and cloud services. Business Apps (SAP, Microsoft Dynamics, etc.): Pre-built connectors for seamless integration. Open Source & No-Code Tools: Integrate with platforms like Zapier, Make (formerly Integromat), and Power Automate.

In some situations merge could be automatic... if i've changed a part of an espace, and the current version of the espace has changes on a different part, why not just receive an warning with "Auto-Merge" or "Merge"