Create the ability to easily transform buttons into links and vice versa

Hi,When you have a lot of local variables in a action it's sometimes hard to find the variable.The sort order is now the order of creating the variables.It would be better to sort them on name of on a manual sort.

Customers that use Outsystems on top of existing external database(-application)s have the need for customisation of the way they connect to these databases. I have seen changes on the database connection for: change of machine/database, change of schema, connecting with a user other than the default user and connecting with a proxy-connection. I have also seen implementations for other initialisation actions in the external database like actions for context-, audit- or debugging-information.Please don’t start any discussion on the need for these solutions. This is not a discussion but a fact for some customers.It would be nice if these customers have a proper way to implement their specific needs.The current implementation of set database connection (and sometimes even more initialisation-code) before every database-action in Service-actions, Soap- & Rest-api's, OnBeginWebRequest & Fetch data from other sources creates a lot of duplicate code.And any of these actions can easily be forgotten.These solutions are sensitive to errors.Since the introduction of mobile and reactive within Outsystems the need for a proper solution is getting more urgent.I would suggest a similar solution on the usage of database connections as is implemented on consuming Rest-api's: OnRequest- and OnResponse-actions.In the OnRequest the connection can be defined and any further initialisation actions like context-, audit- or debugging-information can be done if necessary. If needed, in the OnRepsonse code closing actions like clear the context and audit-/debugging information can be done.These actions must take place on every begin and end of the session to the defined database connection.I think the best place to define these actions is where the database connection is defined and maintained: ServiceCenter.The code to be executed can be written as a public action in a module.  The module.action to be executed can be selected when OnRequest and/or OnResponse on the database connection is switched on. There is no need to do any coding from within ServiceCenter; coding is done at the place coding is to be done in ServiceStudio.Setting the actions on the connection can never be forgotten.The code will only be created once and in one place.Best of all: it will work for traditional, reactive, and mobile and will make the move to reactive simpler.As a consultant I have been allocated to different companies and most of these companies use Outsystems on top of an external database. All these companies will benefit from this solution for the challenge they have in integrating the existing database(-application)s and the challenge of migrating to responsive.

This idea suggests adding a production-level safety guard that prevents critical operations such as delete, update, or bulk actions unless explicit approval conditions are met. In Production, sensitive actions would require admin approval, a justification message, or a time-bound authorization, ensuring that risky operations are intentional and traceable. This feature would greatly reduce accidental data loss and human errors while adding an extra governance layer for enterprise applications.

Organize the CSS inside the blocks and whenever you deploy it creates a single CSS file.That way we would be able to have a more organized code in the components part, and it would not generate several CSS files disturbing the performance.

Hello everybody,When you make a change, for example adding a comment or rearranging statements or actions (without making any changes to your program flow and semantics) then Outsystems always forces you to re-publish your application again.From a conceptual perspective, making the above changes is a separate process because it does not make any contributions to your programs functionalities.It would be very nice to see this in Outsystems. I think it will also save a lot of time for the developer (especially in larger projects).

Service Studio should never allow a user to connect to a PRODUCTION environment (as marked in Lifetime) without warnings. When opening Service Studio, it should never automatically re-connect to a PRODUCTION environment either.We've had too many issues where someone does a hotpatch to PROD, and then the next time they open Service Studio they are workin gin PROD but think they are in TEST.J.Ja

It is common to want to hide rows of a showrecord depending on some conditions. It is also common to want hide some table columns, based on some criteria.

Just like many other sotfware solutions in the market, it would be very helpful if one could customize the workspace, for example, moving the toolbox to the right side of the main area or the development tabs to the top, etc, or even add my own shortcuts to the toolbar, show my favourite or most used widgets in the toolbox, etc... Customization should be only the first step, it should also allow to create a new MainEditor for side by side comparison, create different workspaces for different purposes (debugging, screen development, data modeling, etc). For reference this is how Service Studio is presented today: Source: https://success.outsystems.com/documentation/11/getting_started/service_studio_overview/ And I believe it has barely changed since the first versions. Its time to give it some refresh.

Like we have statIndex property in client side, it would be great if we have the same on server side as well, so that we can fetch limit records wherever required. --Sandeep Kolli