11-29-2013 04:51 AM - edited 03-20-2019 08:07 PM
This bug description seems to be out of date as it does not mention 6.1.5 code.
If I upgrade my customer to 6.1(5)SU3 is this bug fixed? I have searched the readme files for all 6.1.5 versions but can find no mention.
Thanks
12-02-2013 07:39 AM
This bug is resolved in 006.001(002.1000.013) which means it is fixed in 6.1(2) and later versions. Regards, Wes
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide
Log in to Community
