ndMail 1.6 Update Notes

Follow

Updated:

What's New in ndMail 1.6

ndMail 1.6 continues streamlining your email management. A major focus of this release is the behavior of the Global Filing Indicator (GFI). In response to customer feedback about the GFI not appearing consistent in certain cases, we've improved the behavior so it's easier for the end-user to know when something has already been filed by someone else at the organization. We've particularly focused on situations related to cross-cabinet filings, cached predictions which delay the GFI appearing, users who keep the prediction pane collapsed, and cases related to sending and filing across cabinets. Please find additional features and improvements below.

Highlighted changes

Optimized GFI caching

The Global Filing Indicator (GFI) was previously cached with predictions so if predictions were generated for a given message, both the GFI and predictions would be cached for up to 15 minutes. With this release, the GFI is decoupled from the predictions so the GFI will update immediately upon clicking on a given item even if predictions are already cached for that item. This allows users to see when an item is filed by someone else in more real-time. 

Back to Top

Cross-cabinet GFI improvements

Previously, if a user had two cabinet tabs open in the ndMail prediction panel, Cabinet A and Cabinet B, and they had Cabinet A selected as the active cabinet tab, all items that were filed in Cabinet B would not display the GFI. In other words, the GFI used to be tied to a specific cabinet. With 1.6, the GFI process will check all cabinets that the user has open as tabs on the prediction panel and will set the GFI for that item if it is found to be filed in any of those cabinets. Additionally, if it is found to be filed in a cabinet that is not the active cabinet tab, we will place a blue checkmark on the cabinet tab where the item is filed, per the screenshot below.

mceclip0.png

 

Back to Top

GFI support with collapsed prediction pane

Users can now leave the prediction panel collapsed and the GFI will continue to update. Previously, the GFI required the prediction panel be open/expanded. 

Back to Top

Option to force mapping of new Outlook folders

Note: This feature requires Folder Mapping build 1.0.7180

Previously in Folder Mapping, users had an option to prompt to map new Outlook folders when they are created. This feature enhances that to allow firm admins to deploy a registry key which forces their users to map new Outlook folders (registry key detailed below). When the user creates the new folder, they will see the dialog shown below.  

mceclip1.png

 

Back to Top

Additional Improvements

  • Reduced add-in load times when starting Outlook (requires ndOffice 2.6).
  • Improved Folder Mapping processing queues when issues are encountered with the customer's Exchange server. (requires Folder Mapping 1.0.7180).
  • Optimized the Folder Mapping queue such that deduplication occurs at the time the new item is added to the local queue in Outlook rather than after the filing request happens (requires Folder Mapping 1.0.7180). 

Fixed issues:

  • Fixed an issue getting conversation ID information from Exchange in certain cases.
  • Fixed an issue where the Windows 1903 update broke keyboard input fields in both ndMail and ndOffice in Outlook (requires ndOffice 2.6+ for the Outlook panels fields).
  • Fixed an issue where delayed send in Outlook would prevent items from being sent when ndMail is enabled. 
  • Fixed an issue so that using the shortcut Ctrl + > now refreshes predictions properly. 
  • Fixed an issue where Folder Mapping would prompt users to map new Outlook folders more than once if the user had Outlook open on multiple machines (requires Folder Mapping 1.0.7180).
    • See registry setting below.
  • Fixed an issue with Folder Mapping if the user mapped a folder and profiled the mapping with a date field value so we now properly capture that date (requires Folder Mapping 1.0.7180). 
  • Fixed an issue in some environments where Outlook could hang with Folder Mapping delegate filing is enabled and with Outlook set to Work Offline (requires Folder Mapping 1.0.7180).
  • Fixed an issue when delegate filing is enabled if the delegate deletes an owner's folder where the delegate is prompted to map the newly deleted folder (requires Folder Mapping 1.0.7180).
  • Fixed an issue where, in certain instances, the customer's Exchange Server does not return the internet message ID of a sent item properly when it is requested which then leads to a 400 response when the filing request is submitted (requires Folder Mapping 1.0.7180).

Back to Top

New Registry Settings for ndMail Folder Mapping

Registry Path:

‘Computer\HKEY_CURRENT_USER\Software\NetDocuments\ndMail\Folder Mapping’

OR

‘Computer\HKEY_LOCAL_MACHINE\Software\NetDocuments\ndMail\Folder Mapping’

Note: Settings on administration level prevail over user level settings.

 

PromptIntervalOnFolderCreate registry

 Values

NOTE: Most users won't need to use this. Given users have Outlook open on multiple machines and are using PromptOnFolderCreate set to True. This setting determines the amount of time difference (in seconds) between the folder creation time and the folder modification time. On the machine where the folder was created, these two values will be the same. On another machine, there will be some amount of time difference between the two depending on how quickly Exchange/Outlook creates that new folder on the second machine. The default is 0. When set to 0, the user is only prompted to map the folder on the first machine where the folder is created if multiple machines are actively running Outlook. If prompting on all machines is desired, a value of 60 could be put in which would account for 60 seconds of Exchange/Outlook delay in creating that new folder and would therefore prompt the user on all machines to map the folder. 

  • Integer value

ForceMapOnFolderCreate registry

 Values

Forces users to map new Outlook folders upon creation. True will not let the user create a new folder in Outlook without mapping it to NetDocuments. False will not force the user to map the new Outlook folders but could still prompt the user to map the folder if the PromptOnFolderCreate is set to True. 

  • True

  • False

 

Back to Top

Was this article helpful?
1 out of 1 found this helpful
Powered by Zendesk