Another interesting question today, on how to convert a Nintex Form into any type of document. I thought the easiest would be to go to HTML. Rather than building the entire HTML in the Nintex Workflow, I decided to create a template HTML file. Store that in a document library and use that as my starting off point in the workflow. Granted, this is not the ideal way to convert a Nintex Form to something else, but it is one way. There will be better ways in the future.
There are a few things we start with.
1. the SharePoint list that we build the Nintex Form on
2. SharePoint Document Library to hold the HTML template (I called it NF-HTMLDocumentTemplatest)
3. SharePoint Document Library to hold the final HTML file that we create (I called it NF-HTMLDocuments)
4. A Nintex Workflow to read the template, replace the tokens with real values and store the result in the destination library.
Overall, this took a whole 5-10 mins to put together, but the HTML file I created is not pretty. But I’m sure you guys are way better than me in making things look good, especially in the WWW world.
Now in my example, it’s a very simple list and I didn’t make many changes to the form.
The HTML template is also quite simple, as it only has an HTML table with some tokens that we will replace later (tokens are #!TITLE!#, #!COUNTRY!# and #!POPULATION!#)
The next step is to build the workflow. It takes 5 actions, because all we’re doing is reading the template, replacing 3 tokens and write the HTML to a document library.
I won’t go into the details of the workflow here, because I mention it in the video above and you’ll be able to download it from the download section below.
When we run this workflow, this is what the HTML file looks like when rendered in IE.
I told you it wasn’t pretty. This is really just a proof of concept to show you what you can do. I hope this helps those who want to send out some data from a form via email or just save it somewhere in the SharePoint environment.
Make sure that update the Workflow since the url to the template and the output document are hardcoded paths. Also, the Web Request actions use a Credentials constant called Farm Admin.