Would be nice to have an option copy a single value from previewed data.PS: Although, I noticed that Ctrl+C copies all the values from the selected column.

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!

This idea is a suggestion for OutSystems UI but also for an improvement on Service Studio. Add support for a dark theme in OutSystemsUI. This version of the theme would be similar to the viewport simulation approach, with classes in the body tag displaying which type of device the user has. The new classes would be "dark" and "light". Add a ThemeSwitcher Pattern to OutSystemsUI. This pattern would be responsible for managing the theme, keeping the user's preference in local storage/client variables. Add a dark theme simulation in Service Studio Again, similar to the viewport simulation that lets the developer see the page in 3 different screen sizes, there would be an option to see the page in dark or light mode. The dark theme is a great modern addition to any app, because it lets users choose which theme is best for their condition. Having it integrated both in OutSystemsUI and ServiceCenter would allow OutSystems developers to have an implementation of this feature that is both universal and officially suported.

The HTML Element widget is, from what I can tell, limited to a set of tags that OutSystems defined. As new HTML tags are created, and with the surge of technologies like Web Components (that use custom HTML tags), this becomes a limitation and we have to implement workarounds to make a simple thing work. Can this rule be relaxed or even completely removed?

Web developing means having to working in many aplications including many browsers that makes us lose focus on service studio Playing sound on done or erro during run or publish could help keeping notion on the state of the application while on other windows

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.

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.

I would like Service Studio to automatically add code to the assignment after I have named it in this specific way:[NameOfAnInernalVariable]++Obviously, the automatically added code should be:NameOfAnInernalVariable = NameOfAnInernalVariable + 1Perhaps it would also make sense to do this for types other than int - example:NameOfAnInernalVariable  = AddDays(NameOfAnInernalVariable, 1)Although technically simple, this behaviour would save me a lot of time when developing.

We currently have the capability to create structures using a JSON editor, but it lacks the functionality to edit or update them. I propose implementing a feature that allows users to edit and update the structure directly within the JSON editor.

SyntaxEditor Code Snippet$('input[id*=Image1]').change(function(){    readURL(this); }); }); function readURL(input) {         debugger;         var validExtensions = ['jpg','png','jpeg']; //array of valid extensions         var fileName = input.files[0].name;         var fileNameExt = fileName.substr(fileName.lastIndexOf('.') + 1);         if ($.inArray(fileNameExt, validExtensions) == -1) {             input.type = ''             input.type = 'file'             alert("Only these file types are accepted : "+validExtensions.join(', '));         }         else         {         if (input.files && input.files[0]) {             var filerdr = new FileReader();             filerdr.onload = function (e) {                 $('.ImgReviewClass').attr('src', e.target.result);             }             filerdr.readAsDataURL(input.files[0]);         }         }     }