I would really like to see some sort of "auto arrange" for Service Studio that just moves the items in an action to have nice even spacing, put the work for For loops to the side, make branches look nice, etc.J.Ja

Personal test/learning accounts have very short time limits, selected long ago, before the average wristwatch had gigabytes of storage. This has created a problem that if you don't log in to your account weekly, all your work, like forge components you may be maintaining, get deleted. Please can the timeout be extended based on community rating / responsibilities?

Since "Wake Timer" can be called via code, it would be good to be able to pass paramters to it. J.Ja

In modern mobile applications, notifications are key to user engagement. The Proposal: I suggest introducing a comprehensive Advanced Notification Management system directly within the Low-Code environment of OutSystems. Key Features: Rich Media Support: Ability to easily include images, videos, and icons within push notifications directly from the Service Studio. Interactive Action Buttons: Adding custom buttons within the notification itself to allow users to take actions without opening the app. Advanced Scheduling & Throttling: Built-in tools to schedule notifications based on user time zones and to limit frequency (throttling) to prevent spamming. In-App Notification Center: A ready-to-use, customizable UI widget that acts as an "Inbox" within the app to store and manage past notifications. Why it matters: This feature will empower developers to create more engaging and interactive user experiences. It will be especially beneficial for apps where real-time updates and quick actions are critical for success.

As OutSystems is moving away from providing licenses with unlimited ao's could we get the ao count for forge items listed in the forge?

Most of the times server actions, client actions can have multiple branches. While debugging each node is currently available it would save a lot of time if we could just hit continue and the app automatically highlights the full path the execution has traversed. The Idea is to have like a highlighted flow in the server actions, client actions, data actions etc. where developers can see exactly which flow the execution is going wrong in and make fixes accordingly. This would help debug faster, saving the time to actually understand what each node is doing and also understanding the logic on a broader level.

Quite often, I am repeating the same set of joins in queries (both normal and advanced), that I would ordinarily put in a view. Think e.g. of a CRM system that regularly needs "all active clients" or an ordering system that needs "all open orders". Of course if you need just that, it's easy to put it in an action, but I often find myself needing the result and join that with some other tables. Unfortunately, for some reason OS does not allow to define database views, which imho is a great gap. Therefore, I'd really like to see support for database views or something similar (e.g. queries you can define on eSpace level and join the result of with another query, but that amounts to the same).

The default behaviour of datetime variables in Reactive apps is to convert from UTC to local time. This is a great in a lot of use cases, but hard to work with if a user want to see data in a different timezone.In this forum question , some 'hacks' are proposed:Use datetimes as textCompensate at server side for the difference in client timezoneThe prefered solution is to let developers set the config for this automatic conversion. The default behaviour to convert is good, but make an option to overwrite the default behaviour.

As developers building localized applications (like marketplace apps for regional users), managing multiple languages manually in OutSystems can be time-consuming. Currently, we need to export, translate, and re-import resources or manually edit translations. The Proposal: I suggest introducing an Enhanced Localization Tool within Service Studio that leverages AI and modern automation to streamline this process. Key Features: AI Auto-Translate: An option to automatically translate text strings into regional languages (like Malayalam, Hindi, Tamil, etc.) using integrated AI services during development. Context-Aware Translation: The tool should understand the context of a UI label or message to provide more accurate translations rather than literal word-to-word conversions. Visual Translation Preview: A feature to preview how different languages affect the UI layout directly in Service Studio, helping to manage "text swelling" (where some languages take up more space). Centralized Translation Dashboard: A dedicated dashboard within Service Center to manage and update translations for published apps without needing a full redeployment. Why it matters: This will significantly reduce development time for global and regional apps, improve the quality of localized user experiences, and make OutSystems a more powerful choice for building diverse, community-centric applications.

When working on the theme I accidentally introduced an error by putting a square bracket in one of the lines, like the one we can see in line 92 here: This did not raise any errors on TrueChange allowing me to publish the theme and break all the classes that were below that line. Since the theme was visible in the sources of the browser and properly loaded, it took too much time to realize it was a simple syntax error. This could have been avoided if TrueChange would not allow to publish CSS with syntax errors.