I would find it very handy to be able to duplicate any action within Service Studio instead of using 'Copy' which would populate the clipboard, while duplicate would preserve the value in the clipboard.

Right now, you must put the name of a role/screen hard-coded in a static entity. Once the name changes, you'll lose this link, and I suggest too implement some Role Identifier, which you can use in a static, We use this to filter parts of data for users with a specific role. for example, a dynamic menu, which is role-based. this contains the RoleName and Screen URL hard coded.

It already happened to me a couple of times - since I have the habit of setting the assign labels, sometimes I forget the assign itself. An empty assign has no logic at all, and therefore should display a True-Change warning to developers.

I think it would be nice when debugging an application to have a way of copying the runtime values to the query input parameters (test fields). This is very boring and time consuming for advance query with many input parameters for example. On top of that it would be nice to have a way to save these test values, and of course share them along with all development team. Check screen shot below.

The  Community Leaderboard page would be a great place to convert into a Community Dashboard and extend it with more community statistics like:Top Solution Contributors of the month + of all timeTop Forge Contributors of the month + of all timeTop Cheerful (likes given) Community Members of the month + of all timeTop Celebrated (likes received) Community Members of the month + of all timeAnd more...Let give this amazing OutSystems Community its own Wall of Fame!More discussion going on here: https://www.outsystems.com/forums/discussion/64456/community-recognition-top-solution-contributors/

Add a warning on Service Studio if a non-public Structure is not in use.This can help developers to identify non necessary data on service studio and make the code more clean.

It would be very useful if is possible to configure an integration between Service Studio and AI Mentor Studio. In the initial Service Studio tab, where the applications we have access are listed, have a section with a resume of AI Mentor Studio status. Also generate a notification if there's a significant increase of technical debt or if a critical alert like cycling references for example was just detected. I believe this integration would increase the visibility of AI Mentor Studio and it might improve how frequently the developers will check it.

Hi.At all time that update this plugin we've to implement it (again), because our solutions allow to configure quality and resolution of picture taked.Then, can be it implemented at "root" (native) component as well.Adding input arguments for TakePictureJS client action: Quality, TargetWidth, TargetHeight. All is Integer and optional (Mandatory: No) with your default values (originally... quality is 60, targetWidth is 600 and targetHeidht is 600).Add in TakePictureJS step the same arguments, but all "Mandatory: Yes", and use the input parameter correlate.At JS script (of same node) change fixed values to node input arguments.Image of an our solution after this plugin update:Our implementation:

I’m having some color blindness problems especially green/blue esc..During my exam there where multiple question regarding entities and structures. I knew the answer but I couldnt make the difference between green and blue since the screenshots where awfull quality...This is an issue which should be fixed as soon as possible..

Add a warning on ServiceStudio when you have situations like these:Because when your try to access the webscreen as expected: https://<ServerName>/<eSpaceName>/WebScreen1.aspxYou get this message on ServiceCenter: The file '/<eSpaceName>WebScreen1.aspx' does not exist.Sometimes, it's not easy to understand that ,by some reason, you have 2 WebScreens with the same name (specially on big and complex Espaces) on different WebFlows.Credits for this idea also to Edgar Ramos and Vítor Rosário that I found "digging" a bug that was found on a eSpace related to this problem