1.4.1(Jul 2021)

NXPSR-11213 Nexaweb launcher should run with bundled jre if JRE requirement is not met.

Nexaweb launcher with getdown 1.8.6 requires JVM 7 or higher. If JRE is not found on the client machine or the system JRE version < 1.7, Launcher will run with the jre bundled with the launcher.

A log file will be added to user's home directory/.nexaweb/logs/launcher to show the jre used.

NXPSR-11214 Automatically open file with nexaweb extension on download in Edge and Chrome.

Nexaweb launcher will provide an option to set AutoOpenFileTypes browser policy in the registry during installation. Set this browser policy to automatically open file with nexaweb extension on download in Edge and Chrome. Registry values will be removed during uninstallation.

During installation, you have option to the set the browser policy for the current user or all users.

Open

Registry value when Chrome is selected for current user
[HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome\AutoOpenFileTypes]
"1"="nexaweb"

Registry value when Edge is selected for current user
[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge\AutoOpenFileTypes]
"1"="nexaweb"

Registry value when Chrome is selected for all users
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\AutoOpenFileTypes]
"1"="nexaweb"

Registry value when Edge is selected for all users
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\AutoOpenFileTypes]
"1"="nexaweb"

More details at
Microsoft Edge Policies https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#autoopenfiletypes

Chrome Enterprise policy list https://chromeenterprise.google/policies/#AutoOpenFileTypes

Defects