Skip navigation
All Places > Nintex Product Blog
1 2 3 4 Previous Next

Nintex Product Blog

50 posts

In the world of digitalisation and mobile transformation, the question “Do you have an app for this?” is one employers hear from their employees quite often. Mostly the answer is “no” because building customised apps with corporate branding seems to be time- and resource-consuming. Did you know that Nintex App Studio provides a simple and fast way to create an app which perfectly matches your corporate identity and corporate design? No? Than have a look on the cool feature of picking colour schemes.
By default, our Nintex colour scheme is the starting point when designing your company-branded app. But it doesn't have to stay like that. First, you can choose among many pre-designed colour schemes to start creating your corporate design.

Second, it is easy to adapt the colours by using the hex colour codes of your company colours to get a perfect match.

This is how it works:

  • Log in to Nintex App Studio
  • Start to create an app
  • Go to Step 3, "Theme," on the left navigation
  • Select “Customise” as your colour scheme
  • Create your custom colour scheme by adapting following sections:
    • Highlight colour: Changes the colours of the tab bar, selections, buttons, switches and headings.
    • Background colour: Changes the background colour of the app.
    • User interface colour: Changes the colour of the text, labels and icons.
    • Field and modal colour: Changes the background colour of the input fields
    • Text input colour: Changes the colour of the body, label and icon text.
  • Watch the preview on the right side until you are happy with your customisation.

The best thing about it is that after you are finished, the app automatically generates more than 27 colours and shades to make your app look good. All the icons also change colour dynamically, depending on the choices you've made, but if you use custom form icons, you may need to check these.


Useful Tips for dealing with the power of the colours:


  1. Avoid neon colours in text or background – your users' eyes will thank you for it.
  2. Don’t use light text colours on a light background or vice versa; lack of contrast makes it hard to read.
  3. Avoid using colors that clash, such as red and green.
  4. Don’t mix too many colours – best practice would be a maximum of two.
  5. Consider where your app is being used and choose colors accordingly; for example, if it will be used outdoors frequently, a darker theme may work better.


Try it out yourself and design your own branded app.

With Salesforce users increasingly switching over to Salesforce Files in lieu of Notes & Attachments, we want to make sure that you are aware of all the ways you can leverage Salesforce Files within Nintex Drawloop. Here are some of the most useful 

  • Storing generated documents to Salesforce Files, instead of Notes & Attachments
  • Including Salesforce Files as additional attachments
  • Using Salesforce Files for document templates


Here is a brief description of each of these capabilities: 


Store generated documents to Salesforce Files  

To store generated documents to Salesforce Files, first navigate to the Drawloop Admin tab, then select the “Settings” page under “Configuration” 

On the Settings page, under “Attachment Settings” you can select “Salesforce Attachments” as your preferred storage location in Nintex Drawloop. This setting will apply to all delivery options that have an Attach Option enabled, with “Store as Attachment” configured 


Include Salesforce Files as additional attachments 

To include Salesforce Files as additional attachments, you must be on package version 12.2.3 or higher. If you have “Allow Attachments” enabled for your document package, your users will be able to select any Salesforce Files uploaded to the Record that they are generating documents from. 


Use Salesforce Files for document templates

Using Salesforce Files as document templates will require some setup with Libraries in your org. The first step requires you to be in Classic, as there is no ability to create new Libraries in Lightning at this time. 

  1. Navigate to All Tabs > Libraries
  2. Create a new Library with anname you like; in this example, we have named it “Document Templates” 



  1. Now switch to Lightning and then navigate to Files from the App Launcher
  2. Select “Libraries” in the left navigation pane, and then select the Library you created in step 2



  1. Once inside your library, you can click the “Add File” button, which will allow you to select any Salesforce File to add to the Library 



  1. Navigate to the document package for which you want to use the Salesforce File as your document template 
  2. To select the document template files for your document package, first select “Salesforce Content Libraries” and then select the Library you created in Step 2. You can then select the files within that library to use as your document package templates. 



Take advantage of all this great functionality by getting the latest version of Nintex Drawloop today from Salesforce AppExchange! 

What is a Workflow Constant? This is a feature available only in Nintex Workflow for SharePoint (on premises) that allows you to store globally used workflow variables in a single place. These variables can then be used across all web applications and site collections in your SharePoint Farm, or just within a single site , depending on the level at which the constant was created.


Why are they so useful? There are numerous ways in which Workflow Constants can be used. These include saving user credentials for authentication in actions, setting thresholds for approvals, or saving specific dates that are important for your company operational processes. There are many more, generally related to “dictionary” purposes. Broadly speaking, you can define a metadata item in a single place and manage it from there but use it across your workflows. You also can define who has permissions to use your Workflow Constants and whether they are sensitive or not (i.e. whether the workflow can discover their value).



To dive a bit deeper, there are three levels at which you can create Workflow Constant:

  1. Farm level (available only via SharePoint Central Administration: {CA-URL}/_layouts/15/NintexWorkflow/ManageCredentials.aspx?scope=farm&src=/_admin/NintexWorkflow/Management.aspx),
  2. Site level ({SP-URL}/_layouts/15/NintexWorkflow/ManageCredentials.aspx?Scope=Site),
  3. Web level ({SP-URL}/_layouts/15/NintexWorkflow/ManageCredentials.aspx?Scope=Web)


You can choose among five types:

  1. String
  2. Number
  3. Date
  4. Credential
  5. Secure string


It is also possible to mark a constant as “sensitive” (so its contents won't be displayed, for example when logging to workflow history). The “Credential” and “Secure String” constants are “sensitive” by default. Each can be set to be available to everyone or to a specific user or group.

Would you like to find out how to migrate Workflow Constants to Office 365? Read it here: Migrating Workflow Constants from On-prem to Online.

We'd love to hear your thoughts and approach for working with Workflow Constants after moving from on premise to Office 365.

Are you a hoarder?  Try collecting files with Nintex Workflow Cloud

It’s one thing to handle a single file in a workflow.  But it’s a completely different thing to have a collection of files.  The collection variable in Nintex Workflow Cloud now supports the concept of having multiple files inside it.

Think of a scenario where you are dealing with an internal user or external vendor and they upload some files to Box. Maybe you run a real estate agency and an agent takes some photos of a property that will be put on the market.


Once agents upload the files, they can fill in a form where they select the city, and enter some details about the property.


The workflow will start on submission and will then query a content management system such as Box; find the appropriate files; get them and store them in a File Collection; and then use a task action, such as Express Approval or Assign a Task to send the files to a graphic artist to clean up.

Both actions now support Attachments where you can insert the file Collection variable.

No longer do you need to assign tasks with links to files that responders have to open in another tab in the browser, or go hunting for it.  Now you can attach them directly to the task email.


This the next big leap for intelligent business processes.


Note: in the workflow above, I get every document in a specific folder in Box.  You’d most likely want to extend this process as what I have built is quite simple.  You’ll probably want to move the files after the workflow completes.

Also, you may even build in logic into your workflow to look at the file name and only support specific file extensions.  Only then would you add them to your collection.


Did you know Nintex has partnered with Box? See the new Box native app: What's New: Nintex Workflow for Box Native App 

As if task response isn't easy enough, the boffins in the Nintex Mobile product basement just made things even easier. 


Many tasks will require you to read a lot of context to make a decision, and that's perfectly fine. It makes sense to know exactly what you're approving/rejecting/passing for more information and so on. 


But there are those simple, to the point, quick requests. 1 liners with a simple outcome.

  • Have you reviewed this?
  • Is action required?
  • Will you marry me?
  • Are you going to eat that?

You get the picture. 


I'm not suggesting anyone use Nintex Mobile to propose to a loved one, but let's see how we can use Easy Task Approval to ask and answer a simple request via Workflow.


The example I'll use is a task assigned to a Manager to confirm they have carried out an employee review. 


We'll need a workflow with an Assign Flexi Task action in there. And what we'll be most interested in here is the Task Name section. We need to make this as intuitive and simple to understand.



'Workflow Task' doesn't really help my end user make a quick decision here so we need to change that up, and I'll use the Insert Reference in Task Name to make that easier. 

Let's also make sure the Outcomes make sense here, these will be my Easy Approval options.

Looks good. My task is set up and we can see the functionality in action below - 

I'm using Nintex Mobile here from the Google Play Store but this functionality is also available in Nintex App Studio built apps as well. Attached below are screenshots of the functionality in iOS.

By Chris Ellis, Nintex Technical Evangelist


I've been asked this one quite a lot, and I know there are a number of workarounds on the subject, but Lazy Approval and capturing comments through email go together like ... bananas and Vegemite! Ain't nobody got time for that -- until now...


First things first. What's new? Well, the workflow boffins -- Roanna Gunaratnam, that's you! -- have added some slick new functionality in Nintex Workflow tasks.



1 Workflow

1 Task action ("Assign a task" or "Start a task" will do just fine)

A generous measure of Lazy Approval activated on your environment



  1. Drag-and-drop the task action of your choice to the workflow above.
  2. You'll want to configure it with a few outcomes (these become handy buttons in your Actionable Message). 
  3. Go ahead and tick that Allow LazyApproval checkbox. You'll see a new option: Delivery Method.

  4. This is the new configuration for Actionable Messages and we have a number of options here: 
    1. Email Only - Still want LazyApproval  but no Actionable Message? This is the option for you.
    2. Email with Actionable Message - All the initial email text with the Actionable Messages window atop, you got it.
    3. Actionable Message only - this does exactly what it says All the Actionable Message, none of the Initial Email text.
  5. You might also notice, snuck in down at the bottom, a Task ID variable option. If you want to Query List the Workflow Tasks list and pull back the Comments value based on the Task ID, you'll need this.
  6. Save that, we're done here. 


The Sizzle

My example is a hazard-reporting workflow, which will initiate a task to the Health, Safety and Environment Department based on a risk matrix. If it's deemed Low Risk, a task gets kicked off to investigate and take action if required.

The email received by my HSE Dept, with Actionable Message configured, is shown below. The Actionable Message is highlighted in red: 

In this instance, the hazard was investigated but no action was required. So let's fill that in and select No action required.


The response and comments are captured and updated in the Workflow Tasks list for that Task. You can then Query List based on the Task ID if you need the Comments pulled back into a response email for the initiator, for instance. 


(This is available now for Nintex Workflow for Office 365)



Please note:

You need to have Outlook 2016: Version 17.10 (Build 8210.2193) or Outlook for Office 365 as a minimum version for Actionable Messages to be supported

Actionable messages aren't available in Conversational View on Outlook



We’re excited to announce our new partnership with Box, the leader in Cloud Content Management, to further drive productivity and intelligent process automation for our joint customers.


Before the Box partnership, customers have been able to initiate workflows by uploading files, and the workflow can take actions such as routing the files for approval, moving them within Box, sending them to an e-signature provider, or storing the files in a CRM. We have empowered Box users to move beyond file sharing into workflow and content automation.


Today we’re introducing a ton of new functionality in a native app called Nintex Workflow for Box. In addition to the current capabilities, it is now possible to create workflows that can be selectively started from within the Box user interface and view Nintex workflow activity on the files within Box.


We understand that people need to collaborate and work on files in an organic and fluid way where comments and edits are being done to produce the asset. The Box platform is excellent in allowing users to do this. In such scenarios, starting a review process on the file is a specific step in which the user determines when a file is ready to be reviewed.


In preparing today’s announcement, we used Box to collaborate on the marketing brochure. Several of us were updating the file, adding content, images, etc. When we finished, we could manually start the review process to get it approved, and, once approved, the workflow moved it to a “Ready for Print” folder. Through the Nintex Workflow for Box app, we could determine when the process was ready to be started. This allowed the organic and fluid approach to creating the asset and gave us a consistent and governed way to get the asset approved and ready for the next part of the process.


Manually invoke workflows from within the Box


We also can track the workflow activity on the file to determine where the approval process is. We've also extended the capability of the Box Connector so you can now set an Enterprise Metadata template on the file within your workflow design. We'll share more about this in a future blog post.



View workflow activity on the file


If you already use Box and Nintex Workflow Cloud, you can add the Nintex Workflow for Box app, provide the name of your tenancy, and log in with your credentials. If you're new to Nintex Workflow Cloud, sign up for a trial.


For more help, go to how to install the Nintex Workflow for Box app and how to design workflows for


This post is the first in a series highlighting new Nintex and Box capabilities to make content collaboration and process automation easier. Stay tuned for feature updates and scenarios that enable sophisticated workflow, forms, document generation, and more with Nintex Workflow for Box.

By Thomas Clark, Nintex Technical Evangelist

Querying your workflow tasks just became easier in Office 365!


We have added the ability to output task IDs directly to a variable on our Start a Task Process and Assign a Task actions for Nintex Workflow for Office 365. This includes support for multiple tasks.


The ability to output the Task ID of any task associated with a workflow has been available in Nintex for SharePoint and is now available in Nintex for Office 365. It allows users to easily query and work with information users submit via task forms. 


This can include information such as:


   • Comments
   • Who replied with what response?
   • Task due date vs. date of reporting
   • Status of task responses after or before task completion
   • Audit trails for detecting non-compliance


Task ID


When configuring the action, you can output a collection of the task IDs generated by the Start a Task Process action. With this you can collate and store all comments, responses and feedback. Ultimately this means you can easily audit who did what within the task process.


Let’s take a look at the most common use case, which @Jon Hardy wrote about in this earlier blog post:


How to get Task Comments and more in Nintex Workflow for 365 


In the post, Jon outlines the use case for pulling information from any of your associated workflow tasks. He walks through the difficulties of handling multiple tasks and multiple variables when the Task ID is not immediately available. This is important because many users wish to capture the comments of multiple respondents, including who responded and when.


As Jon writes:


" 'Start a Task Processassigns tasks to multiple respondents and tracks their responses to their tasks. When sufficient respondents have replied to give an outcome (as specified in the task settings), then it will proceed down the respective outcome branch.”


Previously, you had to go through several steps to identify all associated tasks and ensure they had unique names in order to query them. Now, you can utilize the "Task IDs" functionality to store all Task IDs associated with an individual task. This will save significant amounts of development time within the workflow and allow you to utilize information submitted to the task list immediately, making it available for presenting to users, capturing for records, and management or audit review.


ID Option


You can take the collection of IDs that was output by the task and use Query List & For Each to check against each associated task in the collection.

Querying the task list


The task list is a list in Nintex for Office 365 that can be queried using the Query List action. In this example, we have the set of Task IDs to easily identify the correct tasks.

The first step I want to illustrate is to loop through the collection of IDs with a 
For Each and output the task IDs to my ID Variable.


For Each


In the query, we can return any of the columns in the task list of interest, such as Assigned to, Modified by, Comments, Completed, Due date, Outcome, etc.


The Query criterion is then:

ID is equal to {Variable:ID}


You can output the results directly to text variables, or bundle the results together in further collections for processing later within the workflow.



Tips & Resources: 


Note 1: To maintain query performance you may wish to create a dedicated task list for this workflow.


Note 2:  Although you can query for the Task ID using this method, it may not be reliable to write to the task list, for example to update a task. The workflow engine may lock the record, causing writing to the list to fail and possibly causing the workflow to terminate. This is because the SharePoint task engine is orchestrating task list updates and will lock the list item at any time. Attempts to write to the task list may work at times and fail at others, depending on the timing of competing task list updates from the SharePoint task engine.


More on using the Query List:   'Query List' Release Blog
More on working with Collections:      'Collections' in Office 365 Blog
Working with 'Collection Variables'
About 'Collection Variables'
More on querying For Each item in the collection:  'For Each' Blog 

Nintex Drawloop has been Lightning Ready! for quite some time. As of our July release (version 14) Drawloop Admins no longer have to switch to classic in order to create, modify, and migrate Drawloop Document Packages.


You can create a new document package by navigating to Drawloop Document Packages inside of Salesforce and clicking on the ‘New’ button. This will redirect you to the Document Package Wizard:


Document Package Wizard

The document package wizard takes you step by step through creating a document package. Starting with the basics like giving your Document Package a name and giving users access to the document package in the set security section.


Document Package Wizard Field Tagger


One of the last steps you go through in the wizard is actually tagging the document package. Here you can decide what type of template you are using, lookup a record, and then tag your document with the fields you want to be merged in when generating a document. Lastly, you’ll upload the document and you’ll be redirected to the Document Package screen with all of your configuration displayed to you.


Document Package Detail Page


There are a couple of items to note when working with our legacy Document Package interface in Lightning:

  1. You can’t create a new component group from the Drawloop Document Packages object in Lightning. To workaround this create a new component group from the Drawloop Component Group object, then link it to a Document Package from the Component Groups related list.
  2. You have to click the play button to access the Select Files user interface. Do this each time you open a Document Package in Lightning.


Take advantage of all this new functionality by getting the latest version of Nintex Drawloop today from Salesforce AppExchange!

In my previous blog Azure AD actions land to power up your workflows I introduced our new Azure AD connector actions which provide the capability to query and retrieve user and manager information for Azure AD..


Now I'm sure many of you looked at these actions and thought awesome but quickly realized you didn't have the right level of permission to create a connection against your organizational AD instance - well now you can! 


By following the steps you can create your own private Azure AD instance, it's simple and best of all it's completely free plus you'll have full admin rights (keep reading to find out why this is important  ).


  1. Go to the Microsoft Azure portal and sign-in, you can use an existing account (commonly one with an Office 365 subscription) or you can create a free one here.
  2. After signing in the top left click '+ New' and search for Azure Active Directory
  3. Click Create and enter a Organization Name and Initial domain name (you can just make up these values). The domain name is what you'll use when creating the connection in Workflow Cloud. 
  4. Once the value is validated with green ticks, click 'Create'
  5. Add a new global admin user (advised) - this allows you to have an admin account on the same domain, otherwise it will be the account you used to sign-in with which will be different. 
    • In the left menu select 'Azure Active Directory'
    • Click 'User and Groups' and choose 'All Users'
    • Click '+New User' and enter valid details
    • Select 'Directory Role' and choose Global administrator
    • Click 'Ok' and 'Create'
  6. In Nintex Workflow Cloud create a new Azure Active Directory connection and sign-in with the newly created admin account


Now you are good to go with trialing the new Azure AD actions!


But wait we have more AD actions!

In my previous post I mentioned we were busy building out some additional AD actions, so I'm happy to say they are now ready for anyone who wants to preview. These actions are more focused on admin functions such as creating users, updating users, disable/enable users and assigning someone a manager. 


If you are interested in previewing the actions you can fill out the preview form by clicking here and we will activate the actions in your tenant as soon we can (you will be notified)..  Once enabled you will only be able to use the actions by creating a connection that has been given Admin consent by an AD Admin (refer previous post), in many cases this won't be possible for security reasons which is why using the above method of creating your own instance is a good way to test them out.


Important note - as mentioned these actions are focused on admin type functions so it's very important to understand that once you create the connection anyone in the tenant will be able to use them e.g. someone could create a user in your Active Directory. So by signing up for the preview you understand and accept this risk.


As always love to hear any feedback..

Over the last two years, we've made a big investment in bringing the Nintex Workflow Platform and its services into regional data centers near you.


Why should you care? For two main reasons: data sovereignty and latency. Let me elaborate a little.


Data sovereignty is the concept that digital information is subject to the laws of the country or union in which it is located. For example, most European customers require, by law or company policy, that any data stored in the cloud must be kept within the European Union. Similar regulations exist in other countries and political or economic unions. This is even more complicated when it comes to personal data.


Latency is the time between a request (e.g. you opening a Nintex Form) and the Nintex cloud service’s response (e.g. the Nintex Form being fully loaded and rendered). Naturally you want latency to be as low as possible to ensure great user experience.

Remember the days when you were waiting for a site to load over a 56K modem? That's exactly what we don't want. The closer your Microsoft Office 365 tenant is located to the Nintex cloud infrastructure, the shorter the latency will be and the faster things will load or execute.



Localizing our services made sense for both goals -- helping our customers and partners comply with regulations when moving to the cloud, and providing low latency for great performance.


Over the last two years we regionalized most of our services, establishing data centers in;

  • West US - California
  • Japan West - Tokyo, Saitama
  • Northern Europe - Ireland and
  • Australia Southeast - Victoria.


The Nintex Workflow Platform consists of different services and products, most of them cloud-hosted. They include Nintex for Office 365, Nintex Hawkeye and Nintex AppStudio. To see where each service or product is hosted, go to You'll not only find the service locations, it is also a great spot to find out about any service disruptions.


If you want to know where your Nintex for Office 365 service is being hosted, jump to your Nintex for Office 365 Workflow or Forms designer, and click on Information -> About. The pop-up will show you which Nintex for Office 365 region you are using. If you want to change region and migrate to a data center near you, get in touch with your Nintex partner or sales representative.



It is important to understand that most services within the Nintex Workflow Platform are transactional, meaning that data is not get stored permanently. Data either passes through Nintex cloud services to a third party application (for example, a workflow publishes content to Facebook) or it is processed and then deleted from the Nintex cloud service, as when  you create a contract using Nintex Document Generation. The exception is Nintex Hawkeye, which not only processes data but permanently stores it.


This post is the first in a short series focused on Nintex Hawkeye. I am to run a session at Nintex Xchange, our annual customer and partner conference (Feb. 26-28 in San Diego CA) to help you understand Nintex Hawkeye's architecture, information flow and storage. Keep an eye out for a few more posts leading up to Nintex Xchange. If there is anything in particular that you want me to address in my session please comment below and I will aim to include it.


I look forward to seeing you all at Nintex Xchange -- there is still time to register!


Visit the Hawkeye How-To page to see how to connect your data and get started!

Traveling home the other day after a great Microsoft Ignite conference in Orlando, I couldn’t help but think about all the conversations we had with current and prospective customers. I particularly appreciated the length of these discussions. This was the first time I can remember having so many demo conversations last 30-40 minutes and span so many different workflow automation topics. Conversations seemed to fly by as we discussed various aspects of the platform. Customers were really impressed with all of the enhancements we've made to Nintex Workflow Cloud, especially in Release 31, which landed Sept. 20, 2017. It's a testament to both the evolution and the maturity of the platform that we faced a welcome challenge -- how to quickly show off all the great new stuff without sending people into workflow automation shock!


I’m proud of what our team has accomplished since our launch last year. The offering continues to evolve quickly and provide a powerful automation platform to our 7,000+ customers worldwide. The latest release includes so much innovation that I wanted to take a moment to quickly highlight a few key areas. 



Forms have long been a key component of the Nintex product suite. They trigger just about every imaginable business process, so you really can't think about workflow automation without considering forms. Our forms offering took a huge step forward not long ago with the availability of Nintex Forms for Nintex Workflow Cloud. Nintex Workflow Cloud now makes it really convenient to design and connect a form to a process from directly inside the workflow designer, which in turn makes it super easy to utilize form data within the workflow. Customers also can easily choose between an anonymous form submission or select a more secure access point through the Nintex Mobile app.



Nintex forms are also responsive and provide the ability to custom-brand and embed the form into web pages or mobile application using a variety of new form controls, including images, headings, date/time, text, single choice, multi-choice, yes/no, and number.


Note: With the introduction of Forms for Nintex Workflow Cloud, workflows built with the legacy Public web forms or Nintex Mobile start events will continue to run, and will remain editable. Due the improvement with Forms for Nintex Workflow Cloud and a more elegant way to include a mobile experience we have deprecated these as options, and they will no longer be available to select from as start events when creating new workflows. 


Document Generation

If you're not familiar with it, Nintex Document Generation is quite powerful. It intelligently automates the creation of data-driven documents using Salesforce, SharePoint or Office 365 at the click of a button. New features here include:


  • Support for multiple templates
  • Conditional inclusion of templates, merge types 
  • Support for multiple file output formats 



Many processes involve the assignment and management of tasks or work that needs to be done. New features here include:


  • Enabled a new workflow design action called “Assign a Task.” This action provides designers with a single outcome task to utilize within their workflow. 
  • Made task outcomes more intuitive by moving the task outcomes field to the outcomes section in configuration for the Express Approval action.
  • Improved the Express Approval experience by ensuring default text size and font are consistent.


File Management

Most processes involve some sort of file, whether a Word document, a spreadsheet, or a PowerPoint presentation. We've always been committed to making file management easy; now we’ve added two new features:


  • Support for the use of file collections in "Express Approval" and "Send an email" actions.  File collections provide the workflow designer a easy way to manage multiple files within a workflow.  In this case a designer could simply attach a collection of files in one step verses adding individual files. 
  • Support for the use of file collections in the "Store a File" action provided for Box, Dropbox, One Drive, Google Drive and Citrix Fileshare. 


These features drastically improve the workflow designer's ability to manage and utilize a set of files related to a process. Nintex Workflow Cloud doesn’t physically store files.  Instead we provide the ability to store files in a external repository such as Box, Dropbox, One Drive, Google Drive and Citrix Fileshare (purposely, for security and simplicity reasons). 


 New file management features include:


  • All EFSS Copy a File actions now have consistent path field "ghost text" to help insure configuration is more intuitive.
  • Copy/Move file actions now support the use of either a fully-formed path inclusive of filename/extension, or a directory path that specifies only the target folder location.



Many processes require some sort of legally binding signature.  Whether you’re approving a purchase, closing a sale, or signing an agreement, adding an e-signature step can greatly accelerate and improve a process. New e-signature features include:


  • Support for multiple recipients/signers in the Adobe "Get Signature" actions.
  • Improved action store output picker in Adobe Get Signature lets a designer capture additional output metadata.
  • Improved the DocuSign experience by exporting signed files to a collection as an output variable.


Workflow Designer

We have improved the workflow design experience by adding a small yet powerful new feature that dramatically reduces the number of clicks required. When you’re building and managing a lot of different processes and workflows, the fewer clicks the better. 

We have also simplified things so that when a particular connector has only one connection option, it is automatically selected.


Workflow as a Service

You can easily trigger a workflow from any external system or application by configuring a workflow to be started externally. That’s because a published workflow is also a REST end point.  This makes it easy to leverage the power of the Nintex Platform from mobile apps or proprietary systems.  New features here include:


  • Streamlined and simplified the workflow publish and contextual dialogs used to configure an externally started workflow.



Connecting CRM processes and data to other key systems and people across different areas of the business isn’t easy.  Nintex Workflow Cloud makes this possible for anyone regardless of their skill set. New CRM-related features include an improved user experience in Salesforce and Microsoft Dynamics when adding fields to the action configuration. Customers can now filter and add multiple fields at once.


So there you have it: Eight significant platform improvements in Release 31 of Nintex Workflow Cloud! We would love to hear any feedback or other input you might have. And if you're new to Nintex, try it free for yourself here: Nintex Workflow Cloud free 30 day trial


Ongoing release information can be found in the Nintex community.

Link to Nintex Workflow Cloud release notes

One of the most popular and widely used features of Nintex Workflow cloud is the “Express Approval” action.  The Express Approval action sends out a task via email and can accept multiple outcomes similar to the screenshot below.  This is a powerful feature as it provides workflow designers with the ability to capture a decision within a process that could result in various outcomes.  It also gives designers the ability to assign a task to anyone inside or outside a company and directs the workflow based on the task outcome or response. An example of the Express Approval action is below.


In this screenshot the Express Approval action has been configured to accept 4 different outcomes:  Reject, Approve, Contingent & Other.


Not all tasks however require a decision. In the September release (Release 31) of Nintex Workflow Cloud we made a new task action available called “Assign a Task”.  The purpose of this action is to enable a designer to assign a task that only results in one outcome.  It basically gives the designer the ability to assign a task and wait until it’s marked complete.  Here are a few scenarios where this kind of task could be used within a workflow.


  • A manufacturing scenario where a number of inspection tasks need to be completed.
  • A sales scenario where a simple follow-up needs to be completed.
  • A HR scenario where a new employee needs to complete a set of tasks in their first 30 days of employment.
  • A IT scenario where a communication needs to be sent when an software update has been scheduled. 


The Assign a Task action has a very similar configuration setup as Express Approval. The Assign a Task action only accepts one outcome. The configuration experience for both actions is almost identical. The only major difference is the number of outcomes.  This should make the use of these actions simple regardless of which one you use shown in the screenshots below.  


Assign a task action

Assign a task action configuration


Tasks are a natural by-product of any process and is an important part of Nintex Workflow Cloud.  We realize that a big part of successful automation involves the management of tasks across different people, teams and systems.  Looking ahead we are thinking about how to further improve this experience to include other features such as reminders and different kinds of mediums including SMS and forms.  What kinds of task related features would you like to see?  We would love to hear from you!


For more information on Nintex Workflow Cloud or to start a new trial click below.

Try Nintex Workflow Cloud for 30 Days - Free! 


For more information on the latest Nintex Workflow Cloud release features - Click here for Nintex Workflow Cloud release notes

Analytics is such an essential part of decision making in business today. Gone are the days of shooting from the hip and hoping an idea lands with the market/industry or even internally. The challenge for most organizations remains to be either a lack of available skills to build out dashboards to gain these analytics and make them consumable, or simply a lack of time.


In this way, Nintex Hawkeye does the heavy lifting for you with preconfigured dashboards built into your tenant to help answer particular questions about your process automated with Nintex. In minuets, you can have the insight you need to make better business decisions, without the need for a background in data science. Nintex refers to each of these as a “Lens”:


Usage Lens - Provides a view of aggregate Nintex usage across the company (or selected Nintex data sources). It helps you understand key consumption metrics regarding; user participation, task completion, and the overall return on investment Nintex delivers. Some of the questions it helps to answer are:

-        What is the extent of Nintex Workflow use across your whole organization?

-        How are people using Nintex Workflow?

-        How many Workflows have been published, and how complex are these? 

-        What ROI are we deriving from our Nintex usage



Inventory lens – This is the latest of the pre-built dashboards and set to be released before the end of the year (apply for advance preview at For IT, admins and ops teams, the Inventory Lens addresses three key areas: 

-        Governance – know where, how often, and how smoothly workflows are running.

-        Assess Expertise – understand workflow ownership and designer proficiency throughout the organization.

-        Workflow Status – discover the reach and impact of workflows, then drill into specific usage and status trends.



Process Intelligence Lens

The Process Intelligence Lens allows you to instrument and measure activities occurring within a particular process automated with the Nintex Workflow Platform. In addition to allowing customers to add relevant context and emit process-specific events to Nintex Hawkeye, the Process Intelligence Lens includes foundation process metrics (e.g. how many times the process has run and the outcomes etc...).



The best part of all of this? You can get started today. If you don’t already have Nintex Hawkeye take the free trial at

Let’s walk through a process together in Nintex Workflow for Office 365, where we will use Beacons to produce valuable data analytics that show us how our business process is performing.


Use Case:

In this example we have an automated business process for Open Enrollment. When an employee completes his/her open enrollment, they will receive an email notification. Next, we have a Flexi Task that routes to the Manager for approval. Regardless whether it is approved or rejected, the person who submitted the request receives an email notification.

Next, the task routes to HR for their decision. Regardless of approved or rejected, the person who submitted the request received an email notification.

Where Beacons come into play:

The Beginning Beacons and Ending Beacons are in the Flexi Task, both for the Manager and HR state:

Once our workflow is published, data is surfaced in Nintex Hawkeye. Initially we see the processes runtime characteristics.

However we can now do more with the help of the data submitted from employees completing the open enrollment. The beacon data is contained in the OData feed that is available in Hawkeye, which means you are able to expedite time to value by alleviating the need to build out custom queries to your data sources. Now we can plug our OData feed into any intelligence tool e.g. Power BI, Splunk, Qilk etc... (any that accept the latest OData Version 4) and leverage the power of those tools to easily create custom visualizations, all through clicks - not code. And best of all by using the custom configured beacons in the workflow we are analyzing the business data that matters to you, rather than simply workflow metrics.

As most of you know, the hardest thing with any data project, is collecting the data and getting it to a place where you can do something with it - Nintex Hawkeye helps us get there.

To learn more about the process of leveraging the OData feed surfaced in Nintex Hawkeye click here - Your Nintex Data, Your Way

Why not try this with one of your workflows today, and demonstrate back to the business, the impact you have made through process automation?