Then it has been fixed.
This may be considered a bug in 5.0 documentation. We usually fix bugs in subsequent releases (very rarely in update releases, only for critical issues)
Regards
Then it has been fixed.
This may be considered a bug in 5.0 documentation. We usually fix bugs in subsequent releases (very rarely in update releases, only for critical issues)
Regards