The Eclipse Sidebar action now has three options for the initial state of the sidebar: Open, Thin, and Closed.

Previously there were only two options (Open and Closed), and the old "Closed" option now maps to the new "Thin" option to match the naming convention used by the Notes client.

The "Enabled Ports" field on the Location document form is no longer hidden

The MCUpgrade Config Wizard now allows to specify a central location for the latest install package on the Distribution tab.

The MCUpgrade Config Wizard now allows to specify a central location for archiving install packages on the Distribution tab. When enabling this option, older "latest packages" (see above) will automatically be archived into "packagename of latest package" subfolders of the archive location.

When publishing upgrades, changes are now logged into the archiving folder (if enabled), or the publish folder. The last 20 change logs are kept.

On the Data Migration tab, cleanup of old workspace folder(s) can now be enabled. Requires MCUpgrade >= 14.2.3. If enabled, existing workspace folders will be cleaned up (after uninstall, if applicable and before moving them, if applicable, and) prior to carrying out install instructions. The cleanup procedure should preserve all current settings.

Installers are now automatically selected after Import from within MCUpgrade Config Wizard.

Note that when importing more than one full client installer, no installer is selected (as we would not know which one to select). Also note that when importing one or multiple addons, they are merged with any already selected addons.

When publishing a MarvelClient Upgrade Configuration, all installers were always deleted from the publish folder and copied over again. Now, only missing installers are copied, existing preserved, and superfluous deleted.

The MCUpgrade Configuration wizard now computes the suggested highest version information from all selected full and addon installers (whichever apply) and suggests to adjust the target version on the Conditions tab if different upon publishing. In line with this change, the target version field no longer has a default value. If the field is empty it will be filled in automatically upon publishing.

The full and addon installer lists have been enhanced for easier selection:

Full installers are sorted in the following order: Standard, Cascaded, Admin&Designer, Basic, HCAA, ICAA.
Within each, all installers are sorted by bitness (64 before 32) and within each bitness by version descending.

Addon installers are sorted in the following order: Standard language packs, Basic language packs, Fixpacks, JVM Patch, Plugins (Connections/Sametime), SwiftFile, HCAA, ICAA, HCAA Basic language packs, and Unknown components.
Within each, all installers are sorted by bitness (64 before 32) and within each bitness by version descending.

To reduce the space used by the top section of the form, the MarvelClient Upgrade Configuration form as been changed and enhanced as follows:

• The Upgrade Directory field has been moved into the Distribution tab
• The Wizard mode has been moved from below the "Type of Upgrade" field to its right

Previously, viewing or selecting installers required a lot of scrolling on the Distribution tab. The entire installer and addon selection portion has been moved into its own new tab "Installers".

In previous releases, one could only choose to enable or disable the upgrade actions, but not to skip the step (Cancelling would cancel the remaining steps). Now, if one selects "Cancel" in the "Create / Update Actions dialog", publishing continues without creating or updating any upgrade documents, but with creating MCUpgrade.zip and publishing it, if so selected.

In the MCUpgrade Config Wizard, on the setup tab, the entry Create_RXX_Databases was previously automatically resolved as Create_R14_Databases for Notes 14. This has been adjusted to automatically resolve to Create_R12_Databases for all current and future Notes 14 releases.

The MarvelClient Analyze database now supports a new optional role [ViewCollapseAll]. When a user with the role opens a view in the analyze database, the view will be collapsed (=all categories closed) every time it is opened. Note that this works on Windows only.

The PerNAB agent now allows to override notes:userdetails_mailtemplate via user:userdetails_mailtemplate_override. The original template name is then stored in notes:userdetails_mailtemplate_org. Overriding the template name can be conditional by setting user:userdetails_mailtemplate_override_if to a template name that must match for override to occur.

In line with this enhancement, the PerNAB version has been updated from 10.0 to 14.0.0

The Mail Template Replace Design feature now has an Edit button, for modifying an existing configuration

Fix for error in Cleanup agent: Cleanup_NotesVersion in line 31: Type mismatch

Previously, the "import installer"dialog always opened "C:\Users\Public" as default location to import installers from. Now, the "import installer" dialog will open the following folder as default:

• if opened from the installer view, it will use the folder of the currently highlighted/first selected installer, if the folder exists (from the viewpoint of the user launching the dialog)
• if not used from the installer view, or the folder of the highlighted/first selected installer does not exist, it will use notes.ini:$MCU_LastInstallerPath, if the corresponding entry and folder exist
• if no folder was resolved from the above, "C:\Users\Public\MCUpgrade\Installers" is used, if it exists
• if no folder was resolved from the above, "C:\Users\Public" is used

After importing an installer, notes.ini:$MCU_LastInstallerPath is set to the folder of the first imported installer, if it is different from "C:\Users\Public" and "C:\Users\Public\MCUpgrade\Installers".

The tabs in the desktop browser preview are now clickable in their entirety. Previously, only the text was clickable.

Updated the digital signature of all binaries (including the panagenda Installer Service and helper DLLs) to until Nov 2024 (previous releases were valid until March 15, 2023)

In line with the change, the version of the panagenda Installer Service is updated to from 10.1.7.1 to 10.1.8.1, and the version of the helper binaries is updated from 10.1.14.0 to 10.1.15.0

The executable nice64.exe has been updated to V14

If the Cleanup_NotesRenames function fails on a document during the cleanup process, it now process the next document instead of exiting with an error

The default list of Old Notes Data excludes now also includes the following two entries when creating new upgrade configurations:

network:workspace\logs*
network:(IBM|HCL)_TECHNICAL_SUPPORT*

Note that this does not affect existing upgrade configurations.

The Mail Template Replace Design feature can now accept multiple target configurations for the same template.

There is also a new option: "Restrict to major Notes version"

If the Cleanup agent encounters the error "Error in CLEANUP_NOTESRENAMES in line 37: Object variable not set - Function aborted" it now continues processing the next document instead of stopping

Changed the "Roam latest backup" example actions so they default to a runtime of Before Login instead of BL Init.

Also changed the title of the "Set mc:DXL Export/Import Roaming" example action to suggest that the DXLRawImport agent should use a runtime of "After Write".

The Roaming Cleanup action now supports a runtype of Background Init.

The "ROAMING: Exclude ini-Entries Directory, SharedDataDirectory and more" example INI Filter action now also excludes the following entries: EXTMGR_ADDINS, AddinMenus, and NSF_HOOKS

Several changes to allow various pieces of code to work properly with the 64-bit 12.0.2 FP2 client, including:

• Online Update using the LotusScript connect option
• Reading the clipboard (Application/Mailfile action, Profile document action)
• Getting the list of servers (Agent action, Recent Apps action)
• Reading the low-resolution database icon (Application/Mailfile action)

Note that these things worked properly on previous 64-bit clients, but changes were required with 12.0.2 FP2. These will also be needed for Notes 14.

Release notes URL generation code has been updated to properly detect templates tagged as Notes 14.

Fixed a problem where Online Update using a Java connection option and proxy server settings would fail on Notes 14.

Fixed a problem where the GetLicenseInfo.xml file generated by Online Update is sometimes empty after a failed connection, and cannot be deleted or modified until the Notes client restarts.

Fixed a problem on the Application/Mailfile action form where the validation display shows the wrong text if 'Variable' is selected as a Local Replica option and the 'Variable' field is empty.

The Application/Mailfile action has a new "Background" option on the Local Replica tab when creating a new local replica.

This new functionality requires MarvelClient 14.0.1 or higher.

OnlineUpdate now works properly on the Windows 64-bit client when using the "LotusScript" connection option

NOTE: the 64-bit version of Notes 12.0.2, up to and including FP2, OnlineUpdate will not work properly with a connection option of "LotusScript" and a proxy option "Use System Settings". This is due to a bug in the Notes client that was fixed in 12.0.2 FP3 and Notes 14.0.0. If you are using an affected version of 12.0.2, please choose a different connection option, or use the menu option Actions – O. Online Update – 1. Perform Full Online Update instead of using the OnlineUpdate form.

The example INI filters used by backup and roaming actions now include EXTMGR_ADDINS, AddinMenus, and NSF_HOOKS to make sure those settings don't roam (they can cause issues roaming between 32-bit and 64-bit clients, or between Mac and Windows clients).

Fixed a problem where the GetLicenseInfo.xml file generated by OnlineUpdate could be locked as a zero byte file if incorrect connection options were used, requiring a restart of the Notes client before the file could be deleted or overwritten.

If "Variable" is selected as the Local Replica option on an Application/Mailfile action and the Variable field is empty, the validation display shows the wrong text.