The user should be able to export site properties, which helps in deploy between environments.

A collate definition attribute for each table/entity in the join will be useful, so as not to force the use of SQL Advanced and to reduce the risks/chance of errors in the development. By default, the collates will come with what is in the bases of origin of the tables, so that they can then be changed according to the need. We have a scenario in which we make joins between tables with different bases and one of them has the SQL_General_CI_AS collate while the other uses SQL_General_CP850_CI_AS. This shows a warning in the column of the join involved, it allows publishing but incurs a runtime error. I thing something in this position:

Css makes wonderfull things but its not easy to work with when we whant to change something, changing a litle color can make us whant to kill someone, by integranting sass-lang on service studio we can get more power managing our css. check out more info on https://sass-lang.com/

There should be ability to add unit tests automatically for any actions. Also a unit tests should be automatically added to a Core Modiules.

 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!

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

Hello OutSystems Community, Building on the theme of making Application Objects (AOs) more visible in the Forge, I have another simple but powerful suggestion. The Problem: When we search for assets, the results page shows a list of component "cards." Each card displays useful info like ratings and download counts. However, to see the AO count, a critical piece of information for assessing impact and cost, we must click to open the asset's detail page. My Idea: My proposal is to display the AO count directly on the asset card in the search results list. This could be a small and clean UI element, perhaps next to the download or rating indicators. It would give us immediate, at-a-glance information for every component on the page. For example, the card could look something like this: [Asset Name] Rating: ★★★★★ (25) Downloads: 2.5k AOs: 8 <-- New information here Benefits: Instant Comparison: Allows developers to immediately compare the AO "weight" of different components without ever leaving the search results page. Improved User Experience: Reduces clicks and streamlines the workflow for finding the right asset, making the Forge much more efficient to browse. Works Perfectly with Filters: This visual aid would be a perfect companion to an AO filtering feature. We could filter for a range (e.g., 1-20 AOs) and then instantly see the precise count for each result to make the best choice. This small UI enhancement would have a huge positive impact on our daily workflow in the Forge. Thanks for your consideration.

Hello everyone, I would like to suggest adding a placeholder for a footer in the sidebar. While I understand this may not be as critical as other issues, I believe it could enhance the overall widget experience. I'm aware of some workarounds for this, but we've encountered problems with our current approach due to the address bar's position on tablets and mobile views. We discussed this internally and agreed that it would be a worthwhile suggestion to raise. Thank you for your attention!

In Service studio, when we manage dependencies, we have an option to show only dependencies which are in use. However, in ODC studio, this option is not available. It will be great to have it there, as this is a very useful feature.

 An italian hospital ran out of valves and a company 3d printed the valves: https://www.3dprintingmedia.network/covid-19-3d-printed-valve-for-reanimation-device/My proposal is an app to crowd-source this kind of effort:- Administrators are responsible for registering and validating the registration of legitimate entities with legitimate needs- Entities make requests- The public provides solutionsThis can be implemented by a small team in a very short time and can help save lives.Most people want to help and don't know how, let's give people that chance to contribute.