Just like Service Studio, it would be great to have an auto-update feature in Integration Studio as well. This would streamline the upgrade process and ensure consistency across tools.

In the Architecture Patterns in ODC course, it would be very helpful to have simple examples of how to apply the patterns mentioned along the course.

Outsystems can provide a direct multi-select dropdown widget which can be useful in most of the applications since multi-select dropdown is more often used everywhere in forms, lists etc.

If you try and install a component from the forge in to ODC and it fails, it gives you absolutely ZERO information as to why it failed, and there's nothing in the log. Please can you add details to the logs when forge components are added to ODC. During Install: Then it fails: There is no useful information about how to solve the problem, especially as it marks ALL the dependencies as failed, even though they show as installed successfully at first.

In multiple enterprise conversations, a recurring concern I encounter is around long-term platform dependency and source code ownership. Prospective clients often ask whether, in a worst-case scenario or strategic pivot, they would have the ability to access and operationalize their application source code independently of the platform. To address this more effectively during pre-sales and architecture discussions, it would be extremely valuable to have a feature in the trial or demo environment that allows export of the application source code in a structured .NET format that can be deployed in a standard .NET setup. Having the ability to demonstrate this live would: Instantly reduce perceived vendor lock-in concerns Increase architectural confidence among CTOs and enterprise architects Accelerate decision cycles during evaluation Strengthen positioning against traditional custom development arguments In many cases, the hesitation is not about capability; it is about control and reversibility. If we can showcase that portability exists in a tangible way, it materially improves conversion confidence. This capability would significantly enhance enterprise adoption conversations.

Hi Guys,It would be great if we could access the findings from the Architecture Dashboard from an API.  This is very useful to connect with CI/CD pipelines. Sometimes we had an Architecture team looking for all projects and if we could aggregate the info in one external tool is a must have for us.Best RegardsFabio

 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!

Currently we have to use non -native methods to enable popup closing by clicking outside. It would be interesting to have it natively.

For example 30 people are working in same environment in a same project. Some times multiple users publishing the same module, currently it goes to uploading state and finally gives concurrent publish error. If the button is disabled and gives an message of "Other team member is publishing this module", it will save lots of time for developer. In my scenario we work with clients in remote, so for publishing only we spend lots of time for this scenario.

When we are developing in Reactive, if we have several data aggregates or data actions in the page, at start this data actions will launch in parallel, not delaying the rendering of the page. But when we refresh the data on an action flow, the flow doesn't continues until the data is fetched. It would be great to have an option to modify that behavour, because sometimes we dind't need to wait for the data to get fetched to continue with the flow, sometimes we only refresh data to update something on the screen