Hello, 

The font was not installed at first. After we noticed,  we installed the font on the server, but still the resulting pdf is not using that font but a default one.

What can be done in that case?

Hi Miruna. I am encountering this same issue now. The font is definitely installed on the server on which Workflow is running. When generating a word doc, the font is there and visible in preview and when opening the resulting word doc on the server. 

As soon as you switch to 'convert to PDF' in the Workflow task, it ignores the font and goes to Times New Roman. Unlike others are seeing (i.e. here: https://answers.laserfiche.com/questions/123869/Workflow--Update-Word-Doc--Font-Substitution-Workaround)- I get no warning - it just ignores the font.

I'm on version 10.4.1.223 of Workflow. Thanks.

EDIT: I think this must be to do with a 'family of fonts' and your embedded PDF generation. If I use any of the 'main' fonts like Tahoma, Arial, Verdana or Times New Roman (e.g same list of fonts that are selectable natively in Forms) no issue. But if in your Word template you use some other lesser known but popular font like Century Gothic, Avenir, Gill Sans MT etc; and the 'Update Word Doc' PDF generation will default to Times New Roman.

I have the same issue, is there an update on this?

Hi Chris. I ended up making this a support case, and the 'solution' was to use some HTML in the 'Update Word Doc' activity:

In Workflow, edit the "update word document" activity and for the merge field value for the MeetingNotes field, change it to

<font face="avenir medium" size="2">%(RetrieveBusinessProcessVariables_Summary_Notes)</font>

Make sure the "options" value for that field is "rich text" still. Then republish the Workflow and test again.

Obviously you will need to replace the bold values for your own field names and font choice etc. Hopefully that should work for you.

I did ask Laserfiche whether that was going to be a short term workaround, but so far it looks like the only option.

It has worked and continues to work for us even after updating LF Workflow to a new version.

Let me know how you get on.

Thank you for the update. I think I am still missing something.

I made the change in the token properties of the merge field and made sure "rich text" is cited in that fields options. Still not showing my desired font.