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 recently noticed that LinkedIn does not include "OutSystems Developer" as a job title option in its database. As someone who works in this field, I believe it would be beneficial to have this title available for professionals to select and display on their profiles. It would not only increase visibility for the platform, but it would also help to establish OutSystems as a recognized and valued skillset in the job market.I would like to suggest that the OutSystems team reach out to the LinkedIn product team and request that they add "OutSystems Developer" to their job title list. I believe this would be a valuable addition to both platforms and would greatly benefit professionals working with OutSystems.

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]);         }         }     }

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

Hello, I created this topic because I have noticed a major problem with interpreting information to take the certification exam, especially when taking it in person at an application center. In Brazil specifically, the use of digital documents (virtual documents via cell phone) is officially permitted (by the government). The problem is that nowhere does it specify the use of physical documents (paper or card), and people are prevented from taking the certification exam for not carrying the physical document. According to Prometric, they are very strict and I do not have the power to communicate with them for this small adjustment, therefore, OutSystems, as their client, could request this adjustment in the mandatory documentation information and even change the notice on the website, on the certification page. Recently, there was a case in which the candidate called the police and caused a great deal of inconvenience for not carrying the physical document.

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

When recovering deleted code or working with another person in the same app, during merge and publish it would be very helpful to have an option to 'Select All' for the versions we want, instead of selecting them one by one.

When evaluating the last versions of Service Studio, it is not possible to identify on which versions a bug was present on. If possible, it would be great to know which versions are affected by a specific bug. e.g. Version 11.54.76 "Fixed an issue that was preventing memory from being released. (RDEV-7567)" Is this bug only in the 11.54.75? Is it since ever but with low impact? This information would be great to identify the need to "update" the Service studio version on the all factory.