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/

One of the purposes of publishing a solution, is to refresh all modules in it, and reflect a change of an upgrade. What I propose, is to remove unused dependencies between the defined modules in the solution. I recommend for it to a configurable option. But it would be helpful especially in big projects, where the architecture is big and complicated. Also, it could be a helpful option before checking the architecture in Discovery. Before the check we have all modules refreshed, and all unnecessary links broken.

An AI within the development studio/canvas that analyzes complex Aggregates and SQL queries and suggests performance improvements. For example, it could recommend creating new indexes, simplifying joins, using CTEs or temp tables or using more efficient filter patterns based on the data model and query structure. This could be a more granular version of the existing AI Mentor.

Hi everyone,I spend a lot of time inactivating the users who should not have access to an environment for some reason. What I would like to suggest is for us to have the ability to set an expiration date for each user that is not an administrator.This way I can easily manage the users on my factory especially when we have outsourced developers.

 The BaseTheme used in Outsystems, as like most of the designers in the market, use the   multiple of 8  rule to create sizes for margins, padding, font sizes, grids... So, if BaseTheme uses the same rule for variables for everything why not use it in the Style Tab too?   Benefits : Less maintenance , Easier for the Develop team to match mockups margins and paddings. Less frustration,  Help experience between the Develop team and the Ui/Ux/ FrontEnd teams easy and softly. Less work for the FrontEnd team finding wrong margins and paddings. Apply best practices , (One-click change everywhere) , Even if there is inline CSS (which isn’t the best practice) when the variable is changed on the theme, the value is automatically updated everywhere. CSS learning ,  Make the Develop team more familiar with the CSS variables.

As requested by OutSystems Support Team, I am creating this Idea because it's important that the build log for any compilation on mobile on ODC be similiar to what we have in O11. Today, the mobile build is a huge amount of text that can be difficult to understand what is the main reason your mobile app is not compiling. In O11, it's more easy to understand. Maybe on ODC, put the main error on the top (or at the end) of the file so the developer can easily identify the root cause of the APK/IPA being broken upon compilation.

 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.

Branching could be useful in different situations, some more relevant than others, but on big factories with a team with several developers, it could be very useful.A situation that occurs frequently is when we receive a change request which requires changes on core entities, this will break the environment , and will affect other developers that are working on a different feature, but are prevented of testing/developing without pain since the environment is broken.So it would be great of having an way of creating a branching per pta of a solution, were the developer could make the change that will break the environment isolated, finishes the development, could test it isolated again (remeber that i've mentioned a branch of the solution), if everything is ok, perform the merge of the branches, create a new solution and schedule the publish.Im mentioning PTA was a way of doing it, it could be by branch, if it was possible to work on different espaces on a context of a branchIf i was a smoker i would quit smoking with this feature :)

GraphQL is an API standard that provides a more efficient, powerful and flexible alternative to REST web services.Source: https://graphql.org/

Make it possible to consume Service actions from within a library. Within a library I can consume a REST API, but can not consume a service action. A REST API gives additional overhead in respect to a service action call, like additional authentication and autorisation. In a service action this is all safely handled by OutSystems.