You are viewing limited content. For full access, please sign in.

Question

Question

Outlook 2016 - email document function opening with no signature

Laserfiche Version 10 Integrations
Updated February 28, 2018
asked on January 22, 2018

We have recently upgraded to Outlook 2016.  We run Laserfiche Rio 10.  When using the Email Document function, the email drafts are now opening without the default Outlook signature.  I've confirmed that users have a default set for both New Messages and Replies.  Anyone have any ideas?

0 0

Replies

replied on January 24, 2018

Hi Laura,

This is standard behavior in Outlook if you launch it from an attachment. You can see the same behavior if you open windows explorer, select a document, and run 'Send To' -> 'Mail Recipient'.

0 0
View 1 previous reply
replied on January 24, 2018

Hi Justin, 

You're absolutely right.  However I should have mentioned that we're in the process of upgrading computers from Windows 7 to 10, Laserfiche 9.1 to 10.2, and Office 2007 to 2016.  I've noticed that some users on Windows 7 with Rio 9.1 and Office 2007 do indeed have their signature populating when initiating a new Outlook message from a Laserfiche document.  However the users that have been upgraded to 10/10.2/2016 are getting the standard no-signature message generated.  It is not a hindrance to our workload, but more of a curiosity that I'd noticed. 

 

Thanks,

Laura

0 0
replied on February 28, 2018

Could there be a potential Bug here (with this version of Outlook they moved from), as we have the same issue with a Customer who whose Exchange/Email was upgraded from Outlook 2007 to O365/Outlook 2016 and they have lost the Outlook Signature with the Email Document function.  They are on Laserfiche 10.1 SP 2.

0 0
replied on February 28, 2018

This is working for me with Outlook 2016 and the 10.2.1 client. The LF client doesn't interact with the signature, it is using the Office API to crate a blank message and add attachments to it.

0 0
replied on February 28, 2018

Thanks Robert.  We have tested and it works for us as well (Fresh Office 2016 install) but not in the case of this customer who did an in place upgrade from Outlook 2007, like Laura as well.  It seems that possibly an upgrade from Outlook 2007 instead of an uninstall of 2007 and fresh install of 2016 is causing this issue.  

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...