Problem: Personal Environments cost OutSystems unnecessary AWS compute time, but deleting them frustrates developers who lose their apps unless they manually export them. Idea: Make Personal Environments ephemeral but with automatic daily app snapshots, so they can be safely deleted sooner without hurting the developer experience. How it works 1. Daily App Snapshots Automatically snapshot all apps/modules once per day. Store snapshots in cheap object storage. Only snapshot OML + metadata (default: no DB data). Developer never loses their apps again. 2. Faster Environment Recycling Only do this if needed to offbalance the data usage in point 1 Reduce always-on uptime from 7 days to 4 days. After 4 days of inactivity: Kill the AWS compute Keep the daily snapshots 3. Auto-Restore on Spin-Up When a user requests a new Personal Environment: OutSystems spins up new infra Automatically reinstalls the most recent snapshot Developer resumes instantly with their apps already there Benefits For OutSystems AWS savings (compute reduced from 7 to 4 days). Storage cost minimal vs. compute cost. Personal Environments become fully elastic. For Developers Apps are never lost. Personal Environment deletion becomes painless. Better trust, better onboarding, better learning experience.

When working with Advanced SQL actions, there is the option to add test values to the parameters, and run the query with them. The executed query is shown in the "Executed SQL" tab, which is great. However, it would be very helpfull if that query could be extended with the parameters used. e.g. declare @company_id int; set @company_id = 3; SELECT [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[ID] , [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[NAME] FROM [OSDEV1].dbo.[OSUSR_WU3_COMPANY] WHERE [OSDEV1].dbo.[OSUSR_WU3_COMPANY].[ID] = @company_id That would make it possible to copy the query with the used parameter values, and paste it in the database tool and be able to run it directly (instead of having to configure the parameters again). Please note that this is somewhat related to this idea, but I believe my suggestion is better: https://www.outsystems.com/ideas/8176/show-real-value-on-advanced-query-executed-sql/

A ranking system for the Mentor Program where mentors earn points based on sessions they conduct. As their points increase, their ranking improves, helping us easily identify and connect with the most active mentors.

 Challenge: Currently, widgets in Service Studio don't have names by default. Developers typically only assign names when they need to manipulate widgets in business logic. However, widget names are essential for test automation because when a name is defined, the generated HTML element ID includes a static part (based on the widget name) alongside the dynamic part. This static portion can be used as a reliable selector in test scripts. Without named widgets, HTML element IDs are entirely dynamic, making test automation scripts fragile and prone to breaking whenever screen changes are made. This forces QA teams to constantly update test selectors. Proposed Solution: Auto-generate unique default names for widgets within each screen (e.g., Button1, Button2, Input1, Table1). This would: Provide stable HTML element IDs for test automation without requiring manual developer effort Make test scripts more robust and maintainable Reduce the time spent fixing broken tests after UI changes Improve overall application testability out-of-the-box Trade-offs: This would make the HTML slightly more verbose, but the impact would be minimal compared to the significant benefits for test automation and quality assurance workflows.

A mobile application that allows developers to join User Group events anytime, even when they don’t have their laptop. This makes event participation easier, increases accessibility, and encourages more developers to attend and learn from OutSystems community sessions.

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 :)

When changing locale of a screen, in multi-lingual applications, everything is translated, except validation messages. The validation message is displayed in the right locale when triggered, however, if the validation message was already added, and then the locale changes, the validation messages are not translated to match the new locale. To translate the validation messages, the user has to trigger the form validation again.

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

In each training video on the OutSystems learning platform, include a “Schedule Call with Mentor” button (as shown in the attached image). When clicked, it can redirect learners to the ADP mentor list, allowing them to easily schedule a mentorship session. For freshers, this feature would be extremely helpful to learn faster, clarify doubts instantly, and gain confidence in their learning journey. Currently, many newcomers know about the forum, but not about the mentorship program. By placing this button directly within the training page, it encourages them to explore and connect with mentors proactively.

I would like to suggest having option to enable or disable logging for each service action by adding optional parameter to service action "Enable Logging" by default true but developer can change it to false. Something similar to log email content. I understand service action has same behavior as Rest API so it has 3 logging options (Default, troubleshoot, Full) but this option used per module so its affecting all service actions into the module but sometimes I need to change logging for one of service actions only. We faced a case that we have service action that has too much traffic calling it so it log every hit to API log table into OutSystems Log database which causing a huge increase into size of table although our logging level is default. It is not important or no business need for us to log this action so we stopped logging for service actions into this module to avoid this increase. As another workaround we replaced this service action with server action. We are using O11