asked on May 19, 2017
One of our users received this error when refreshing the page in WebAccess. We are using the 9.2.0 version of WebAccess and we are on Laserfiche Rio. Is there a hotfix for this issue?
0
0