HCL Nomad Web 1.0.21 is now available. This release is focused entirely on bug fixes and stability improvements, with no new features introduced.
For panagenda customers, however, there is one particularly important fix: HCL has resolved an issue where the MarvelClient configuration database specified through NOM_MC_DB in notes.ini was not being utilized. This restores the expected behavior for environments using a custom MarvelClient configuration database.
What’s new in HCL Nomad Web 1.0.21
There are no new features in this release. HCL describes 1.0.21 simply as a bug fix release. The update addresses twelve issues across HCL Nomad for web browsers.
Important for panagenda MarvelClient customers
One of the fixes is particularly relevant for environments managed with panagenda MarvelClient:
NWASM-10172 | KB0131809
This issue was introduced with HCL Nomad Web 1.0.20. As described in our information about the previous release, Nomad Web 1.0.20 did not correctly honor the NOM_MC_DB setting. As a result, environments where MarvelClient used a configuration database with a non standard database name or path could experience problems because Nomad Web was unable to locate the configured MarvelClient database.
With version 1.0.21, this has been fixed.
This is particularly important in larger environments where the MarvelClient configuration database is intentionally located at a specific path or uses a customer specific database name. The database should not have to be renamed or moved simply to accommodate Nomad Web.
Administrators can use a Domino Desktop Policy to set the NOM_MC_DB value in notes.ini and point Nomad Web to the required MarvelClient configuration database. With the fix in 1.0.21, Nomad Web once again respects this setting as expected.
For customers affected by the issue in 1.0.20, upgrading to 1.0.21 therefore restores the intended configuration and removes the need for the temporary MC_DB workaround that was available for the previous release.
Other fixes in 1.0.21
In addition to the MarvelClient related fix, HCL Nomad Web 1.0.21 contains the following corrections:
| Issue | Details |
|---|---|
| NWASM-9895 | Unable to select multiple values in the Date/Time field under certain conditions |
| NWASM-9966 | IME input to a database field is not possible while the Search dialog is displayed |
| NWASM-9981 | Embedded Outline icon position “Middle-right” is not honored |
| NWASM-9991 | Print Preview dialog shows extra input fields and text and borders are not aligned correctly |
| NWASM-10054 | Crash while importing a large database via Open Application |
| NWASM-10130 | Legacy gray system style buttons are converted to outlined buttons |
| NWASM-10147 | “LookupHandle: handle out of range” in GetPrintSettings causes a crash |
| NWASM-10165 | Email footer inline images are displayed as attachments |
| NWASM-10167 | Tabbed table cell color rendering changes unexpectedly |
| NWASM-10172 | The panagenda MarvelClient configuration database specified by NOM_MC_DB in notes.ini is not being utilized |
| NWASM-10202 | An expired certificate is used despite a non expired certificate already existing in certstore.nsf |
| NWASM-10205 | Nomad Federated Login with Google Workspace as the IdP results in a 400 error |
The complete details are available in the HCL Nomad for web browsers 1.0.x Release Notes.
How to get the latest version
HCL Nomad Web 1.0.21 is available through the My HCLSoftware Portal. HCL announced the release on September 15, 2026.
Conclusion
HCL Nomad Web 1.0.21 is a focused maintenance release with no new features, but it contains several useful fixes for stability and compatibility.
For panagenda customers, the most important change is the fix for NOM_MC_DB. Nomad Web once again honors the MarvelClient configuration database specified in notes.ini, including environments where the configuration database uses a customer specific name or path.
If you are using panagenda MarvelClient with HCL Nomad Web, upgrading to 1.0.21 is therefore particularly relevant. The fix ensures that the existing NOM_MC_DB configuration can be used as intended without requiring changes to the MarvelClient configuration database itself.
