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 <span> that gets added around items in ListRecords causes a lot of issues with jQuery and other things. For example, we tried using a div with display: table-cell and it did not work because of this. J.Ja

It would be helpful to be able to create multiple plans and schedule when they are being published or add them to a publishing queue.Our company has a large number of applications and we are running into the situation where we have so many applications its taking a long time to publish.  If we can split up the applications being published and schedule it to run in off-hours it would improve performance.Another case is we have multiple developers trying to publish to the same environment. Sometimes we forget to go back so the QA spends time waiting for all of the changes to be published for testing.

When dealing with mathematical calculations or complex queries it's easy to lose track of parentheses.Check the attached image for an example of highlighted parentheses on Notepad++.

When I try to use the built-in action ListAny in a client action that needs to be a function, I currently get the error message sayingOnly actions that are functions can be used in other functions.From the documentation I get it that you don't want to perform asynch or server calls within a client function, but surely ListAny (or any other 'harmless' action) should be allowed?Or, at the very least, please make a function version of the built-ins ListAny, ListIndexOf and ListAny available.

Dear all,The AD has a chart with the overall technical debt trend for all applications within Outsystems factory, however should be very interesting to have something similar for each application.Something like:Best regards,João Paulo Pires

A native service studio plugin for Figma that doesn't just "import" but "links" components. Changing a padding value or a colour token in Figma should trigger a " suggested update" in Service Studio, allowing for" live code sync "between the design tool and the low- code IDE.

Currently, if we define a Sorting by an attribute, that sorting becomes unresponsive after introducing a Group By in the aggregate, as the sorted attribute is no longer part of the aggregate output . This does not raise any errors or warnings in the TrueChange Tab or any signaling in the workspace. I find that this is an easily overlooked situation that can lead to unexpected behavior or inconsistent results. I suggest the implementation of a typical Outsystems background validation that triggers a warning (written on the TrueChange Tab and a visual cue on the aggregate) whenever the aggregate's sorting references attributes that are not part of the aggregate output after a Group By, ensuring consistency and preventing silent issues.

When we do a merge with two OML, would be useful to have a search box to filter whats been shows in Compare and Merge box.

Hi guys, we use something similar here, but we do it manually.We know that good architecture is very important in our projects. It is a wonder if we could see in our tree view the actions and other dependencies with the same color they were classified in the discovery tool.For instance: library modules can have the default icon green and core modules a default color orange.So, when you are in a green module and try to consume an action from the core module, you can see you are doing something wrong directly on your tree view and safe time to run the discovery and check this later.Even the developer who is not so expert in 4LC can help to keep the architecture in the right lines.