Since xxx have started its move towards a closed ecosystem, version upon version they are becoming more avid for the metadata of their user base. Now, with OTRS 5 and its new 'Daemon', there are routines crafted for this metadata harvesting that an admin can't disable anymore via the web UI.
These settings are in Admin > SysConfig > Daemon > Daemon::SchedulerCronTaskManager. They are:
Code: Select all
Daemon::SchedulerCronTaskManager::Task###RegistrationUpdateSend
Daemon::SchedulerCronTaskManager::Task###SupportDataCollectAsynchronous
Daemon::SchedulerCronTaskManager::Task###OTRSBusinessEntitlementCheck
Daemon::SchedulerCronTaskManager::Task###OTRSBusinessAvailabilityCheck
To disable them, open Kernel/Config/Files/ZZZAuto.pm and add the lines bellow to the end:
Code: Select all
delete $Self->{'Daemon::SchedulerCronTaskManager::Task'}->{'RegistrationUpdateSend'};
delete $Self->{'Daemon::SchedulerCronTaskManager::Task'}->{'SupportDataCollectAsynchronous'};
delete $Self->{'Daemon::SchedulerCronTaskManager::Task'}->{'OTRSBusinessEntitlementCheck'};
delete $Self->{'Daemon::SchedulerCronTaskManager::Task'}->{'OTRSBusinessAvailabilityCheck'};
I'm most than sure that even this method is not going to work for a long time. xxx may well just remove a configuration option for that at all. Of course, you can remove the underlying routines if you know where to lock and how to code, but they are going to come back upon every upgrade. The average, not code savvy user will have no idea that this is even happening. I predict a much worst situation in the upcoming OTRS 6.
My advice to all of you: it's the time to design a plan to move away from xxx at all.
Mine is 'en route'. xxx doesn't deserve my commitment or respect anymore as a user and/or developer. I'm going to fulfill their wish and let them live only with the paying customers of their BusinessSolution. That's what you wanted xxx, isn't it?