Added support for managing replication priority for local databases. Requires Config template 20201216103500 or higher.

Add timestamps and thread ids to console log messages.

Allow new MC_LogIncludeStdOut variable to be set during 'before login init' runtime.

New ini variable MC_LogIncludeStdOut, for use by support when troubleshooting very specific problems where we need to capture console messages.

Nomad-only, changes for testing

Better handling of Location documents when using limited names roaming. Workaround for an issue that could occur if roamed Location documents have exactly the same NoteID as documents from a previous installation, but a different name.

New placeholder %NOTES_USER_COMMON_NAME% for use in backup and roaming actions - returns the common name portion (CN=) of the current Notes user

Fix for roaming/rollback action if 'restoreregex' option was used and the regex matches multiple files. Prior to this fix, it was possible that files with multiple regex matches were restored using the wrong file name.

New MC config variables:

• • os:process_creation_time = the time the Notes client process was started
  • os:process_runtime_ms = the amount of time the Notes client has been running, in milliseconds
  • os:user_idle_time_ms = the amount of idle time (no keyboard or mouse activity) for the current user session, in milliseconds
  • os:user_documents_directory = absolute path to the current user's Documents directory
  • os:user_downloads_directory = absolute path to the current user's Downloads directory
  • os:user_desktop_directory = absolute path to the current user's Desktop directory

The ".ini & Variables" action can now manage:

• JSON files
• XML files
• INI files with or without sections

Requires MarvelClient Config Template version 20200902 or higher.

Added support for SafeLinx proxy authentication on Nomad.

Implemented geolocation for Nomad clients running on Android devices. See release notes for MarvelClient 11.0.3 (below) for details on geolocation.

Added new MC config values for the Eclipse version used by the Notes Standard client: <notes:eclipse_version_major>, <notes:eclipse_version_minor>, <notes:eclipse_version_step> and <notes:eclipse_version_number>.

MarvelClient now handles the situation where a user has multiple shortnames more cleanly.

If multiple shortnames have been defined in a user's Person document, only the first name in the field will be written to the <mc:userdetails_shortname> variable, and all names will be written to the new <mc:userdetails_shortname_all> variable as a comma-separated list.

New MC config variables that indicate where the actions.xml file was downloaded from. <mc:actions_last_remote_source> will be set to "networkdirectory" or "backupset" depending on where it came from, and <mc:actions_downloaded_networkdirectory> or <mc:actions_downloaded_backupset> will be set to "1" if the downloaded actions.xml file from that location was newer than the local actions.xml file.

Added support for new Eclipse actions that can modify items in the launcher bar of the Notes Standard client. Requires MarvelClient Eclipse Plugin 11.0.3 or higher, and MarvelClient Config Template 20200716 or higher.

The server lookup order for the Config DB has changed slightly.

Previously the server specified by <mc:userdetails_lookup_server_fallback> was checked before any servers specified by the <mc:configdb_fb_*> variables. The order has been reversed so the <mc:configdb_fb_*> servers will now be checked before <mc:userdetails_lookup_server_fallback>.

You can use the new <mc:userdetails_lookup_ignore_configdb_fb> variable (bool, defaults to false) to disable <mc:configdb_fb_*> server lookups.

MarvelClient can now change the replication formula for existing replicas. Previously this was only possible for new replicas. Requires MarvelClient Config template version 20200608 or higher.

Customers using HTTP roaming with authentication can use the new MC_ActionXMLRoaming_AuthURL notes.ini variable to roam the actions.xml file.

Added new options to the Cloud Migration action.

It is now possible to use the stored location of the old mail file without requiring it to be opened. This allows the "Change all links" and "Clean up old links" steps to run if the old mail file is no longer accessible.

Added functionality to detect the new HCAA client (HCL version of ICAA).

In older versions of MC, the following config variables will be incorrect if used with HCAA: <notes:mode_running>, <notes:icaa_version>, and <notes:is_icaa>

New feature: Server Access Restrictor

Allows you to prevent Domino server access for Notes clients without active MarvelClient.

This works through a combination of 2 things:

• MC will change the version that the Notes client presents to the server. This new version can be customized by the admin with <ini:MC_ServerAccessRestrictorSetClientVersion>. Example: MC_ServerAccessRestrictorSetClientVersion=99.0.7 FP2
• Set the minimum client level setting in Domino server configuration settings to a sufficiently high number (e.g. 99.0.0).
  

Now, the server will deny access to any client without MarvelClient active, since its version is too low.

Note: The ini variable must be present before login. So it has to be ensured that all clients have it turned on before activating the server-side setting. Also, newly set up clients must have MC enabled and have the setting in their notes.ini (or a pre-deployed actions.xml with an INI action in it).

Added support for the new local database encryption option "AES" that was added to Notes 11.0.1.

If the new option is selected for a database and the action runs on an older version of Notes, it will use strong encryption instead.

Fixed an issue where some manually created bookmarks would lose a view-reference.

This would happen in the case where a user would create a bookmark by drag&drop-ing a tab to the bookmark bar. It would only occur for database designs that use a frameset, and only in newer Notes Client versions. The effect was that the bookmark would open the frameset, but not automatically display the right view.

Added new MC config setting <mc:replpage_create_option> to control how Application/Mailfile actions and Replicator Page (System) actions will create missing Replicator Pages.

Replicator Pages are stored in each Location document and are only created by the Notes client when the Location is active and its Replicator Page is first opened by the user.
Up until now, Application/Mailfile actions and Replicator Page (System) actions would only add entries to existing pages, and ignore Locations that not yet have a Replicator Page.

Now you can set <mc:replpage_create_option> to enable these actions to automatically create a new Replicator Page.
Possible values:

• create_none - default option (old behavior); don't create any new Replicator Pages.
• create_empty - create an empty Replicator Page (not even default entries).
• create_default - create a Replicator Page with the default entries, but no entries for existing local replicas.
• create_full - create a Replicator Page with default entries and entries for all local replicas (same as the client itself would create).

Added new config variables for device type.

• <os:device_type> - a string that can be used in paths and similar places
• <os:device_readable> - a more human-readable string that sometimes contains more information.

These variables are read from operating system calls. Their content depends on whatever hardware and/or drivers return, so their value can be anything and might change.
For devices or operating systems, where no data is available (Windows, mostly), these will be set to the platform name and either Desktop or Laptop, for example: "Windows_Desktop", or "macOS_Laptop".

You can use <os:device_type> in backup-/roaming-keys with the new placeholder %OS_DEVICE_TYPE%

Added ini settings to control how Roaming actions unpack zipped files. Normally a standard temporary file name (roaming_temp.zip) is used for storing zip files so they can be unpacked. In some situations, this file cannot be deleted because other processes lock it (indexer, anti-virus), meaning the next zip cannot be downloaded. The following options should only be changed/used, if there are problems of this nature.

• <ini:MC_Roaming_ZIPTemp_UseRemoteName> (bool, defaults to false): instead of "roaming_temp.zip", use the remote name from the backup set (rev_xxx_name.zip). Will prefix it with "temp_".

• <ini:MC_Roaming_ZIPTemp_PrefixRandomString> (bool, defaults to false): in addtion to other options, prefix a random string (and also "temp_").

• <ini:MC_Roaming_ZIPTemp_CleanUp> (bool, defaults to true if any of the above MC_Roaming_ZIPTemp variables is true, is false otherwise). Delete the file after unzip.

• <ini:MC_Roaming_ZIPTemp_RemoveBeforeDownload> (bool, defaults to true): make sure no file exists in the target temp path before downloading (was the case before, now we have an option to turn it off)

Geolocation

MarvelClient can now determine the current geographic location.

This data consists of coordinates (<os:geo_location_*>) and address (<os:geo_address_*>). 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. If you intend to collect and use this data, make sure to turn on related features on the operating system level ("Allow programs to use location data" etc). You might also want to consider that some platforms will display a prompt to the user to allow the access to this data.

This functionality is still experimental, and has some privacy considerations connected to it, so it is turned off by default. Set <mc:geo_data_enabled> (bool, defaults to 0) to 1 to enable it.

Furthermore, since this functionality is depending on operating system calls that differ in reliability between platforms, it can be en-/disabled on each platform separately.

• <mc:geo_data_enabled_ios> (bool, defaults to 1)
• <mc:geo_data_enabled_macos> (bool, defaults to 0)
• <mc:geo_data_enabled_win> (bool, defaults to 1)

These variables will only be considered if the global flag is set to 1.

Generally, this data will be available immediately. But in some cases it can take a few seconds, or rarely even longer. For that reason, there is a 10-second timeout on retrieving this data. Set <mc:geo_data_timeout_ms> (number in milliseconds, defaults to 10000) to change it

Due to the potential delay, geolocation data will only be collected in background (first server access, and other background run times). If you want to make sure that you have this data collected for analytics purposes, you can set <mc:geo_data_scan_in_shutdown> (bool, defaults to 0) to 1. This will force a read of the data during shutdown.
Note: Geolocation conditions will force a read of the data at the time they run.

Added a new Geolocation condition to only execute Actions based on geolocation data.

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.

Make sure to consider the points mentioned in the Geolocation section above.

Nomad: Changed behavior of MarvelClient during Nomad setup.

If <ini:MC_DB> is not present, MarvelClient will now try to find its Config DB in one of the default paths on both the MailServer from namelookup and <ini:MailServer>. If a database can be found on the namelookup-based server, it will be used. If the server does not contain a Config DB, or cannot be reached, <ini:MailServer> is tried next. If the server does not contain a Config database, setup will continue and MC will be disabled. If the server cannot be reached, setup will fail (but in that case, Nomad setup will fail on its own as well).

If <ini:MC_DB> is present, however, MarvelClient will behave more like on the Rich client, and use the <ini:MC_DB_*> variables to locate the config db. If any of the servers from those variables cannot be reached, setup will fail.

A few more details:

Before, MC would work the same as on a Rich client. If <ini:MC_DB> was missing, MC would try to find the Config database in one of its default locations. These default locations would oftentimes be on the user's homeserver, based on namelookup. If that server could not be reached, setup would fail.

Since many customers have complex setup scenarios, where the homeserver is not necessarily the same as the server against which Nomad devices are being set up, this scenario could cause issues with failures happening in cases where they should not. The new behavior will prevent unwanted setup failures.

MarvelClient for Nomad!

MarvelClient is an integral part of the new HCL Nomad for iOS and Android devices. It is built-in and turned on from the start. This means you don't need to deploy a binary to any Nomad clients, or set any notes.ini variables.
During Nomad setup, and on every subsequent start: If MarvelClient finds a Config DB in one of the default paths on the user's homeserver, it will download actions and run them. Refer to the MarvelClient section in the official Nomad documentation on ways to direct MC to the Config DB if you do not have it at a default path or on a different server.

The available feature scope consists of most actions/functionalities in MC Basic (Analyze, Manage, Migrate). Some of these will not be supported due to technical limitations (e.g.: you cannot run programs on iOS). For a list, see platform limitations section in the main document for the 11.0 release.

Some functionalities are turned off by default and need to be manually activated (local replica and full text index management in Application/Mailfile action, and File Deployment actions). See Config DB release notes for details on how to turn them on.

HCL Notes 11 support!

This is the first release of MarvelClient to support Notes 11. Older binaries will not work, so make sure to update to MC 11 before deploying Notes 11.