Prod data is not always so confidential to developers that it really needs to be hidden in Service Studio. Having it available makes it much easier to solve problems in Prod.A flag to display or not could be available to admin.

In advanced queries, It would be useful to see all the attributes of the output structure or entity.I should be able click my output structures and see all the attributes of that structure or entityFurthermore, if the query output is an entity, clicking on a specific attribute should select that attribute in the query.

Add Social Buttons to share Ideas .Add some social button like Facebook , Linked in ,Twitter .These buttons fix near to comment and views in idea page when an idea creator want to share his/her ideas just one click is enough to share.

When we try to run an Advanced Query, in the test button, to see if the query is having the expected behavior, it happens that sometimes we have errors and the error message is never clear (eg: after ')').From what I suggest in continuation to my previous idea, of putting the numbering of the lines in the Adcanced Query, also indicate in this error message the line where we are failing. What do you think of this idea? It could help a lot.Nuno Miguel Verdasca

Not sure how recent this step is, but when opening an eSpace, I've noticed that my Service Studio hangs for 1-4 seconds in this step: It seems to me that "fetching possible entry modules for debugging" is only needed on the debug panel and can be done in the background without delaying the opening of the eSpace

Due the desired movement of Outsystems into the Enterprise IT world, from my experience, sooner or later, it will be needed a way to easily connect to MQ based ESB's or EAI. It should be a native feature of the Agile platform to have a way to subscribe to a message queue (MSMQ or JMS) and fire an Action or a BPT process whenever a message with certain characteristics arrives to that queue. It should be analyzed the fact that an ESB or EAI processes thousands of messages per second, so I believe that a tie to the RDBMS might not be a good technical solution. It should also be possible to write to queues (the idiom should be the same as Webservices). At least the standard: Point-to-Point, Publish/Subscribe and Broadcast message transmission/reception models should be supported.

 To use input mask in the platform it's necessary use third party components that are not supported by outsystems, and all forge's components that set input masks don't work in Android 4.0 or superior. Then, my idea is the platform natively offer support to input mask. Thanks

Hello community!I want to suggest a small functionality that, in my case and probably yours, will reduce some extra interactions with Service Studio.When I want to access the handler action of an event, I have to look for it in the screen actions. In case there are many screen actions, it will add some small extra time (but this is done multiple times).The suggestion I propose is to allow to open the handler action directly from the handler field. In the case of this screenshot, I want to open the DataField_OnChange_Validate.If you have another solution to make this interation more clean, be free to suggest it.Cheers,António Pereira

Hello, I think to have a option to disable the manual swipe on StackedCards would be a very usefull feature. Thanks, Paulo Torres

Hi,It is a great idea to provide severity of issues on the architecture dashboard - something like Sonar and checkmarx. So the teams can focus on Sever issues first (like Very high, high, medium, low). Something similar to Impact - but impact right now does not show a level of impact.Right now Architecture Dashboard provides everything according to category - but not according to severity.This similar kind of severity based analysis report is provided by paid subscriptions like OmNext, Boncode etc. however since we already have this similar report right out of the box in architecture Dashboard, then why not include it here.Thanks !Vikas