Issue fixed in release 1.4.1.3

The following issue is addressed in this release:

Parent topic: Changes in previous releases