Community forum

Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


dsvahn
2015-12-04T14:27:29Z
Feature:

Be able to disable "job start/stop notification popup" for all clients. Like in the settingstab.

Because when you have multiple jobs running at the same time it shows up on the entire screen and takes up some cpu-load (if you have several users online it gets even more affected)

So a server setting to disable this would be appreciated.
Sponsor
Forum information
Mariyan Ivanov
2017-07-14T11:41:46Z
If you're using WebClient it gets even worse - filling up the screen and consuming lots of server CPU for the IIS. You can turn them off but settings are not kept on log out.
Support
2017-07-19T08:10:19Z
You can disable it in Client settings of the Web Client or in Windows machine through VC Tray client in system tray->Settings.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Mariyan Ivanov
2017-07-24T11:14:55Z
Originally Posted by: Support 

You can disable it in Client settings of the Web Client or in Windows machine through VC Tray client in system tray->Settings.



It's a bit sad to see that you're not paying attention to what exactly your users are asking for...

Originally Posted by: dsvahn 

Feature:

Be able to disable "job start/stop notification popup" for all clients. Like in the settingstab.

Because when you have multiple jobs running at the same time it shows up on the entire screen and takes up some cpu-load (if you have several users online it gets even more affected)

So a server setting to disable this would be appreciated.



We're aware of clients settings, but it's not serving our needs. As having hundred or so jobs running is making the notification completely useless. Having dozens of users and making them do the same settings over and over again is making the client setting useless as well. On top of that the worst part of Web Client is that the settings are not persistent, so you're required to configure it every single time that you open the console.

I've noticed that this topic is marked as "Resolved". That's wrong and needs to be changed!
SafonovPA
2017-12-28T10:09:02Z
Completely agree - very important feature and it's should be implemented.
Have same problem with lots of web client users
Support
2017-12-28T13:02:31Z
The problem with this is that we try to offer as much customization as possible. Also, actual settings are done and stored in each Client. Because of this you need to change settings once for each user.

It is important to add that Job Started/Stopped events are default off for latest build.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top