Seriously!! How was that update even allowed to be slipped out under the radar via Platform (Release Announcements), under the title “Removal of obsolete files from BES Support”
That topic should have been worded “BESClient/action script functionality change - CAN BREAK TASKS”
If you going make a change that has the potential to break custom/customer content (when it uses the BES Support Tools) please can you make sure its worded correctly so that it does not get overlooked and gives the customer a chance to update any content that might use it.
This sort of change is normally only expected for dot version release update, certainly not expected as part of a site update!
This activity resulted in production tasks failing for a critical baseline!