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.
Interesting Idea,
but what if you have some confidential data that developers shouldn't have access to, but still want to make other Entities "visible".
A flag per Entity could solve this, but the maintenance of it would probably be a lot of work especially considering it being changeable only by an admin, who usually has already a lot to do.
So, you'd probably want a per Application flag where you can say that the data off that whole Application is visible in Service Studio, while also keeping the per Entity flag to further specify if needed.
You’d lose some security especially when working with highly sensitive data, Banks and similar institutions will probably never allow this.
Seems like a lot, but as you said it would be very useful to solve errors and other Problems.
I agree, now we need to have a tool like SQL Sandbox to do updates on Prod.Where I work we have the policy to enable/disable the SQL Sandbox only for the period needed, to limit unwanted access to it.
@José Gonçalves @Markus Mayr @Daniël Kuhlmann
Our R&D team could not agree more, which is the reason why we developed and published Orbit Suite Data Manager Forge Component, free to use. See our must recent post and release information.
https://www.outsystems.com/forums/discussion/83021/new-orbit-suite-data-manager-v4-4-12-with-enhanced-functionality/
https://www.outsystems.com/forge/component-overview/13176/orbit-suite-data-manager
@Markus Mayr
See screen shot below of what we've implemented per you recommendation above, "but what if you have some confidential data that developers shouldn't have access "