Hi, As a secutiry increase to our applications it would be nice if we could assign roles (former permission areas) to screen actions and user actions. This way users that didn't have permission to run them, would never be able to use firebug and other tools in order to activate buttons that trigger the action and we wouldn't need to always be "asking" in every action, if the user has permission to run it. Another benefit would be, by unchecking the anonymous role, we could also automatically know if a session timed out, without having to "ask" that also in every action. What do you guys think?

Hi all,I would like to request an addition to the configuration tool/ server.hsconf.More and more we run into customers hosting there OutSystem platform in Azure resources segmented in a dev/tst, acc and prod subscriptions, resource groups, ect…. Each segment with its own servers, scale sets and a SQL managed instances to provide database needs. With an Azure Active Directory tenant to provide users authentication for the platform, and no “real” AD in sight.On the application side this handled beautifully by OutSystems. But in the situation above we are currently forced to use SQL authentication because there is no option to manage user authentication for the back end via ADD.Can you please add the option to use ADD users, service principals and/or managed identities as an authentication mechanism in the connection between the platform and an ASMI?! This for manageability and security benefits.Thanks in advance!

"setCurrentLocal" is an action that allows us to choose the language of the application. For example, if I want the application's local language to be Portuguese, I would put "pt-PT" in the input of this action. Once we choose the language, it would be interesting if the built-in functions of OutSystems returned the output in the chosen local language, in this case, Portuguese. For example, using the formatDateTime(date, "ddMMMMyyyy") function would return "01Julho2023" instead of "01July2023" if the application's local language is set to Portuguese. This way, we wouldn't have to translate the function's output.

OS11 can connect with SAP using SAP Group Logon, but that is not available on ODC. On ODC only SAP Direct Connection is available. It's important because many clients only have SAP Group Logon active in Production environments for load balancing.

Having an option on the screen or in the button parameters to prevent the user from double clicking on any element twice or others when the server is processing.Per example if the server is slow the action logic may still be processing and some users have the tendency to double click buttons (like Create/Save) repeatedly, duplicating records (per example).You can avoid this by using the Button Loading widget on Mobile and Reactive Apps, but there is no option for the whole screen. On Traditional Web you have to implement your own logic or use a Forge Component (Page Loader) or ( Button Locker), per example.

Like ForumThread: https://www.outsystems.com/forums/discussion/62101/how-to-remove-a-native-platform-configuration-for-a-mobile-app/ we can add config and generate an app. But are unable to disable/delete that config. Add option Disable Native Platform, Like PWA Config has. when not used, still all versions are going through the MABS. Reasons 1. We tested an app for perfomance in NativeAndroid vs the PWA version. The PWA versions was good enough so we want to go forward only with the PWA. but are now unable to remove that config. 2. We had multiple mobile native apps that only used components that are now also supported within PWA. Therefor we would like to clean up the builds and generations of APK if we are not needing them. 3. strange to add config and we are unable to deleten or make disable it.

It would be really useful to keep the filters selected once we return from the Detail of the Error. It would save us some time.

Implement a new "Download Module" link that automatically downloads the lastest version of that Module:

Hi,Would be great for troubleshooting if the runtime values used in query parameters were also logged in the error log text. The tenant Id would also be a good idea to support multi-tenant scenarios.Of course this would only be applicable to query related errors and they could be shown in the log in a very simple manner like:"TenantId = 1Param1 = 123Param2 = "Text"Error in advanced query  (...)"This would allow much faster debug in Service Studio.Cheers,Hermínio

When we have the need to invoke the same entity twice in advanced queries we have the absolute need to put an alias in one of them, to distinguish them. The thing is that service studio puts a warning to it if you use Alias.* ... Perhaps one could assign an alias to the output structure?