NXPSR-11213 Nexaweb launcher should run with bundled jre if JRE requirement is not met.
Nexaweb launcher with getdown 1.8 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 set AutoOpenFileTypes policy in the registry during installation to automatically open file with nexaweb extension on download in Edge and Chrome. Registry value will be removed during uninstallation.
Registry value for Chrome
[HKEY_CURRENT_USER\SOFTWARE\Policies\Google\Chrome\AutoOpenFileTypes]
"1"="nexaweb"
Registry value for Edge
[HKEY_CURRENT_USER\SOFTWARE\Policies\Microsoft\Edge\AutoOpenFileTypes]
"1"="nexaweb"
More details at
Microsoft Edge Policieshttps://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#autoopenfiletypes
Chrome Enterprise policy list https://chromeenterprise.google/policies/#AutoOpenFileTypes
Defects
NXPSR-11215 | Nexaweb launcher does not work with Custom JVM Custom JVM installation and upgrade in the document is not working |