I agree this is a good idea.
Justin's comment about the warnings (perhaps a confirmation dialog) will also definitely help.
I have disabled Service Studio automatically connecting to the last used environment, as this has caused some issues. Perhaps a dialog message informing you that you are not connected to a development environment will also be helpful.
It would be nice that Service Studio could identify a login in a Production Environment and change it's color / add an Production icon warning.
There is an Idea for this already
For now I agree :D
It would be totally awesome if this colorizing also includes the "recent list"
Too often i kinda forget to look at the environment behind the modules
I really miss it. It's a great idea and easy to implement, no impact anywhere.
I think it would be usefull to change Service Studio Theme (colour, appearance) so we could set different colours for instance for different environments (Dev, Staging, QA...).
There is already an idea for this. https://www.outsystems.com/ideas/2353/different-colors-service-studio-by-environment?IsFromAdvancedSearch=True
March 2016?! In my opinion this is one important thing to develop. :)
Hi community,
Like other software, where it is possible to define the color for each environment (ex: red for production, yellow for quality, etc), it would be very useful if service studio had the same behavior.
Sometimes, and i'm not the only one, I'm working on the wrong environment and i don’t realize it, until later :(
Thank you.
Would be very helpfull!
Happened to me so many times. Any evident visual clue would be helpful.
I have had the same problem too multiple times! Great idea!
Would be great, for service center we use the Google extension Tampermonkey to give the headers of each environment different colours. Works like a charm.
You’ve got my vote Gonçalo!
Good idea. Always happen to me as well (wrong environment).
Why would a color be an advantage over the already noticeable "environment name" in the 2nd tab?
and when in production-mode you will get a dialog to confirm if you are sure?
As a developer and when doing app maintenance, I´m sure this happened to some of you too:
We are developing some new code on a environment, which we were supposed to publish in DEV and then publish it to Quality/Tests (QA) and then to PRD (Production) through Lifetime, but instead without looking at the first tab on Studio we wrongly publish it to one of the other environments like QA.
So to avoid this mistake I would like to suggest OS to implement a different color tab, the first tab on the studio after you enter the environment, for each one of them, like per example:
DEV : Green, QA: Yellow, PRD: Red.
Hello guys! My idea is to have something, like a mini banner or look like, that would be visible if we are connected to a PRD environment. This would be helpful if, by mistake, anyone goes into PRD and publishes any undesired code.
Idea aligned with the one below:
https://www.outsystems.com/ideas/10518/configure-service-center-header-color
I'd you have this "goes into PRD and publishes any undesired code"
There is definitely other things to worry about. Why is there undesired code in prod? And why would you have someone in your team that is allowed to publish that in prod?
Hi,
I think that can be a good thing if, when we open Service Studio in Production environments, something really visible and a warning appears. Something like a yellow/orange/red border in canvas or in other place (and a warning) so we can distinguish that we are seeing the production environment.
Best regards,
Ricardo Pereira
It would be very nice to be able to select colours per environment, which will be set either to the whole theme colour in Service Studio or just the header menu bar and also to the menu header in Service Center.
In this way when you for instance left one Service Studio instance open and change between environments, you are less prone to make mistakes to publish in the wrong environment. Of course you have the little text right now in the footerbar and in the headerbar, but colours will work better for me when the impact on a wrong publish can be big.
I think based on another idea ( inspiration ) more focussed on servicecenter where service studio is more important to me , this will benefit many. Hope for an implementation soon as possible.
Please vote up if you agree. Thank you
For Service Center there is already an idea, for service Studio also, I will merge your idea with the existing idea on Service Studio,
I suggest differentiating the non-production environment from the dev environment by assigning it a distinct color. There have been instances where I unknowingly performed tasks in the QA environment, mistaking it for the dev environment. By introducing a unique theme or color for the QA environment, it would be much clearer to identify which environment I am currently working in. Additionally, it would be beneficial to implement a warning/alert system when publishing changes to the QA environment, serving as a proactive reminder to ensure the intended environment is selected before publishing. n the QA environment
It would be nice if people first search ideas and check if the idea exists, I have merged this idea so many times with the origin all posted version that dates back to 2016. Will have to merge yours now also.