Please add the ability to upload a demo app for ODC External Logic components.

You always have to use the Swap Connectors because True has to go down and False to the side for the exceptions.

When perfform a release via LifeTime, in case dependent applications need to be published. But you don't always want this.In large factories, it's a lot of work to unselect all dependent applications.As select/deselect all button would be a nice feature.

When on the ODC Portal, the user can view and configure the apps that are in each Stage, however, the navigation through these can be enhanced. Currently, when the user accesses the Apps menu, and then opens an Application, the Stage is always set as Development . Even if the users change the Stage to QA for instance, when navigating back to the Apps list, and opening another App, the Stage is reset to Development . This is annoying because if the user is performing a considerable amount of configurations, he/she is always obliged to change the Stage for each App he/she wants to configure. What do you think of keeping the value of the Stage in a client variable? This way it would facilitate a lot of the scenario described above as it would be a lot less clicks to reach the same goal.

To have a 'Find Usages' function for API clients created in ODC portal. When we expose API thru libraries, we can add ClientId and ClientSecret as settings. Then we will add the values, in the actual consumer app settings in ODC portal. Since there can be a lot of application using same ClientId and ClientSecret, it will be useful to have a 'Find Usages' for the actual API client created. This will allows for easy governance, and also ensure the correct app is using the correct API client.

That's about it.Add output parameters in WebBlocks so you can reuse the data on parent screen or block.

When evaluating the last versions of Service Studio, it is not possible to identify on which versions a bug was present on. If possible, it would be great to know which versions are affected by a specific bug. e.g. Version 11.54.76 "Fixed an issue that was preventing memory from being released. (RDEV-7567)" Is this bug only in the 11.54.75? Is it since ever but with low impact? This information would be great to identify the need to "update" the Service studio version on the all factory.

 Allow line breaks in translated text fields within the built-in translation interface. Currently, when editing static text directly on a screen (e.g. by double-clicking a text element in Service Studio / ODC Studio - we are using both now), it is possible to insert line breaks. These line breaks are preserved and correctly rendered on the page. However, when translating the same text through the translation interface, the translation field is limited to a single-line input. There is no way to insert line breaks in the translated version of the text . As a result, any original formatting that relies on line breaks cannot be reproduced during translation. The only current workaround is to export all translations to Excel, manually locate the relevant rows, insert line breaks inside the Excel cell (Alt+Enter), and then re-import the file. This process is slow and cumbersome, especially when correcting or updating a single translated text after a small change in the original. It also increases the risk of accidental edits, typos, or inconsistencies when handling the export/import file The translation interface should support line breaks directly in the translation field (for example via a multi-line input or allowing a keyboard shortcut such as Shift+Enter). This would allow translators to preserve the intended formatting of the original text without relying on the Excel export/import workaround. Thank you very much in advance!

It would be great to have OutSystems Developer School and bootcamps in south america time zone, too, it would be easier to learn in the morning

Allow creating an action from the selected section of a flow. The action would get the required inputs and outputs, and the flow from where it was extracted should automatically fill the action parameters with the local variables it was using