This issue was fixed with SDSCM00047357. This is the reason the bug no longer appears after the 6.1.4 release.
↧
This issue was fixed with SDSCM00047357. This is the reason the bug no longer appears after the 6.1.4 release.