Client Data Collection improvements:

• Fixed an "item not found in index" error in the email configuration document.
• Fixed a problem where the collection could fail if the Eclipse data directory is not found.
• An error message is now displayed if MarvelClient is not installed on the client that is doing the data collection.

Initial release with Change Logging.

The Config database now logs changes when Actions are modified, so you have a record of what changed and when. 

Changes to the Action XML can be seen in the Advanced - Logs view, in the new "Changelog" category. The logs will only appear after changes are made with an updated Config database template (changes made using older templates will not be available).

When using URL as a download location on the Distribution tab of a Configuration document, you now have the following new options:

• Username
• Proxy server
• Follow redirects
• Close connection after each chunk
• Additional URL options

Added validation code to Location action to prevent newline characters from being added to Mail File and Mail Server fields.

New tab for License Details on the Online Update form. Displays information about the entitlements and expiration date of the license that was used for Online Update.

Changes to the ".ini and Variables" action:

• Changed the XML for the remove action, to make it work properly with versions of the DLL that were expecting a value.
• Fixed a problem for this action where backslashes in regex values were not properly escaped for "Only if matches" conditions.
• Fixed a problem where the "Only if matches" condition for a remove action was ignored.

Fixed a problem where the "Offline replica maximum attachment size" value in the UI was rounded, but the unrounded value was used in the action XML.

Modified the Profile Document action form so time-range type fields are displayed properly in all rows.

Fixed a problem where disabling the "Manage root notes.ini" option would cause the "Prepare or Public Upgrade" button not to work properly (no actions were generated).

All XSLT documents used for parsing XML uploads now have descriptions indicating what they do.

New Action for Nomad Application Restrictions. Requires HCL Nomad 1.0.8 or higher, on iOS only.

The following restrictions can be enabled or disabled via MarvelClient:

• • Adding attachments from the mobile device (including photos)
  • Importing attachments from the mobile device (including photos)
  • Viewing attachments
  • Cut/copy/paste operations
  • Opening the Notes mail file
  • Enabling local replication and offline replicas
  • Setting the maximum size of attachments
  • Locking the maximum size of attachments so users can't change the value
  • Allowing biometric authentication (FaceID or TouchID) to unlock Nomad

Various small enhancements and fixes for Mailbased installation:

• • Added descriptive text for the Send To option
  • Closing and saving the Mailbased Installation document will no longer ask to send; you must use the "Send To" button
  • If you enable binaries in the DLL update view, there is now a prompt that reminds you to update the binaries on the Mailbased Installation PostOpen script.

The Cleanup and PostProcessing actions will now run after the Audit process if no Audit Configuration document has been created.

NOTE: If you have a Cleanup Configuration document defined (from the Administration/Cleanup & More option in the navigator), the parameters in this document are used when the Cleanup action runs. Please check this document to make sure the parameters are valid for your environment.

Source filepath / URL are now also editable when distributing files without MC, leading to a corresponding MCUpgrade.ini entry SourceDirectoryInit. This new entry only becomes effective when MCUpgrade.exe is executed outside of the UpgradeDirectory, UpgradeDirectory is not set in MCUpgrade.ini, or MCUpgrade.ini is missing.

Note:
SourceDirectoryInit overrides HKEY_LOCAL_MACHINE\SOFTWARE\panagenda\MarvelClient\Upgrade\SourceDirectoryInit.

At the end of publishing an upgrade, the question "Do you want to copy the installers to the stage directory, too?" has been changed to "Do you want to copy the installers to the publish directory, too?". This will create a clean publish directory (on the same level as build and stage) with only the relevant upgrades components in them.

Requires MCUpgrade 11.0.33 or newer to support automatic unzipping of MCUpgrade.zip.

MCUpgrade 11.0.33 and newer no longer send SMTP Emails upon deferral. Instead, STMP info emails are sent, which can be disabled (=NEW) on the Tracking tab if Deferral is enabled. When re-publishing an upgrade with MarvelClient Upgrade releases < 11.0.33, you will get two deferral notifications unless you disable the new tracking option.

Improved behavior when opening a user document from any detail document (desktop, notes.ini etc.).

Previously it was only attempted by replica id, potentially searching for the user document in the replica on the top of the MC Analyze icon stack. Now, the Analyze database first checks whether the user document can be found by current file path, with fallback to replica id.

Fixed an issue where manual categorization of MCUpgrade Actions was overwritten upon re-publishing.

Important:
Before manually categorizing your MCUpgrade actions after applying this update, you must FIRST republish any existing upgrade configurations that you want to categorize freely. After creating new upgrade configurations or re-publishing your existing ones you can freely categorize them.  

Fixed an issue in OnlineUpdate, where sometimes it would display the following error: "Form has been deleted. The application design may be out of date. Try updating the application design."

This error did never interfere with OnlineUpdate itself, it just prevented a final dialog with detailed info about the updated components from being displayed. The components are now instead shown in the OnlineUpdate form itself, on a new tab next to the "Progress"-tab.

The Cloud Migration action now has new options to better deal with cases where the old mail file cannot be opened.

With this release, the action will do the following to find the path to the old mail file:

• If the option "Use stored value from profile" is enabled, and it can find a mail database location that was stored in the profile by the Cloud Migration Preparation action, it will try to open the mail database at that path. If it opens, that path will be used.
• If the option "Use stored value from notes.ini" is enabled, and it can find a mail database location that was stored in the notes.ini by the Cloud Migration Preparation action, it will try to open the mail database at that path. If it opens, that path will be used.
• If the option "Use stored value from location" is enabled, and it can find a mail database location in the currently active location document that is not pointing to a new server (as indicated by the pattern), it will try to open the mail database at that path. If it opens, that path will be used.
• If "Abort if old mail file cannot be found" is enabled, and none of the three options above could open the mail file, the action will abort here.
• If the option is disabled, and "Skip/fail steps if old mail file cannot be opened" is enabled, the action will assume no old mail file can be found and further steps will behave accordingly. (This would match the behavior of the previous version).
• If both options above are disabled, the action will try to use an old mail DB location without opening (and thereby verifying) it. It will use the first of the mail database locations that can be found by the first three steps.
• If "Abort if old mail file location is unknown" is enabled, and none of the first three steps could find a mail DB location (or all three were disabled), the action will abort here.
• If that last option is disabled, the action will assume no old mail file can be found and further steps will behave accordingly.

So with these new options, the action can be configured to require old mail database open (to ensure it is there for replication, and have a validated path for changing old icons/bookmarks/etc), to require at least the path to be known (replication fails, but changing old icons/bookmarks/etc will work), or to just work either way and skip/fail steps.

IMPORTANT NOTE

The following four settings are automatically added to MCUpgrade.ini when performing a full client ICAA/HCAA install for possible coexistence with Notes 10/11, if:

NICE uninstall is set to "Do not uninstall" on the (Un)Install tab AND
(the new notesdatadirectory is set to (%MCU_NotesDataDirectoryOld%|%LocalAppData%\HCL\Notes\Data or %LocalAppData%\HCL\Notes\Data) for multiuser installations OR
the new notesdatadirectory is set to %MCU_NotesDataDirectoryOld%|%ProgramFiles(x86)%\HCL\HCAA\Data or %ProgramFiles(x86)%\HCL\HCAA\Data for single user installations)

(The same applies to ICAA and corresponding paths)

• SkipNotesDataDirectoryMigration=1
• SkipMultiUserDataDirectoryMigration=1
• SkipNotesProgramDirectoryMigration=1
• DeleteNotesINI=0

To make one aware of this special install option, preparing/publishing an upgrade still prompts whether one might want to adjust the new data directory to ICAA/HCAA\Data.

IMPORTANT NOTE

Indexing the Connections Plugin file (HCLConnectionsNotes_20200317-1837.zip) seems to fail at recognizing the plugin. This is not true, the file is a 114MB zip file with Mac and Windows plugins. Simply extract the ConnectionsAddonInstaller.zip and index that. That will also save you 75 MB, since the windows plugin zip is only 39 MB ;-)

In DLL Update actions, the flag "Only execute this update for existing MarvelClient Essentials installations" had no effect. Essentials DLL Updates would always only run on MC Essentials clients.

This old setting has now been removed, and instead there is a new setting to allow a switch from full MarvelClient to Essentials (off by default).

Added new role [DebugRuntypes] to make all runtypes available for all action types in the UI.

Normally, each action will have only the runtypes selectable that it supports. With this role set, an admin will be able to select any runtype for any action in the UI.

Note: This allows admins to select runtypes that might not be supported in the DLL. Which at best means that actions will not run, and at worst can lead to crashes. So use this role with care.

Fixed an issue in the Application/Mailfile action, where providing a replication formula together with the replica settings "Always replicate" or "Variable" would not set the replication formula.

Note: Even in those two cases the replication formula is only set when the replica gets created. It does not get set or updated for already existing local replicas.

Fixed the behavior in cases where admins do not have deletion rights in the Config DB. In older versions, attempting but failing to delete an action would still create a remove instruction leading to potential inconsistencies between the actions enabled in the Config DB and the actions.xml on clients.

Now, the Config DB will check if and admin has deletion rights, and only then will also create remove instructions in the download view.

New action for Eclipse: Cleanup Workbench Files.

The workbench stores a list of all open tabs, but in many versions of Notes 9 and 10, it never removes them when they get closed; data just accumulates over time.
This can increase the size of the Eclipse workspace significantly, and can have negative effects on performance and stability. For MarvelClient, it means roaming those files will take up more space, time, and bandwidth.

This new action will clean up any unneeded information to deal with all these issues. Just scheduling it to run every few weeks should keep the file size in check.

The DLL Update action now has a new flag "not on Citrix".

For Citrix users, the MarvelClient binaries are usually part of their images, and don't need to be deployed or updated by each client themselves. Stopping DLL Update actions from doing anything there will prevent mistakes and possible startup delays.

This new flag is set by default for all newly created DLL Update actions, and also set retroactively if an older DLL Update action is saved. Uncheck this flag if the action fails because it wrongly detects a VDI.

The Config DB will now have set the property "Don't maintain unread marks" by default on new installs. This should increase performance in some scenarios.

Existing databases are not affected, but turning off unread marks manually can be beneficial and is advised if they are not needed.

OnlineUpdate usability has been improved. The message boxes displayed and the options given are clearer and more consistent.

• Added a button to the OnlineUpdate form to just check for new updates, but not apply them (also available via the Action menu in the client).
• If it doesn't find any updates, it will now give the option to abort.
• At the end, it will now only display a single message box listing all updated components.

Added a new geolocation condition to only execute Actions based on geolocation data. (requires MC binary 11.0.3)

It allows checking for location based on address, distance to a coordinate-pair, or position within a coordinate rectangle.
Since reading the location can take a few seconds in some cases, it will re-use location data that has been recently read, with a 120-second limit (can be set in the action).

The condition will fail, if location sharing is turned off. This means that any Action or reference using the condition will not run.

Note: Geolocation support is experimental at the moment, and disabled by default. You can turn it on by setting <mc:geo_data_enabled>=1. Be aware that you must also enable "allow apps to access your location" in the location privacy settings of the respective device/operating system.

Note: Which data is available, and how accurate it is, can vary significantly. Mostly it depends on settings in the operating system and available hardware features. You might also want to consider that some platforms will display a prompt to the user to allow the access to this data.

Added a new Action Settings\CWSBG. Workspace Background to manage the Workspace Background for Notes releases >= 10.

You can attach an image you want to use, or point to an existing image on the target device.

Even though the Analyze template comes with transaction logging turned off, you may want to actually turn it on again in your environment, as long as you are on a decent Domino release.

In the early days of transaction logging, we did not recommend it. Since then, transaction logging has become reliable and awesome, so we encourage its future use.

Added a new feature to collect support data from a client.

This is for manual collection of support files, especially from clients like Nomad on iOS, where accessing the necessary files is difficult. On the device, open the Analyze DB in the client, and use the "Copy support data" link on the welcome page, or "M5. Collect Support Data" from the Action menu of the client. It will zip up and copy the files to the Documents directory on iOS, making it accessible through the Files app. It can then be sent via mail or other options.