The Default Person/Group plugin for MacroView DMF and MacroView Message defaults the value of person/group metadata properties to the current user when saving new documents and emails.
How it works
When a document or email is saved using drag and drop, any person/group metadata columns with internal column names corresponding to names that have been configured will set the default value to the current logged on user.
Important: This plug-in will only function once it is added to your MacroView DMF or Message licence. Contact email@example.com to obtain a licence for these plug-ins.
If you are running MacroView DMF or Message 8.6.103 or later you do not need to install this plug-in separately as it is already included in the DMF or Message installation and will become active once a license has been obtained. If you already have this extension installed and upgrade to DMF or Message 8.6.103 or later you can uninstall the separate add-in.
Close Microsoft Outlook, DMF Explorer (if applicable) and the MacroView DMF Local Service then download and run the Default Person Group installer that corresponds with your installation of Windows.
- MacroView DMF or MacroView Message 8.4.1298 or later
If after installing the plug-in is not available refer to how to activate a licensed DMF or Message plug-in.
Using registry setting
Specifying the internal column names of any person group fields that are to be defaulted to the current logged in user in the following registry key:
Multiple columns can be specified by separating them with a semi-colon.
Using a configuration files
MacroView DMF 8.8.520 and later versions support using a configuration file to deploy these settings.
The expected config filename/path is in the MacroView AppData store location “Extensions\MapFolderNameToFieldValue\configuration.json.config”
To deploy the configuration file, create a Folder in your Central Configuration Location called "DefaultPersonGroup" and save the file named configuration.json.config to this location
Sample configuration file
The format for the configuration files is Json.
"FieldNames" : [
Each value FieldName1, FieldName2, FieldName3 etc. is the internal name of the column.
Save the file as configuration.json.config
See the Setting a Central Configuration Location for more details on how to deploy the file.
Note: If both a configuration file and registry settings are defined the configuration files will override the registry