Background & Current Behavior On OutSystems 11, we were able to query an aggregate view of Users and their Roles and/or Groups (both directly assigned roles and those inherited via group membership) in a single transaction. In ODC, many of the system entities are obsolete including Role. To replicate some of our page, we must now use the newly introduced User Access Management APIs. Get /users had been promising. It can return the list of users' based on the parameters provided. It could have been the best alternative if when passing "assetKey" (applications id), it can return the users with the roles for that application. However, while it does return the users with directly assigned end-user roles, it omitted users where their end-user roles were only inherited from a group. To work around this limitation, we must now: Call Get User Groups for each user For each group, call Get Group Roles Merge and dedupe results in-memory This multi‐step approach leads to an exponential number of calls when you have many users and groups, causing unacceptable latency and resource consumption. Why This Matters Performance Degradation N users × O groups per user + P roles per group Dramatic increase in response times and network traffic Increased Complexity & Maintenance Custom merging logic Higher risk of bugs, especially around pagination, retries, and deduplication Business Impact Current workaround severely degrades performance Enhancement & Expected Behavior Extend the Get /users endpoint so it returns each user’s full set of roles, direct and inherited in one call. We can also add backward compatibility by adding new parameter such as "includeInherited" to identify whether to continues to return only direct assigned roles.

When I'm calling with Outsystems support I always hear the same music Although the piano concert when i'm on hold is OK, it can use some variation.Perhaps cello or violins for a change?

CSS preprocessors have had nesting support for a long time, and it is now natively supported in CSS as well. Furthermore, many browsers already provide support for CSS nesting already: https://caniuse.com/css-nesting CSS nesting is a valuable tool, which has many advantages, including enhanced code readability and organization, which ultimately contribute to the improved maintainability and efficiency of the CSS stylesheets. Therefore, adding this functionality to OutSystems would be beneficial.

It would be helpful to be able to import/export OML data about a module to a structured plain text file. This would allow developers to use git for storing code changes. Using git could solve branching/merging and code review concerns for changes to modules in the platform without having to build those features in Service Studio or other management tools. Features that would be helpful related to this Export an OML to structured plain text (xml, json, yaml, other). Import from plain text into service studio. Deploy using this format (ties into using third party CICD to deploy to various environments. Ideally, branching/merging, code reviews, unit testing would be more fully implemented in OutSystems but this feature would allow a "quick win" for teams trying to achieve this functionality.

Ability to split an eSpace by choosing the objects you wish to carry to a new eSpace. The previous eSpace will automatically consume references from moved objects. Entities will keep their data.

When I copy an input from one webblock or screen to another webblock or screen there is an error because the variable linked to the input does not exist.Now I can choose to create the local variable with the option"(New Local Variable)"The variable will have the name Var1 (Unless there is already a Var1 of course :) )Why not give the name from the Input variable property, so I the example above the name Locale?Just like when you copy a button and the action is not there.Now  create the action with the option "(New Screen Action)" The screen action is now created with the Name "PerformSearch" and not with the name "Action1".

get a data from Ai as an Realtime which we can get the data as dynamically for an user

There are times when we need to go through this tedious code debugging procedure to fight those pesky bugs that are tormenting our precious logic. We need to delve deep into the data lying under those nested variables, containing unfathomable variable-level listings, one over the other. I hereby request the ability to download (or at least copy to the clipboard, depending on a predetermined textual size) the full JSON content of the debugging area variables , so that we, developers, can fulfil our task better than our ancestors did.

Sometimes, when we’re about to post a question, Neo could quickly suggest similar discussions or relevant Forge components. That way, we can check if someone has already solved a similar problem before creating a new post. It’ll help reduce duplicate questions and make it easier for developers to find the right answers faster.

In ODC at the moment we don't have the ability to define an identity provider by application . I have a real cenario that i want to have applications that use Azure AD authetication and other apps for the same client want yo use the Outsystems Buil in provider so my idea is that expand the option that exists by environment to be by application . Regards