The new option to publish with an added message is very nice, but too often I forget to click the dropdown arrow and accidentally Publish normally. Because there is no way to add a message after already publishing, this can get quite annoying. I suggest a simple extra configuration checkbox in the Service Studio Preferences to optionally change the "with Message" option to be the default. When enabled, Normal publish should still be available through the dropdown arrow.

For mobile apps developed by ODC, when the app detected updates on server side it'll proceed the OTA automatically. It may interupt user's operation at the time. It's better to have an interactive confirmation for user to choose to update or postpone it. mandatory update can be executed as the time on applicaiton ready or on resume.

Currently, when developer works with ODC studio, it only can save the code changes to sever by click 1-publish. A save to local feature will be valuable for developers to save their interim code changes locally before submit to server, it'll improve the collaboration and efficiency.

Currently, OutSystems primarily builds apps that function only online—with the exception of mobile apps, which utilize local storage and can be installed directly on clients' phones. However, the vast majority of applications depend on the client's online status. If the client has an excellent internet connection and a high-end device, and the app is well-designed, it works beautifully. Yet, this is not the reality in many Latin American countries, where internet speeds are often low and client devices are not always up-to-date. I have been developing for the public sector in Brazil for three years, and the main bottleneck hindering OutSystems' growth is the perception that it is slow, prone to freezing, and suffers from frequent timeouts. Even when creating a high-performance application that adheres to all best practices and criteria, we still run up against limitations regarding the client's internet availability and the age of their hardware—specifically, whether they have a modern device or at least one from the previous generation. With that in mind, I propose creating a new module—either within ODC or as a standalone product—that enables the creation of an `.exe` file for installation on client PCs, utilizing an internal database (like MySQL) that installs alongside the application. A standalone product would be ideal, as it could offer a more comprehensive feature set—such as installer-specific design elements (e.g., software terms of use screens, specific configuration interfaces, animations, icons, etc.). It would also allow for better utilization of the machine's hardware to render smoother, more complex graphics by leveraging the PC's graphics engine. Furthermore, this solution would allow OutSystems to tap into the small and medium-sized business market. I realize that this segment isn't OutSystems' primary focus, but the costs associated with this new product—or its inclusion in ODC—would be significantly lower; server-related expenses could be cut in half or more, as there would be no need to manage databases and server requests. Of course, it could be a subscription package, but one focused more on support and user management rather than the database itself. Well, that’s the idea; I’d appreciate it if you could correct me or help make it more robust. Thanks for reading this far.

Add a password visibility toggle during Service Studio Login to view the entered password

Be able to create a unit test for a Server / Service / Client (?) / Screen (?) action that shall be executed without developer intervention, for regression purposes.

Hi Outsystems teams, Since the OS charing static entity for 1 AO, to save some cost for clients, in many projects, we hardly use static-entity even though it should use Static-entity for many purposes. We need to use alternative ways to implement the static concept, like using structure, hardcode... This led the development become more complex in design, implement, and more hard-code used, but we can't spend 1 AO for just 5 records stored in static-entity like status, type, etc... Actually many projects opened just to Delete all static entity from the code to save cost. From begining we've learnt how to use Static entity, and in real project we need to learn how to not use Static entity to save AO, this make static entity very dead. Can Outsystems consider to lower the price of AO somehow like count it 1 AO = 3 or 4 static entity, or consider make it free if there are < 10 record store in static entity, this would be a great thing for Outsystems developers and clients. Thanks :)

Feature Request: Add Filter Options to "Find Usages" Results Problem: When using the Find Usages feature in OutSystems, all references to a widget, action, variable, or other element are displayed in a single list. In large applications, an element can have 100+ usages, making it difficult and time-consuming to locate the specific usage that a developer is looking for. Proposed Solution Introduce filter and search options in the Find Usages results panel. Possible filters could include: Module Screen Block Client Action Server Action Flow UI vs. Logic Usage Type (Read, Write, Call, Reference, etc., where applicable) Additionally, add a search box that allows developers to quickly search within the displayed results by screen name, action name, or module. Benefits: Faster navigation in large applications. Improved developer productivity. Easier debugging and impact analysis. Reduced time spent scrolling through long usage lists. Better overall development experience in Service Studio. Example: If an action has 150 usages, instead of scrolling through the entire list, a developer could: Filter by a specific module. Search for a screen or action name. Narrow the results to only the relevant references. This enhancement would make the Find Usages feature much more efficient, especially for enterprise applications with large codebases.

Provide a secure, built-in read-only data viewer for ODC Production environments, allowing authorized users to view entity records without creating custom screens or APIs. Benefits: Faster troubleshooting and support Reduced development effort

It would be great to have the option to mark individual training videos as Favorites or Bookmarks. For example, while following the Becoming a Tech Lead Guided Path, there are several videos that I would like to revisit later. Currently, I can track my progress through the path, but I can't easily save specific videos for future reference. Adding a favorite/bookmark option to each training video would allow learners to quickly find and rewatch important content without having to search through the entire learning path again. A simple "My Favorites" section could provide easy access to all saved videos and improve the overall learning experience.