ECC Server Manager Design
Posted: September 22nd, 2022, 10:29 am
I recently had a call with someone on the ECC server manager. They were clicking stop and it showed as stopped, but the ECC connection was not brought down
I talked with Steve and realized the confusion. In order to stop the connection for a specific environment, you need to click disable:
The service managers job is to continuously start the ECC connection when it goes down, so to stop it is to turn off the auto run of it. like a batch job. but if an ECC connection is already running, stopping SM doesn't kill that connection.
This set up doesn't seem intuitive. I think it should mimics windows scheduled tasks where there is a disable and stop option for each environment.
Instead there is a stop button in SM which doesn't stop any of them, a disable option in each env that stops them. The stop is what disables them from coming back.
Is there a reason for it being the current way? If that makes sense in some context, I think better labeling or text should be given to help the user understand that without having to read some separate documentation
This set up doesn't seem intuitive. I think it should mimics windows scheduled tasks where there is a disable and stop option for each environment.
Instead there is a stop button in SM which doesn't stop any of them, a disable option in each env that stops them. The stop is what disables them from coming back.
Is there a reason for it being the current way? If that makes sense in some context, I think better labeling or text should be given to help the user understand that without having to read some separate documentation