Hi Sam,

I don't know if you're aware, but in the Preferences window, you can disable the option to connect to the last environment at startup, which makes you choose an environment to connect to every time you open Service Studio.

Doesn't that fit what you need?

Kind regards.

Hi Ricardo,

Thanks for the suggestion. I am aware of that option indeed. The thing is that I do like the feature of Service Studio connecting automatically to an environment.

What I am struggling with is when I connected to an environment different than DEV once for whatever reason, Service Studio picks that up the next time (sometimes the next day). The specific environment you are connected to does not always stand out very clearly. Because of that, it happens that I end up doing developments in the TST environment whereas I actually wanted to do those developments in DEV, and I am sure I am not the only one. 

To fix this, I am suggesting to have the option to configure Service Studio not connecting to certain environments (e.g. the TST environment) automatically. Or to allow us to choose one specific environment to connect to automatically. The first might be more suitable if you tend to switch between environments for different companies. The second would be useful for developers working in one environment for one company.

The main problem in any case is that it is not always as clear which environment is opened. My suggestion tend to fix that issue, but I am open to other suggestions.

Ok, Sam, I understand your point. 

As a preference, I don't mind having to always choose an environment every time I open Service Studio, even if I'm working in one specific environment for many days in a row. As a matter of fact, avoiding making changes in a non-DEV environment by mistake is exactly the reason why I have that option disabled.

Let's see what the community thinks about that.

You are right, that Idea is similar enough to warrant a merge.