The 'RequireScript' System action adds a Javascript to the html header as a synchronous ['sync'] script by default. Here is an example of a require script added to a header:Here are some examples of scripts added by OutSystems UI (we can see that they are set asynchronously ['async']):This configuration is important because a sync script that has an error could stop the page from loading and trigger an error screen.So the idea is to add more inputs to the 'Require Script' System action to allow at least to set the async configuration.We could keep the default as sync but also allow the user to set it async. As a plus, we could also have the remaining configurations available, as used by OutSystems (type & chartset).This would give more control when using require script and avoid potential page crashes. I think everyone could benefit from this upgrade.

 Problem Description When working on complex action flows in Service Studio, it’s often hard to visually identify the main path, the sequence that runs when everything goes right and no exceptions are thrown. Once an action starts to grow with multiple if nodes, exception handlers, and different branches, all the lines look the same. This makes it difficult to quickly understand: Which path is actually executed most of the time Where to safely add new logic Where performance-heavy steps should go How the flow is intended to run under normal conditions This becomes even more confusing when maintaining someone else’s work or revisiting a module after a long time. Idea / Proposed Solution It would be extremely helpful if Service Studio allowed us to highlight or mark the main execution path inside an action flow. Some possibilities: Manually select certain steps and mark them as the “main flow,” so they get a subtle color or visual emphasis Dim non-main branches for easier reading Add a toggle to show/hide highlighted paths Or even allow Studio to auto-suggest a main path based on the straight-through execution sequence Even a small visual cue would make a big difference when reading or designing large flows. I believe this small enhancement would significantly improve the experience of working with complex action flows, especially in enterprise-scale applications.

Every timer has a WakeTimer action that is only accessible within the module of the timer. It would be way more handier if that WakeTimer action would be a public action so that we don't have to create wrappers for it anymore.

Hello,In version 11.53.28 there is a new export image function for UI, logic and processes. This is a great future, however I feel like the position of the 'export x to image' button for actions should be changed. I believe that many developers are used to quickly adding input-parameters, which now leads to saving images. My suggestion is to move the export function down in the list, below the variables.

I propose adding an optional parameter to the Round() and FormatDecimal() functions to select the rounding strategy (e.g., Round Half Up, Round Down, Ceil, Floor ). Currently, OutSystems client-side uses Decimal.js with a hardcoded default of ROUND_HALF_EVEN . While standard, industries like Fintech and Brokerage often require different methods (like ROUND_HALF_UP for taxes or ROUND_DOWN for fractional shares). Update the built-in functions to support an optional rounding parameter: FormatDecimal(Decimal, Integer, Text, Text, [RoundingMode] )

Cache is great in some situations, but it could be used in many more if we could invalidate specific records of the cache, instead of the whole tenant. A simple example: I have an action that returns a user's teams. I'm always calling this action and the teams change very seldom, so caching this action greatly improves performance. I know that the cache for this action is only invalid if someone changes the user's teams, so, if I could invalidate the cache when the user's team are saved I could potentialy run that code only once per user, after an update. At the moment I don't dare to cache that information because it's not acceptable for a user's teams not to change after a save and invalidating the whole tenant's cache will cause scalability problems if the application gets enough users for team changes to be relatively frequent.

Currently, SQL comments have no difference color than the normal SQL. I would like to have a different color for comments in the Advanced SQL editor so they will be more visible. OutSystems: Notepad++:

Currently, the Forge component pages have tabs like Overview, Reviews, Versions, Documentation, and Support. Adding an “Improvements” tab would allow developers to share enhancement ideas, suggestions, and feature requests directly with the component creators. This will help Forge makers understand what the community needs most, plan better updates, and evolve their components into more complete, community-driven solutions

Some Indicators still need enhancement as they still generate a lot of False Positives. So, it's an annoying task having to go over all of them and marking as False Positive or even Already Fixed or Won't Fix.So, if I could just mark the items I want to change and select the new Finding type at once, it would be very helpful. Most of the times the reason is the same anyway for several items.

While consuming any rest API with null value fields, platform discard those fields from the output of that API. So instead of discarding those we can consume those as text and show message that your null values fields are created as text. Thanks.