Allow Rich Text in Document Generation
The Document Generation action allows data from the workflow to be dropped into office documents. It does not however allow rich text to be injected into documents.
For example, a rich text field in SharePoint will come into Nintex Workflow as HTML, which will then obviously just appear in a Word document as raw HTML, not interpreted as bold, italic, etc.
Both On-Prem and 365 now support the rich text field when used as a tag in a document template, it will convert assuming html is valid.
Is this supported for Nintex Workflow Cloud? I would hope so unless the Nintex platform products are completely independent of each other and there is no shared base.
Barry Cairns commented
Is this supported in PowerPoint? I tried this and the workflow always suspends with a non-descript error. The same rich text content can be used in Word with no problems.
Kent Del Castillo commented
Karen Newlin is correct below: "This does not work for tables that have been added to Enhanced Rich Text fields and inserted into the Word Document as a tag via DocGen. All table formatting is completely lost. All other HTML formatting seems to work correctly."
Ali Kadhim commented
I am still having an issue with this, I tried both rich text and enhanced rich text and I still get the tags showing the generated word document. can you please advise? thanks
Karen Newlin commented
This does not work for tables that have been added to Enhanced Rich Text fields and inserted into the Word Document as a tag via DocGen. All table formatting is completely lost. All other HTML formatting seems to work correctly.
I have been trying to use Rich text field by tagging the field in document but the table structure, space and many things are totally lost in the generated document
Note: Using Nintex for Office365
Hi, what steps should I take to send the RTF to word?
Tom Castiglia commented
I'm really glad to see this is started. Had to disable Rich Text on some multi line text fields in order to support document generation. Hopefully this feature can get released to Nintex for Office 365 and Nintex 2013/2016 at the same time.