Document Generation allows workflow designers to quickly add the power of dynamic document generation to their business process. With Nintex Workflow Cloud, workflow designers will be able to use cloud-based repositories such as Box, Dropbox Business, Microsoft OneDrive for Business, and Google Drive as a repository for both their templates and their finalized generated document.
Let’s take a look at business process built in Nintex Workflow Cloud and how it uses Document Generation to build a Partner Agreement document based on start variables collected from Salesforce.
Within the Start event, information such as Account Name, Billing Street, and SLA are collected when an Account is updated. We will use the ‘SLA’ start variable to help us determine the partner template.
Depending on the ‘SLA’ value, a variable is set ‘TemplateName’ to the template that will be used. If the ‘SLA’ level is not ‘Gold’ the ‘TemplateName’ variable is configured:
If the ‘SLA’ is listed as ‘Gold’, the ‘TemplateName’ variable will be configured:
So how do these start variables relate to the new Document Generation action within Nintex Workflow Cloud? Well, let’s take a look at how we configured the action in this workflow:
The key settings of the Document Generation action are where did you store your document template, and where does the finalized document. When selecting the ‘Generation Type’ choose between keeping the original source of the document (Word, Excel, PowerPoint) or choose a PDF output. The top ‘Connector’ will allow you to choose the cloud-based document repository your template is located in (Dropbox Business, Google Drive, Microsoft OneDrive for Business, Box).
Since we are using the Dropbox for Business action, we will provide a Member ID. Next, look at how the Template input is configured. We are hard-coding the beginning of the path, but then use the ‘TemplateName’ variable to select the specific document in the Dropbox for Business directory. By being able to access variables within the Template input, file selection can be dynamic!
After selecting the file, we need to start using the Nintex Document Tagger to add our variables information to the template we have created.
After your document is tagged, and saved to the repository, it’s time to select the final repository for the completed document. Select the Connector, Connection, and any other required fields. Next, select if you wish to overwrite files with the same name in the final repository.
Saving the path of the final document is accomplished by storing the ‘Store path’ output to a String Variable. If the number of document generations left in your subscription is required, store the ‘Store usage meter message’ output in a variable.
Once the Document Generation Action is configured, the path output can be used in other actions, such as Express Approval and DocuSign.
Document Generation opens up a new level of possibilities within Nintex Workflow Cloud, and I’m excited to see the solutions that are created!
Visit the Nintex Community today to learn more and engage in conversations with fellow Nintex users!