This is a known issue and its fixed in SP1510 (VeSys 2.0 2014.1 SP1510) where it is currently available for download on SupportNet.
↧
This is a known issue and its fixed in SP1510 (VeSys 2.0 2014.1 SP1510) where it is currently available for download on SupportNet.