New Accessibility category in Ideas and new Accessibilty tag in Forums. It may be that this was decided internally as not necessary, but with accessibility becoming a must, and since it's a very broad topic, I feel that a dedicated category and tag in the Ideas and Forums, respectively, would benefit and facilitate the search for this topic.

Show who are the users online and currently working in this shared environmentThis future will be really useful to improve joint working culture.If the user is publishing then it will show their status as publishing.If they just working on it then it will show their status as online.If the user is not using the environment then it shows his status as Offline.It will help other users in the shared environment to avoid publishing at the same time.

Currently, OutSystems Service Studio does not support changing: The editor font family and font size in the Service Studio interface (Toolbox, Widget Tree, Properties panel, etc.) The overall UI scaling for high-resolution displays The language of the Service Studio interface (menus, property labels, and tooltips remain in English) While we can fully style our application UI, we cannot customize how the Service Studio development environment itself looks or behaves in terms of text visibility and localization. Most leading IDEs (like VS Code, Eclipse, IntelliJ, Android Studio) support: Font and UI customization Localization of interface into various languages By enabling these in Service Studio, OutSystems becomes more developer-friendly, more inclusive and better suited for international markets It would create more impact like Increased developer productivity and satisfaction Compliance with accessibility standards Easier onboarding of non-English speaking teams

like switching between different devices , switching between design modes in the studio

When viewing data in a table add a default sort so that the last entries appear first.I believe most of the times the developers want to see the last inserted items in an entity.At least, when I do "View Data" I always end up adding the sort...Edit: It could be an option in Service Studio.

The accelerator should allow developers to easily configure the behavior of the Delete action, providing the option to choose between hard delete and soft delete based on project requirements. This enhancement would: Improve data integrity: Prevent accidental data loss by allowing for easy recovery of "deleted" records. Enhance auditing capabilities: Maintain a historical record of deleted entities for analysis and compliance purposes. Increase flexibility: Provide developers with the choice of deletion behavior based on project needs. Reduce development effort: Eliminate the need to manually implement soft delete logic for each entity. Additionally for the existing feature, enhance the OutSystems Entity Action Wrappers Accelerator to include a built-in option for soft delete. By default, the generated Delete action should mark the entity's 'IsActive' flag as 'False' instead of performing a hard delete. This will improve data integrity and provide greater flexibility for data recovery and auditing purposes. By incorporating this feature, OutSystems can further streamline the development process and provide developers with more robust and flexible data management capabilities.

Having the possibility to remove the help from right click, because the help appears now in the same place that paste was before. So now I'm clicking it a lot of times :(This can be a option in settings, for example.

It would be great to have a native Service Studio for Apple Silicon (M1/M2 Arm CPUs), instead of running them through the Rosetta translation layer. The performance and power consumption are not ideal at the current state.

When I was looking at the download page, I noticed two version naming systems are currently in use:For the IDE, on the downloads page we see the release "tag" (eg: "Development Environment 11 - Release 12").But then, on studio, we see the version number (eg, "11.0.406.0")Again, with platform server and lifetime this scenario repeats: on the download page the tag, on the software the version number. This creates a bit of confusion when one is trying to understand, e.g., which version of the platform server to download.By looking into this article detailing the version naming system and this article detailing the release lifecycle, one can reach the conclusion that the tag on the download page refers to the release life cycle ( the when ) and the version number details the type of changes on the release ( the what ).My suggestion is first and foremost to use a single naming system both on the software and the website, to avoid confusion. But going a little bit further, I would suggest adopting a simpler system where version number is based solely on the release (which in the end is the only thing the user cares about).  If as the article I previously linked suggests, there is predictability on the release cycle, then similarly to Ubtuntu, one can even make the date part of the versioning system, naming both the release and the version after the date, and if necessary, additional numbering for minor patches.Additionally, it would be really, really nice if we had exactly this page , but with the download links on the tables.Thank you for your time,Filipe

Hi,I believe that can be a good improvement to have the possibility to disable an REST/SOAP method from our exposed APIs.With that we can maintain versions with methods under work without the need to have different versions and, I believe it's more practical :)  (like the "disable" capacity in the action flows).The idea is to have them under the API but not available to use and not present in the generated documentation.Best regards,Ricardo Pereira