Just a followup on this. I was able to escalate this problem, and have heard that this issue is fixed in the View 6.0 release which is due out in Q1/Q2 of 2014.
↧
Just a followup on this. I was able to escalate this problem, and have heard that this issue is fixed in the View 6.0 release which is due out in Q1/Q2 of 2014.