>Partially good news. If true then it also implies that there is no workaround available for the current release......

I still haven't had the change to test the solution recommended which is listed at the bottom of the page in the Comments section. Maybe that is a workaround.