One of the purposes of publishing a solution, is to refresh all modules in it. Since the developer would be aware that he/she is applying a major change, why not to add an option to remove locale unused items in the module. Just make the feature configurable.

Currently the way email customizing works is really annoying (especially theming). It would be very cool if you could use HTML (for example MailChimp templates) to use as a starting point for OutSystems Emails.

 Trigger a warning when there are output parameters that have no value assigned in a espace  action.

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

OutSystems could introduce a feature where the platform automatically optimizes entities based on usage patterns. For example, when an entity is used in high-traffic applications, the system could dynamically adjust indexing, caching, and query execution strategies without manual intervention. This would allow developers to focus more on business logic rather than worrying about performance optimization.

Hi Team,Can we not add password toggle feature in service studio switch environment screen like below?Existing Service studio snap,

Looked at the Large List Navigation Sample in the Forge today, I think this should be part of the Aggregate for faster lest memory intensive data fetching.

Improve the filters in the Application's screen: Separate the actual filter ("search applications by name or team") into 2 filters: Application Name Team Name Create a new filter to search for a module name.

here are the way if we want to create the pagination logic by the help of local varibles

When the timepicker renders, it inherits the current page locale. However, when the locale changes, the timepicker does not change its locale with it. But keep the locale it has when it rendered. Here are some examples: English to Arabic The screen renders with English locale. The timepicker uses 12-hour clock symbols of "AM" & "PM". But when the locale changes to Arabic, instead of using "ص" & "م", it is still using "AM" & "PM". Arabic to English Same issue can be detected in the reverse scenario. The timepicker keeps using "ص" & "م", as it rendered when the locale of the page was Arabic.