Add Mnda Autograph with airSlate SignNow

Add mnda autograph

[Music] in this walk-through video we're going to take a look at how you can streamline and automate your request for nda approval workflow using nintex workflow cloud requests for non-disclosure agreements are one of the most common workflows in business and if you'd like to check out the easy to use template in the ntx process accelerator gallery go ahead and go to gallery.nintex.com navigate to workflows nintex workflow cloud and then look for our mutual non-disclosure mnda request workflow while you can import this workflow directly from the nintex process accelerator gallery into your nintex workflow cloud tenant today we're going to go ahead and look at how you can make this workflow from scratch the first step in automating this process is actually going to be designing our form to do this we'll go ahead and select our start event and then select form and here in our configuration panel we're actually going to update this to give access to anyone with the form url this way they do not need to be an authenticated user within our nwc tenant to access the form and submit the request then we'll go ahead and select design form and this will open the nintex workflow cloud forms designer the first control that we're going to go ahead and add to our form is a label that we'll use to house our title because the label control allows for rich text we can then go ahead and change our font format from a normal into a heading let's go ahead and try this one that's a little bit too big let's go ahead and see if we can try one that's a little bit smaller okay i think that looks a lot better next what we're going to do is we'll actually drag on two different group controls the group control allows you to nest other form controls within them to make more logical grouping of controls within your form designer this first group will house a bunch of controls related to our contact information of the user that is submitting this request we'll go ahead and we'll update the group name and then we'll go ahead and set this show header to yes and provide a header for the group the second group of controls is going to be all about the agreement information so let's go ahead and update our group name and header within our contact information we want to be able to provide a first name last name and email our first name and last name will be done using the text shortcontrols and then there is a dedicated email control for capturing email addresses we also want to capture the company name who's submitting this request so we'll use a text short for that as well then we'll go ahead and go through and rename our controls so they have more logical titles and you'll notice that as the control titles are updated the names will automatically be updated also these name values will then be seen as start variables within the workflow for use later we also want to make sure that all of this information is required as it will be necessary later in our process now if we wanted to provide the user with a little bit more assistance we can also provide placeholder text in each one of these fields so that the end user knows exactly how we want the data formatted let's go ahead and add that now next for our agreement information we actually want to add a start date or a date time control and then we'll add a choice control that will specify what our relationship type is going to be and finally we actually want to add one more text short control that will be the open text field if the relation type is set to other let's go ahead and we'll update our control names in our desired agreement start date we will go ahead and restrict past dates as agreements should only start either today or in the future and then we'll go ahead and we'll update our choice control so that it's not radio buttons but instead is a drop down list with the please select option enabled now with our final field of relationship type other we only want this to show when relationship type is set to other so how do we do this well to hide or show fields on nintex forms we will use rules so let's go ahead and take a look at how we can configure a rule to hide or show the relationship type other field on our form within the rules tab we'll go ahead and select add new next to form rules and then we'll give this rule a name of show relationship type other and rules within nintex forms are really designed as a if and then a then outcome so in this case we'll say if relationship type is equal to other then we want our relationship type other to be visible and required else we want our relationship type other to not be visible and not be required with the rule complete now when we go and preview the form this time when we select the relationship type of other the field appears and when we change it back to something else the field disappears and with that we've now completed the design of our request form so let's go ahead and we'll apply changes and start working on building our workflow the first action that we're going to add to our workflow is our generate document action this will be used to take the information provided in the start form and generate our nda document you can find it in the template description within the gallery template in this particular example we're going to use our box connector and i already have a connection established however if you'd like to add a new one you can do so from within the workflow designer we'll then go ahead and populate the path to where our template is held and then we'll configure the output file name and where we want that file to be stored once it has been generated the final step of configuring the generate document action will be storing the paths where this document has been held within the store path section we'll go ahead and create a new collection variable that will store all of the urls this has to be a collection because there can be multiple files or multiple outputs that are stored because of this the next action that we'll use in our workflow is a get item from collection action which will then extract out the url that we are looking for for our single document and if you're wondering why we selected an index of 0 instead of an index of one is because collections start with a counter of zero and so the first item in the collection actually has an index of zero instead of one now that we've generated our document with the information collected from our start form we actually want to send this out for signature using nintex sign powered by adobe sign to do this we'll use our git signature action we'll then go ahead and configure our git signature action with the information that was collected in our start form we'll give them the recipient role of signer and the recipient identity authentication of email we'll give it the agreement name of company name space mnda then let's go ahead and add a message and in this case i'm just going to say hi first name please sign the attached document a copy of which will be kept on file for you finally we need to actually grab our document in this case because it was actually stored within a box file we're going to go ahead and select other connector and then we'll go ahead and provide the path that we got from our collection and finally as an output we'll go ahead and grab our agreement id with the get signature action configured we now need to configure the outcomes based on what the user ends up doing in this case we'll go ahead and configure a send an email action for our expired completed and aborted outcomes and then we'll do a store signed document within the completed branch with our expired and aborted emails configured we'll go ahead and store the signed document using our store signed documents action from nintexsign in here we'll go ahead and select our connection we'll pass it the agreement id and then we are going to store this document back into box and this time we actually have a specific path where we'll store our signed documents we again want to get our file paths and so we will reuse the same variable that we used earlier we can then copy the get file path that we used earlier as the reference will be the same even though the data held inside the variables will be different we'll then go ahead and use the get a file action that is connected to box so that we can get that signed document and store it into a workflow variable and then finally we can actually send our completed email with that signed document as an attachment lastly let's go ahead and we'll update these send in email titles so they are a little bit more logical and with that we will have completed our mnda workflow using nintex workflow cloud we hope this walkthrough has been helpful in your workflow development process and we can't wait to see what you build next [Music]