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.

When using Dropdown Search widget, selecting an item, then changing the locale, the dropdown loses its selected value. Here we have an example of a dropdown search items, one that has the selected value(s) assigned as the StartingSelection, and the other has the StartingSelection set to null. An option was chosen, in our case "Ben White". When the locale changes from English to Arabic, we can see that the one that has the selected items as the StartingSelection retained the selected option, the other did not.

Dropdown Tags widget puts a margin at the end of the selected value, in order to create a buffer between the value and the action in the end. However, in pages with right-to-left direction, the margin is not reversed, it remains the same. It may cause an issue of the selected value overlapping the widget actions. Here is an example of LTR & RTL pages: English Arabic

When using Dropdown Tags widget, selecting an item, then changing the locale, the dropdown loses its selected value. Here we have an example of a dropdown tags items, one that has the selected value(s) assigned as the StartingSelection, and the other has the StartingSelection set to null. An option was chosen, in our case "Ben White". When the locale changes from English to Arabic, we can see that the one that has the selected items as the StartingSelection retained the selected option, the other did not.

A propose a public bug tracker for issues in the OutSystems platform. I understand why OutSystems would be reluctant to do this but here's some advantages: Transparency : a public bug tracker shows commitment to transparency and accountability, building trust with the community and customers. Community Collaboration : it allows users to report bugs, suggest fixes, and contribute to the platform's development. Improved Communication: users get visibility into the status of reported bugs, avoiding redundant reports. Prioritization by Demand : users can vote on issues they care about most, helping OutSystems prioritize fixes based on real-world demand. Knowledge Sharing : a public bug tracker serves as a centralized knowledge base where users can search for known issues and workarounds. ( Disclaimer: an LLM did help me write some of this ) The motivation of this idea comes from the time wasted recently creating support cases for problems that were already identified by the OutSystems team. Many of these problems have forum posts with dead ends, where people were left without an answer. I would imagine this would also free up time from the support team. Cheers, Tiago

Ability to zoom in and out in the main window in order to have a better control when inserting or moving elements.

Hi guys,A question that everyone has been asking after changing the certifications, and with this I think that was pleasing to many ... is why the specialization in Mobile does not appear in the Diploma that we download. I think it would be an asset to have this information also present in our certifications (and specializations) diploma from OutSystems.Cheers,Miguel

The option to remove unused dependencies by eSpace is realy great! But I think it can be implemented to Applications at all. It wold be nice to have an option in ServiceCenter to remove all unused dependencies by an Application.

Hi all,I would like to request an addition to the configuration tool/ server.hsconf.More and more we run into customers hosting there OutSystem platform in Azure resources segmented in a dev/tst, acc and prod subscriptions, resource groups, ect…. Each segment with its own servers, scale sets and a SQL managed instances to provide database needs. With an Azure Active Directory tenant to provide users authentication for the platform, and no “real” AD in sight.On the application side this handled beautifully by OutSystems. But in the situation above we are currently forced to use SQL authentication because there is no option to manage user authentication for the back end via ADD.Can you please add the option to use ADD users, service principals and/or managed identities as an authentication mechanism in the connection between the platform and an ASMI?! This for manageability and security benefits.Thanks in advance!

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.