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

OutSystems already makes it incredibly easy to work with well-defined JSON by using structures and auto-mapping features. This is a huge time-saver for many use cases where the JSON format is stable and known in advance. However, as applications scale and start interacting with more dynamic or external APIs, developers often encounter more complex and less predictable JSON formats — ones that include dynamic keys, mixed-type arrays, deeply nested objects, or optional fields. Currently, handling such JSON in OutSystems often requires workarounds like JavaScript, server-side logic, or external services. Introducing more native low-code tools for advanced JSON manipulation would reduce complexity and enhance developer productivity even further.Key Suggestions (all optional, modular enhancements): Support for dynamic keys in JSON structures Example: { "user_1": {...}, "user_2": {...} } Allow mixed-type arrays in a single list Example: [ "Hello", 123, true, { "x": 1 } ] Enable handling of deeply nested arrays and structures Example: { "matrix": [[1, 2], [3, 4]] } Introduce JSONPath-style querying for deep traversal Extract a value like "c" from { "a": { "b": [1, { "c": true }] } }. Improve error feedback from JSONSerialize and JSONDeserialize Provide clearer debug info for mapping failures. These improvements will not only maintain the simplicity of current low-code development, but also open the door to more reliable integration with complex APIs and data formats, without disrupting the existing patterns used by the community. In one of my recent cases, I was not able to integrate a polygon type structure(standard) from the customer API, so I had to ask for a change in the structure. So after this implementation we can get a solution to this problem.

This idea proposes an optional feature to export an OML as a read-only .NET project for inspection and analysis purposes.

After analyzing application dependencies, if an application doesn't have the compatible dependencies, this warning is shown: " [App X] may not run as expected Installing this app may not run as expected and will impact other apps due to incompatible dependencies . To safely install [App X], it might be necessary to update [App 1], [App2], ... and [App N] to compatible versions. ". It's not clear what will happen if a user installs this application. Does this mean that the application we are to install will not work correctly because it's dependent on other apps that are not compatible or can this install also break something in the environment? Normally only the installed application will not work as expected and it should work fine if we solve the dependencies issue. But having the mention that "and will impact other apps due to incompatible dependencies" creates doubts on if we will damage anything in the environment. If nothing will be harm, then this text should be removed, and only be left the information that the app to be installed will not work as expected. In case the app could cause any harm to the environment, then this should be detected and that warning should be shown only in case it can cause any damage to the environment.

Can we have a built-in Multilevel Dropdown widget in OutSystems? The dropdown should support: Submenus inside dropdown items Further nested submenus (multi-level hierarchy) Dynamic data binding for all levels Styling and interaction similar to menus in modern web apps This would be especially useful for use cases like: Country → State → City → Area selections Product Category → Subcategory → Item Any scenario that involves a tree-like structure or hierarchical selection

In advanced queries, It would be useful to see all the attributes of the output structure or entity.I should be able click my output structures and see all the attributes of that structure or entityFurthermore, if the query output is an entity, clicking on a specific attribute should select that attribute in the query.

When debugging a Module, it's possible to use Step Into to execute assignments one by one (instead of executiong the entire Assignment Statement at once). This is a great feature, but it could use some improvements:There's no visual clue this happens. The "cursor" (arrow) stays on the Assignment Statement node, until the last of the assignments has been executed. It would be great if the Assignment would open in the Property Pane (where it normally opens when clicked), with the cursor/arrow pointing at the currently executed line.The Step Into steps into everything , including User Functions. If the first assignment uses a User Function, that Function is stepped into directly, which can be confusing. So if 1 above is implemented, SS should first show the cursor at the first assignment, before executing anything. Also, it should then be possible to use Step Over / Step Into / Step Out having a scope for that Assignment Statement (so Step Over executes the current assignment, Step Into steps into the first User Function, Step Out executes all assignments and returns the cursor to the next Statement to execute).If 2 is implemented, also make sure to select (or otherwise mark) the User Function, if any, so it's clear what the user is going to Step Into. If there are multiple User Functions, they should be marked one after the other.EDIT: The above should also go for Structure/List mappings.

If we have an application with very complex structures nested or related with each other (created manually or loaded from a WSDL), it would be very helpful if we could see those relations in a diagram similar to the one the platform has for entities. Not sure the proper name for such a diagram though...

When copying and pasting in Service Studio using the keyboard shortcuts, the elements are pasted in the top left corner as opposed to the right-click paste which will paste close to the current position of the mouse pointer.I think it would add some consistency if the CTRL+V action also drops the elements close to the current position of the pointer.

Hello, I think to have a option to disable the manual swipe on StackedCards would be a very usefull feature. Thanks, Paulo Torres