I would like to suggest improving the loading animation in the Service Center when applying filters or performing actions. Currently, the indicator is barely visible and only appears if you scroll down, which makes it difficult to know whether the system is processing, still loading the filters, or if the action failed. At the moment, there is only a small loading bar that becomes visible when scrolling. A clearer solution could be to add a button‑loading or a loading indicator next to the filter button, so devs have immediate feedback that an operation is in progress. Filtering: Loading not visible The red loading bar at the top only becomes visible when you scroll down.

 New functionality: It would be nice to select some logic nodes, right click and "🔒 lock" them. How it will affect the developer? When you want to do changes, you have to unlock the nodes and provide a comment/reason why you want to change them. Other effects? During the merge or code update, all commented changes are shown so each developer knows something happened there. This would be a good functionality to protect Interface-code or some heavy business logic that normaly does not need to be changed. When would this come into play? Replace All / Find'n'Replace might change code that should only be changed with care APIs/Interfaces might be changed because of a call or so, but more than just one person should be informed about this Law relevant logic might be changed etc.

 Problem: The procedure of changing themes in OutSystems is by and large a process of trial and error. Developers need to update styles and check each screen separately, which takes a lot of time. Enhancement: Introduce a live preview editor for themes that reflects changes automatically on all screens. Developers are free to change colors, fonts, and styles and they can even choose not to publishing or navigating between screens and yet see the result. Benefits: Time is saved as the user is not required to test and switch between screens constantly. The customization of themes is brought about in a quicker manner and with less effort. The look of the app is consistent throughout the entire ‍‌‍‍‌‍‌‍‍‌application.

Hello,Since it is very hard to get access to the database credentials for the Outsystems enterprise licenses, it would be very useful to have a button to export aggregate/advance query results to an excel file, and the service studio could download the file.This feature is very handy for QA environments when sometimes developers don't have access to deploy code but they can see it.Regards,

Currently, if we define a Sorting by an attribute, that sorting becomes unresponsive after introducing a Group By in the aggregate, as the sorted attribute is no longer part of the aggregate output . This does not raise any errors or warnings in the TrueChange Tab or any signaling in the workspace. I find that this is an easily overlooked situation that can lead to unexpected behavior or inconsistent results. I suggest the implementation of a typical Outsystems background validation that triggers a warning (written on the TrueChange Tab and a visual cue on the aggregate) whenever the aggregate's sorting references attributes that are not part of the aggregate output after a Group By, ensuring consistency and preventing silent issues.

I would like to be able to consume REST API's with the  - preferred - OpenAPI  YAML document format

The Julian Number to Date Converter on the ODC platform enables users to quickly and accurately convert Julian dates into standard calendar dates. It simplifies date interpretation for datasets that use Julian numbering, ensuring consistency, readability, and error-free date handling across analytics, reporting, and operational workflows. This utility improves efficiency when working with legacy systems, data integrations, and time-based calculations within ODC

Hello community! Today, I want to talk about an idea that I believe may not be entirely new, but I haven't seen many approaches to it, so I decided to write it in a more structured way. (The most similar idea I found was this: Translation Teams ) The idea is allowing community members to contribute in translating OutSystems documentation. I'll explain why and how I envision this implementation. Why? Regardless of the language we speak, we all prefer reading and hearing our mother tongue, as it resonates differently in our hearts. A study in the NeuroImage journal concluded that there are structural differences in the brain connections of people with different native languages. ( Native language differences in the structural connectome of the human brain ) If our mother tongue influences our brain in this way, it will undoubtedly impact how we learn, whether in our native language or in a language learned later in life, such as English. Considering this, I believe translated documentation can significantly enhance a user's information processing, accelerating their learning and development . But what about English? We all know it's crucial for developers to read and communicate in English for various reasons. Documentation helps in this! Yes, I don't deny that. My goal is not to translate all content or dismiss English . I propose implementing translation to help in studying/understanding documentation. How? The idea is simple. Community members submit translated documentation to OutSystems. The translation team (if it exists) reviews and, upon approval, makes it available. Questions may arise: How many languages? Translating documentation into every language is unrealistic. Initially, I suggest translating into the world's top 5 or 10 most spoken languages, covering a large audience and gauging project success. Members suggesting translations? That's crazy! There could be errors or trolls! Various measures can prevent these scenarios. I propose limiting the number of members suggesting translations: - Only active or higher-ranked members can suggest translations; - Members with specific certifications/proven technical knowledge can suggest translations; - Only MVPs or Champions can suggest translations; - Members must apply for a "translation program", proving linguistic abilities for specific articles/languages; - A combination of the above. Members could use tools like Google Translate or AI! True. For that members might be evaluated for translation skills, and OutSystems could verify translations. Using translation tools doesn't necessarily mean poor quality; it just requires validation. OutSystems just did this with AI translation for Japanese! Yes and no. While OutSystems' implementation is excellent for forums, it may not suit documentation. AI may not grasp documentation contexts, leading to empty translations. Reliable translations by professionals understanding the original message, context, and technical aspects would be more valuable than AI translations. This is my idea. It's complex and may not be as easy to implement as it seems. It would take time and effort, but I believe it would be a great addition to this constantly evolving community in need of skilled developers. This implementation would not only expand OutSystems' reach but also enhance every user's experience and learning! Please share your thoughts on my idea. If you have questions, ask, and I'll respond if I can. Support it if you find it valid and would like to see it implemented. Cheers, Mauro Alviza

Please add the ability to upload a demo app for ODC External Logic components.

 Free Tier - personal environment w/ 1Gb data Middle Cloud Tier  - $20/mo per server with 10Gb data, 50 users, and custom domains but without enterprise customer support Middle DIY Tier - $10/mo per Outsystems platform server instance Enterprise Tier  - $1600/mo for enterprise environment/support