Summary

Release Announcement

This release of eRAD RIS 4.2023.019resolves an Installer issue with the RIS Client upgrade.

Resolved Issues

This release resolves the following issues:

Category	Redmine #	Subject
Thick Client GUI	33824	Resolved Thick Client GUI issue where client upgrades failed due to permissions issues (with Known Limitation). Specifically, this affects users of PECOS functionality, which employs a new Microsoft Webview2 control that requires a cache folder within C:\ProgramData\eRAD\eRAD RIS\. Standard users do not have the increased permissions required to access this folder during upgrade. Workaround: There is no reliable workaround for this presently, as the only solutions are to either perform a core reinstall with a privileged account when the error occurs, or have an administrator remove the ris.exe.WebView2 from within the C:\ProgramData\eRAD\eRAD RIS\ folder.

Category

Redmine #

Subject

Thick Client GUI

33824

Resolved Thick Client GUI issue where client upgrades failed due to permissions issues (with Known Limitation).

Specifically, this affects users of PECOS functionality, which employs a new Microsoft Webview2 control that requires a cache folder within C:\ProgramData\eRAD\eRAD RIS\. Standard users do not have the increased permissions required to access this folder during upgrade.

Workaround: There is no reliable workaround for this presently, as the only solutions are to either perform a core reinstall with a privileged account when the error occurs, or have an administrator remove the ris.exe.WebView2 from within the C:\ProgramData\eRAD\eRAD RIS\ folder.

New Known Limitations

While no new known limitations were identified with this release, the following expected behaviors were noted:

· Expected behavior by design (from #33824)

o Issue: Deploying the #33824 fix will only resolve issues upgrading the RIS Thick Client GUI in future releases.

o Impact: Affected client installations will continue to fail until after this fix is deployed.

o Workaround: The current workaround of manually upgrading affected workstations (described above) is required for this release (but not future releases).