In Client Web applications, when performing custom validation on a Form, developers cannot directly set Form.Valid manually. This creates a limitation in advanced scenarios where validation conditions can't be fully handled by the built-in validation framework. For example, if a developer wants to invalidate the form based on a business rule such as: Number < 100000 there’s no way to directly set: Form.Valid = False Instead, developers are forced to: Create an extra local boolean variable to store the validation result Reuse the same condition again when checking whether to proceed or show an error This results in code duplication, reduced maintainability, and extra steps for logic that should be simple. A better approach would be: Allow manual control of Form.Valid — enable developers to set it to True or False inside client logic flows or expressions Or introduce a built-in method like Form.Invalidate() that can be triggered conditionally, without relying solely on form input widgets This would: Simplify complex validation scenarios Reduce the need for extra variables and duplicated conditions Improve logic readability and maintainability Let developers manage validation state more directly

Hello everyone, I’d like to suggest implementing a mechanism for approving forum solutions. With more and more community members actively contributing and answering questions, it would be valuable to have a way for a champion, MVP, or staff member to officially approve a solution and/or provide authoritative feedback. This could include notes such as suggested improvements. I believe this would be especially helpful for newer or beginner members, who may not yet have the experience to evaluate multiple answers and might default to the first response, even if it’s not the most accurate or optimal one. Such a feature would help ensure higher-quality guidance across the forum and make it easier for users to identify reliable solutions. Additionally, there are many older topics that have received answers, but the topic creator never officially marked a solution or confirmed whether the answer worked. This often leads to members replying to old or inactive threads, which can unintentionally push newer and more relevant topics down the forum list. I’ve seen cases where newly created topics end up on the third page of the forum because multiple old threads were resurfaced. With an approval mechanism in place, moderators could review these older topics and officially approve a solution where appropriate.

Hello All,JavaScript has had ES6 and ES7 syntax since a couple of years. The new syntax provides some good features like lambda syntax, the 'let' keyword, the 'const' keyword, template literals etc.While some old browsers do not support all of the syntax, there are libraries like 'babel.js' ( https://babeljs.io/ ) which transform modern JS to ES5 (the usual JS syntax).It would be great if the OutSystems product allowed using modern JS directly in ServiceStudio.OutSystems can integrate the babel.js within the platform - so that it can convert any modern JS syntax to ES5 (older JS when required for old browsers, already most modern browsers do support ES6 , but not all..).Advantages:1. Developer productivity with modern JS will be very good. Many forge components rely on JS and JS libraries and having support for modern JS will be great.2. Modern JS is helpful for writing easier to read and maintainable JS code.3. On the mobile front in OutSystems - apache cordova for the mobile plugins is JS based - so supporting modern JS would be a win over there too.

Currently, OutSystems UI provides built-in Open and Close actions for individual Tooltip components. However, if we review the Tooltip API implementation, we can see that there is also a GetAllTooltips method available. https://github.com/OutSystems/outsystems-ui/blob/53a8f0e/src/scripts/OutSystems/OSUI/Patterns/TooltipAPI.ts#L2 If you want to show all the tooltips in the screen you need to rely on a iteration and trigger the open tooltip action. Add the GetAllTooltips and ShowAllTooltips to the list of OutsystemsUI Actions.

[Service Studio]If you are developing a Big Action full of Sub-Actions all with plenty of mandatory entry points, it would be useful to have a new Sub-Folder area where no Validations were made on the "Work in progress" Actions/Functions that way you could publish the eSpace until all the new actions could be used.That area would also include Finished and Validated Actions with no usage anywhere else within the eSpace

OutSystems Reactive Web Apps that allows developers to define a global Client Action "Global OnBeforeNavigate" (or Server Action) that executes before navigation to any screen. (In Reactive - At least On before request of server & Service action, allows to add custom logic validation, Authentication, etc) This acts as a centralized "middleware" or "router hook" similar to ASP.NET Core Middleware Currently, OutSystems developers must manually call shared actions in OnInitialize of each screen — which is error-prone, repetitive, and unscalable in large apps. Adding global lifecycle hooks brings enterprise-grade control and flexibility to navigation handling — making Reactive Web development cleaner and more maintainable.

The reactive web is taking its first steps, but right now it's not fully mature and doesn't have all the functionalities of the traditional web.It would be great to have a gap analysis document  which states what is now missing from Reactive compared with the Tradicional web. It would help to make the decision whenever a new application is going to be created. Should we go for Reactive or Tradicional?Example: Lifetime analytics not fully working in Reactive. Translations are not yet ready in Reactive. Etc.

For a DropdownSearch there are options for translating/changing NoResultText and SearchPrompt It would be good if the OptionalConfigs also have a configuration for clearButtonText

As a developer, I find myself constantly using properties of lists and data actions like `. Empty ` and `. IsDataFetched `. When assigning to a boolean variable, Service Studio could suggest this properties. See in the following example that I wanted the `Tickets.Empty` property, but it was not suggested.

Hi all,On Reactive web apps it's no longer possible to add variables on the screen title, it only allows text.Reactive:Web tradicional:I think it's good thing to have because if a customer has a lot of tabs open, he has to open each tab to find the "order" that he wants to see.Thanks!Miguel