Skip to main content

The workflow and document template I am walking through in this blog and video is available to download from our Nintex Gallery at this link. 

 

Creating Your Template in Nintex AssureSign

 

The first thing we will need to do is create the template in AssureSign that we will be passing data to from Nintex Workflow Cloud.  I am using a word document, which I will upload into AssureSign in order to create the template

 

20962i591AE0262BAE80F1.jpg

 

 

To start creating the template click on View Templates in the left hand navigation

 

20963i90741429A3351155.jpg

 

Then on the next screen you will need to click on create template, give your template a name and click continue

 

20964i9E318E7B33460567.jpg

 

Then you need to drag and drop your word document into AssureSign

 

20965iBAE738644EB9E728.jpg

 

Now we can start to build out our template, we need to add a signer and then we will have the ability to create our JotBlocks on the template which is where the information we collect in Nintex Workflow Cloud will be passed into.

 

In order to do this, drag a JotBlock from the right hand menu onto the template where you want to have the information placed.

 

20966iF869D81E5BA58FC2.jpg

 

The JotBlock can also be resized by grabbing the bottom righthand corner of it and dragging it to the size you want it to be on the template

 

After dragging the JotBlock onto the template you will get a popup that will allow you to configure it, you will need to give it a unique name before saving it.

 

20967iB6143FFB11D1D812.jpg

 

Now since we will be passing the information to the JotBlock from Nintex Workflow Cloud we need to configure a sender input for it.  These can all be created ahead of time, or you can create them when your adding the JotBlock to the template by clicking on the blue circle located in the Edit Fixed Text line.

 

20968i78FE1522BD2B09F2.jpg

 

This will popup another window allowing you to configure the sender input for the JotBlock.  Give it a name and click Save Sender Input.

 

20969i06D81322FA49FC43.jpg

 

Now we can click on Save JotBlock to close the configuration of the JotBlock.  You will see the JotBlock with the sender input listed in it on the template.

 

20970i638A6CF464EB4411.jpg

 

Repeat this for all fields on the form that you want populated from Nintex Workflow Cloud.  Your template will look something like this after you populated all the fields with JotBlocks.

 

20971i671457091E823674.jpg

 

The last step in the template creation is to add the signer/initials JotBocks to the template.  This is done by grabbing the Signature or Initials JotBlocks and placing them on the template where we want these actions to happen

 

20972i242911253AEE1929.jpg

 

The image here shows one initials JotBlock and the signature JotBlock on the template.  Now we have completed our template and we can move to Nintex Workflow Cloud to configure the connectors.

 

Note:  If you want to allow the users to update information in the document during the signing process use the blue JotBlocks.  If you just want the signer to only be able to sign and initial the document, you need to use the fixed JotBock.

 

20973i6E13746A9C8F6B3A.jpg

 

Using the AssureSign Connectors in your workflow

 

There are two connectors available in Nintex Workflow Cloud for AssureSign.  The Get a Signature action will allow us to create our connection to AssureSign and map the fields from the workflow to the sender inputs in AssureSign.  The Get a signed document allows us to get the signed document back so we may use it in the workflow to email out or maybe save to a system of record other than AssureSign.

 

20974i8068CB0C39FF86B5.jpg

 

I am not going to get into form creation in this post, but we will need to create our form that will capture all of the information that be used to populate the template before it is signed.

 

20975iAF83BFCC7F7825ED.jpg

 

Once we have the form finished, we can create our workflow, in this example I am just capturing the data on the form and sending it to AssureSign to get a signature then I am checking to see if it was actually signed or if it was declined by the signer.  If it was declined, I am sending an email to the initiator to let them know it was declined and if the document was signed I am getting the signed document back and sending an email with it attached.

 

20976iCC2197A4C140E298.jpg

 

Let’s take a look at how the AssureSign connectors are configured.  We will first need to create our connection to AssureSign, select the account if there is more than one available, then select the template we are going to be using.

 

20977i917682B94AAD0E24.jpg

 

You will need to create and API user for your connection, when created it will give you and API Key and API Username, make sure to copy and keep both of these in case you need them again later. 

 

20978iFC2540DE7CDB7496.jpg

 

After creating the connection and selecting the template we will need to add the signer details. In my case I am populating these with data collected on the form, but they could be hardcoded as well. 

 

AssureSign does offer mobile e-sign so if you populate the Mobile phone the signer will also receive a text asking for permission for AssureSign to send them the signing information, if they reply YES they will receive that info and be able to complete the signing from their mobile device.

 

20979i1F83B70A3D7CBAD8.jpg

The next thing we want to do is map the sender inputs to the form fields, so the data will get passed to the template

 

20980i2B0C14D893882E2C.jpg

 

I am using the Start event Form Variables to map the form fields to the sender inputs

 

20981iEA5DD3FD0F8DA014.jpg

 

Once your done mapping the form fields to your sender inputs the last thing we need to do is set a variable to capture the output of the action which will be used later to retrieve the signed document

 

20982i1027A90DE033383D.jpg

 

That’s it! The Get a signature action is now configured.

 

In the workflow I created I am checking to see if the document was declined using a branch by condition and checking for a Declining signatory, if one exists it was declined if not then the document was signed.

 

20983i320EBB7300A462AD.jpg

 

You could also check the envelope status as well and branch by status.   The available statues for the envelope are 

  • in-progress
  • expired
  • completed
  • cancelled
  • declined
  • signer_authentication_failed

 

Now lets setup the Get a signed document action to retrieve the signed document from AssureSign.  We will set our connection, account and template just like we did in the Get a signature action.  Then we will select the document to return and also pass in the envelope id so we get the correct signed document back.

 

20984iE977AA724F5BC776.jpg

 

 

 

To get the envelope ID use the output variable that was configured in the Get a signature action

 

20985iC5BEFED838913AA5.jpg

 

Then we will save that signed document into a variable that can be used in the workflow to email the signed document or maybe save it to another system of record

 

20986i08870EFBA93C65F0.jpg

 

Ok now we have both connectors configured, lets test the workflow.  Once we fill out and submit our initial form we will receive an email that the envelope was sent to the signers for them to sign.  These emails can be customized to include your company logo and other information you may want to send

 

20987i46FAB6456A2B07BB.jpg

 

The signers will receive an email saying they have a document that is ready to be signed with a link to begin signing

 

20988i59BA65A095A74293.jpg

 

To begin the signing process, check the box saying you have read and agree to the terms and conditions and click start signing

 

20989iDD8680FFEB0BF4E8.jpg

 

Setup your signature by either typing it in or using your mouse or a stylus to create it and your initials and click adopt signature

 

20990iF2323E1F0213E95B.jpg

 

Now we can review and sign the document

 

20991i1DDBA76A632C0699.jpg

 

Click Apply initials and signature and then click finish to sign the document

 

20992i294856A1467D9A43.jpg

 

We now have a signed document that will be saved in the envelope in AssureSign and returned to the workflow by the Get a signed document action and emailed to us

 

20994i511EBB1B37B4B1D1.jpg

 

20995iF778A52C4CB2757E.jpg

 

 

20996i584D706C93D5571C.jpg

 

If you have any questions or would like to see a demo of Nintex Workflow Cloud and AssureSign please reach contact your account manager or sales@nintex.com

 

 

What do i configure in the NWC api connection screen?



I did the following, but account and template stay empty.



 





 



 


@DanielAdvantive 



 



Were you able to create the API User in AssureSign?  And then use those credentialss in the connection?  It sounds like the connection didnt work correctly if you arent seeing anything in the account and template dropdowns.


Reply