Service Studio should never allow a user to connect to a PRODUCTION environment (as marked in Lifetime) without warnings. When opening Service Studio, it should never automatically re-connect to a PRODUCTION environment either.
We've had too many issues where someone does a hotpatch to PROD, and then the next time they open Service Studio they are workin gin PROD but think they are in TEST.
J.Ja
The idea is always you are connected in a production environment from Service Studio and try publish anything, Service Studio show a confirmation to continue. Maybe the idea could be a simple changing of the "1 - Click Publish" button to be more evident you are connected in production envrionment.
It is to avoid users connected in production environment by mistake publishing things in this environment.
Service Studio stores the last host you had connected and sometime the user could connect in production by mistake thinking it be the development environment.
Well, tbh, normal users should not be allowed to publish directly on production!
Yes
I agree, but the platform allows it. In some emergency or just to publish a simple change somebody prefer do it using Studio instead of publish the eSpace from Service Center or Lifetime. Sometime you can't publish all the eSpace, need only solve a problem.
Similar in spirit to:
http://www.outsystems.com/ideas/123/different-service-center-colors-for-different-environments
Virtually identical to:
http://www.outsystems.com/ideas/2223/prevent-or-warn-user-if-1-click-publish-initiated-from-production-environment
and:
http://www.outsystems.com/ideas/1709/warn-when-connecting-to-a-production-environment
And yes, J. is right about the permissions... but as the "one person with permission to publish directly to PROD" I've messed this up myself MORE THAN ONCE!
The problem is that Studio re-connects to the last environment you connected to, so after a hot patch to PROD, the next time you open Studio it connets to PROD, you forget that you are in PROD and not DEV, and start working... oops...
In earlier version this wasn't possible if the 'production mode' was set in service center, so you first had to set the server mode to 'development' before able to publish to the server. Service Studio also didn't allowed the publish when the server was on 'production mode'.somewhere this option was removed....
wait for it.... :)
Hey Justin,
From now on, when you publish a module into a production environment you will get a confirmation message popup to make sure you know the impact your operation might have:
As usual, you find your contribution in the latest Service Studio version's release notes:
https://success.outsystems.com/Support/Release_Notes/10/Development_Environment/Development_Environment_10.0.906.0