when you upgraded or install a new platform server..- you have to install .net framework manually- configure iis manually- use the configuration tool- do a commandline command updatedb- start services- do a commandline scinstall- update recheck licence.why can't we have this all in 1 wizard and/or unattended install with a config-script.

This is just a small detail, but when we have a big For each label, it will be overlaid with the "cycle" label.The improvement idea was to center the label cycle across the arrow.I have a screenshot attached.

Title says it all. :)J.Ja

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

Hi,The use of domains is essential when doing factory governance, but this concept is stuck only in discovery. This concept is also essential in Architecture Dashboard, Service Center and Lifetime analytics.- ArchitectureThis is where it's more important because domains are the top of our architecture and we need to have this vision. It will facilitate domain technical debt control and facilitate reports.- LoggingIn service center and in Lifetime Analytics it would be great if we can filter all data by domain also, because this is our top level on our architecture and we need to have this top vision (errors, page accesses, general logs).In Lifetime analytics it will be great also if we can see the performance by domain an then we can start drill down, but this top level architecture vision is important.

For security reasons, it would be nice to have an option to enable obfuscation (scramble) for all automated Outsystems' javascript code for reactive applications.

Add a new client action for System event for when the mobile app is updated (through dehydration).This way we can add specific logic to treat properly this situation (toggle features, start sync, improve user experience, add analytics, etc...)

 It would be great if any new ODC forge component could be listed in OutSystems Community newsletters , as daily digests.

Hi OutSystems Team, In the OutSystems Support channel , implement a time tracking rule based on SLAs , as some clients use this metric and end up counting elapsed time, which is incorrect. When the issue remains on the client's side, the SLA should not count, or if the client "disappears" and does not close the ticket, this time should also not be counted. This helps OutSystems protect itself from misunderstandings and potential penalties (fines) from the client, which could lead to misinterpretations. The current view considers tickets as either open or closed. Time tracking helps with OutSystems' resolution metrics and protects the company from other interpretations and metrics. It would be beneficial if this data were exported along with the ticket ( spreadsheet generation ).

When creating a new application in Service Studio, I really appreciate how the platform automatically extracts the primary theme color and generates a default logo based on the uploaded application icon. This greatly helps with the initial branding setup. However, I’ve noticed that the favicon is not automatically set in the same way. It would be a great improvement if the favicon could also be auto-generated or defaulted to the uploaded application icon, just like the logo and color theme. This would ensure a more consistent visual identity for new applications right from the start, without requiring additional manual steps. Thank you for your continuous improvements and for considering this suggestion!