Hi OutSystems Team, It would be incredibly valuable to introduce a feature in Service Studio that allows developers to select and manage specific versions of producers when configuring dependencies. This enhancement would align with the familiar workflow of Visual Studio’s package manager, empowering teams with precise control over which producer versions their applications depend on. Key Benefits: Stability & Reliability: Locking dependencies to verified versions minimizes the risk of unexpected changes or regressions. Simplified Rollback: Facilitates quick reversion to previous versions if newer updates introduce issues. Improved Developer Experience: Mirrors established practices in other development environments, making dependency management more intuitive. Collaboration Support: Promotes consistency across teams by ensuring uniform dependency versions, reducing integration conflicts. Please find below a mockup illustrating the proposed implementation.

It would be interesting to have a Null() function that replaces NullIdentifier(), NullDate(), and NullTextIdentifier() in OutSystems, like traditional programming.

 As a developer, I want to assign set 3 values to a single Site Property for all environments. This will dramatically speed up a deployment, where you won't browse several modules and change Site Properties depended on Environment. It is common practice when we set a Site Property value to production value by default, and change it manually in Dev and Test. In this case we kind of avoid a "human error" if we forget it during deployment. But sometimes we have several such properties, e.g. SomeDomainUrl , which should be different for each environment. I would suggest to inherit the practice we use in not low code: we might have several configuration files for each environment, e.g.: appsettings.json appsettings.development.json appsettings.test.json That means during a deployment build process the compiler will choose corresponding settings. How I see it: When you add a new Site Property, you can add (+) two more for tst and prod . If a developer does not add it, they are the same by default. Like that: Site Property : fromEmailAddress Value : "noreply-dev@mydomain.com" (+) tst Value : "noreply-tst@mydomain.com" (+) prod Value : "noreply@mydomain.com"

Hi,Is there any way Outsystems can add the email feature in Reactive Web without the use of the current workaround by using the action made from a  traditional web appThanks and regardsRaphael Laurence Reyno

Right now, ideas are scored like this: It feels like only quantity is valued, instead of quality. In my opinion, a better system would be to award points not for creating an idea (which promotes "idea spamming") but for the thumbs up the idea gets. There could also be an extra point award if the idea is implemented.

The ability to assign customer icons to folders:

I would love it if I could open the widget tree in a new window similar to how you can with the aggregates. Here is the icon that will open the aggregate in a new window:

I would like to have a search function in the stylesheet editor, so I do not have to copy the entire style to Microsoft Word before I can do a search.

When recovering deleted code or working with another person in the same app, during merge and publish it would be very helpful to have an option to 'Select All' for the versions we want, instead of selecting them one by one.

Creation of a widget to be used on the screen's actions that allow a simple and much faster validation of a form. Why?The time that nowadays we take to perform all fields validation in a form is high. Additionally, in a typical "Save" action, it gets very confused when we mix the "twenty" validations of dates, mandatory texts and business logic, with the save action indeed. It is not visually pleasing to read the action. How?Create a widget that visually looks like the form of properties of a entity. In that form, the user can add the fields that need validation, including also the expression that it is used to validate and the error message to show for each field. The widget can return a boolean called "Success" so that the user can continue to work in the "Save" action.