Issue with "Automatic Saving" Feature in M-Files for Outlook Pro – Required "Name or Title" Property for Folder Rules & Outbound Email Limitation

Hello everyone,

I’m currently testing the new M-Files for Outlook Pro add-in, particularly its configuration in M-Files Admin, as my team has tasked me with evaluating its capabilities. I’ve set up the configuration in my demo environment and am testing its core features.

One specific issue I encountered relates to the "Automatic Saving" feature, which should allow emails to be saved automatically in M-Files based on folder rules. The idea is that emails moved to a designated Outlook folder will be saved in M-Files with predefined metadata, and replies in the same conversation should be automatically saved as well.

Here are two issues I've encountered:

  1. "Name or Title" Property Requirement: It seems that my document class must include a property specifically labeled "Name." Without this exact property, the folder rule cannot be defined, and I receive an error. For instance, if I attempt to use a custom property like "Title – Sales Order" instead, the rule fails and cannot be saved. I’d like to know if there’s a way around this requirement or any alternative configurations.

  2. Inbound-Only Email Saving: I’ve noticed that only inbound emails are saved with this feature. For example, all incoming emails in the same conversation thread are  saved automatically, but if I reply to this email, my outgoing messages aren't saved. I couldn’t find any documentation clarifying this limitation. (Refer to Screenshot 1)

Has anyone experienced similar issues, or are there known solutions or configurations for these limitations? Any guidance would be appreciated!

Thank you in advance for your insights!

Parents
  • To describe the issue with more details, i have some examples here attached with screenshots. 

    Classes that i used for automatic and manual saving emails:

    Using this class for saving emails automatically (=> defining a folder saving rule) won't post an issue, as this class "E-Mail" has the property "Name or Title" (first property in the screenshot). 

    But if this property doesn't exist, say for this class "VK-Schriftverkehr" (eng.: sales correspondence):
     (S.shot2)

    I will get an error when using this class to define a folder saving rule (refer to S.shot 3 and 4)
      =>  (S.shot 3 & 4)

    But if i were to save an email using this class manually, the email will be save to M-Files. (refer to S.shot 5 & 6)

     =>  

    (S.shot 5 &6)

    Is this a bug ?

  • Our product team is looking into the folder rule issue, thanks for reporting!

    "Send and save" feature is coming in a future update, currently targeted for early next year.

  • The folder rule issue will be fixed in the December update, which will also bring new functionalities for the add-in.

  • Will the update also include the send and save feature?

  • Not yet, but there are other improvements.

  • ok thank you. 
    I was also told to test out the "M-Files for Outlook Lite" Add-In but i couldn't find this product on the M-Files catalog. If memory servers me right, the product release date is still TBD according to the  Product Guide for M-Files Outlook Integrations. Could the product team give an estimate to when the lite version will be released? 

  • You are correct, M-Files for Outlook Lite is not yet released. We don't yet have a release estimate but will communicate it as soon as we have one.

  • Hello Joonas,

    there's a new update Version for the Add-In with the current version 24.12.1.0

    However, this MF-App is not signed.

    The ZIP Folder consist also a powershell script "signature" but trying to run this script leads to an error as well.


    Since i want to try this add-in with a cloud vault, apps must be signed.. The previous version of this app was signed.. What happened? Can the team fix this issue?

  • Did you try installing the .zip file that you downloaded from Catalog as is? You are not supposed to unzip it as the digital signature included in that PowerShell file must accompany the actual application.

Reply
  • Did you try installing the .zip file that you downloaded from Catalog as is? You are not supposed to unzip it as the digital signature included in that PowerShell file must accompany the actual application.

Children