News

The following Nintex How-To Center articles were published this week:Nintex Upgrade Center: Upgrade forms in the Assign a Task action This article steps you through how to upgrade a Nintex for Office 365 workflow to Nintex Workflow Cloud that has Assign a task action forms. Nintex Workflow Cloud: Calculate a Value action This article with video details how to use the Nintex Workflow Cloud Calculate a Value action. Nintex Workflow Cloud: Set a Variable Value action This article with video details how to use the Nintex Workflow Cloud Set a Variable Value action. Nintex Workflow Cloud: Log to Instance Details action This article with video details how to use the Nintex Workflow Cloud Log to Instance Details action.  Each Friday, a summary of newly-published Nintex How-To Center content will be posted.  If you'd like to request content, visit the Nintex How-To Center main page and click Request Content. From there, you'll be able to suggest a content idea and have other users vote on it. I

 I found that in our demo Microsoft 365 tenant, there were Nintex updates for Nintex Form and Nintex Workflow as shown:Nintex Workflow for Office 365 (Version: 1.0.4.0)Nintex Form for Office 365 (Version: 1.2.4.1)  But I got some hiccups while updating Nintex Apps for Office 365. So, let me give a step by step guide to update Nintex Apps.    Step 1 Issue: Nintex Forms for Office 365 within SharePoint Online, there is no option update from SharePoint Online StoreFollow this URL (Dated: Aug 8, 2017)Step 2: Sign in your Office 365 credentials and Nintex Form will be updated.  Step 3:Even after Nintex Form App update, it will still show, “An update for this app is available”.Next, click on Nintex Form App. Step 4:This time around you will able to get the button, GET IT as shown:Follow this URL  (Dated:  29, Feb 2016)https://community.nintex.com/docs/DOC-3493    Step 5:In few minutes, Nintex Forms and Nintex Workflow Apps will be updated. The steps may wary for different Office 365 tenants

Hi, Everyone,Today we released the latest versions of both Central and Bot. I encourage you to upgrade Central and Bot today! You will also notice that we have released an updated version of the Chrome extension which should upgrade automatically in your browser.We have added two new actions – Open Chrome and Open Edge – that should make it more reliable to open these browsers.You will see a ParseJSON function in Bot as well, making it easier to work with objects returned from REST calls.If you are using Open Data, there’s a new option to execute one or all records, so check that Help topic out if you are using Open Data actions.If you are in the banking industry and use Fiserv, you are most likely moving from IE-based automations to Google Chrome and perhaps custom applications. We have made some enhancements for you to be more successful with both, particularly Fiserv Navigator. We have also made it easy to create copies of your IE actions so that they target Chrome or Edge. Right-cl

The following Nintex How-To Center articles were published this week:Nintex Gallery: Import the Nintex Workflow Cloud Leave Request Template This article with video steps you through importing the Nintex Workflow Cloud Leave Request template from Nintex Gallery. Document transmission using SharePoint Online This article with video details Nintex AssureSign document transmission creation in SharePoint Online. Capture Process and Procedure Details This article with video shows how to capture process and procedure details in Nintex Promapp. Nintex Workflow Cloud: Upgrade Workflows from O365 This article with video is a great overview demonstration of upgrading Nintex for Office 365 workflows to Nintex Workflow Cloud.  Each week, a summary of new Nintex How-To Center content will be posted.  If you'd like to request content, visit the Nintex How-To Center main page and click Request Content. From there, you'll be able to suggest a content idea and have other users vote on it. If you have a

New workflow inventory widgetsWe've added three new widgets to the Inventory dashboard to give you a more comprehensive view of your workflow usage. The Workflow Inventory widget displays a breakdown of workflows across your Nintex platforms:Production workflows within your subscription Development workflows within your subscription Deactivated workflows in Nintex for Office 365 The Published workflows widget presents a month-on-month consumption trend of your total published workflows and a predictive trend line to predict future usage demand. The DocGen action for workflow widget displays the total execution count of document generation actions across your published workflows. If a DocGen action is used, you can track the number of times it is executed in the Workflow table.  Nintex Workflow Cloud Instance activity reportThis new report displays all activity details for a specific Nintex Workflow Cloud instance. It is useful for auditing and tracking purposes. You can download a copy

Customizing Notification Programmatically for Nintex AssureSign One of the most powerful parts of Nintex AssureSign is the fact that you can manage the entire signing process programmatically through our API. In this post I wanted to showcase how you can customize notifications when sending envelopes using the Nintex AssureSign API.  For this example we are going to be using the `submit/prepare` API endpoint to customize the envelope and notification that we wish to send. As with any interaction with the AssureSign API, the first step will be getting your authentication token. You can do this by creating an API user from within Nintex AssureSign (video link), and then using the API username and key to get your authentication token:  Submit/Prepare with custom message for default email designs Authenticate Request POST https: //account.assuresign.net/api/v3.7/authentication/apiUser Content-Type: application/json Accept: application/json { "request": { "apiUsername": "ApiUserName", "key"

What is the Process Reporting API?The Nintex Promapp® Process Reporting API exposes process health and usage data through an OData feed to enable people to build their own custom queries, making it a lot easier to see trends and report on process excellence, without having to run manual csv reports.What data is available?Process health data - refers to the publish status (in progress, published, awaiting approval, etc.) and review status of your processes. Process usage data - refers to process views. Read the API reference here: Reporting API reference. We plan to make more data available in future releases. What tools can I use to access data in the Reporting API?The Nintex Promapp® Process Reporting API uses the OData 4.0 protocol. You can use any tool that supports token-based authentication, such as Microsoft Excel and PowerBI. For more information, seeOData.org andOasis: OData Version 4.0 Protocol.Note: Tools that use forms-based authentication such as Tableau are not supported a

The Nintex Gallery provides the Nintex Workflow Cloud Leave request template, to help you quickly implement a basic request form and approval workflow combination for your organization to capture leave requests. In this video lesson, you will learn how to import this template to your Nintex Workflow Cloud environment and then make a customization that might be helpful to your process.   ResourcesNintex Gallery - Nintex Workflow Cloud Leave Request Tour the Nintex Gallery 

I recently had a requirement come up while implementing an On-Boarding Workflow. The requirement from my client was: "we want to have multiple list item attachments for the new employee process but when the workflow starts I need to have different attachments emailed to different employees". I started to think about this because there is not an action within Office 365 to get list item attachments, although there is a web service we can call to get them. I wanted to document the steps I needed to take just in case others needed to do something similar. Step 1) Build Dictionary to set the Request Headers.Drag and drop Build Dictionary action on to the canvas and Add the following Items: Below is what the action will look like when you are done.Key: Content-type Type: Text Value: application/json;odata=verbose Key: Accept Type Text Value: application/json;odata=verbose Output: RequestHeader of type DictionaryStep 2) Build URL StringUse the Build String Action to build out your Web Se

Hi, Everyone,As you may have heard, Nintex recently acquired a process discovery and RPA tool called Kryon on February 15th. You can read more about that in our press release and community post.While Kryon will be our preferred RPA platform moving forward, we will continue to support Nintex RPA long-term. The combined team is structured to maintain RPA and add features and functionality over time as needed, so I want to assure you that Nintex RPA is fully supported, and you will not need to move your scripts or botflows to Kryon. However, if you are interested in the features and more expansive scope of Nintex Kryon RPA, please reach out to your Nintex account manager. There will be more information to come but I want to assure you that all our RPA customers are very important to us, and we will continue to be here to support you.Thanks,MikeNintex RPA Product Manager

At Nintex, our goal is to provide you with the tools and knowledge you need to start automating your business processes as quickly as possible. This begins with our robust process platform suite of products that help you in the areas of process mapping, advanced workflow design, robotic process automation, document generation, electronic signature capture, forms creation, and more.  We recognize that many of your processes are unique to your organization, and require collaboration and design, specific to your requirements. However, there are many organizations that share similar process automation needs for things like new employee onboarding, invoice processing, and purchase request processing. This walk-through video will take you on a tour of the Nintex Gallery where we host various pre-built workflows and templates like these that can help you jump start your automation processes.   ResourcesNintex Workflow Cloud Leave Request Template

We have released March 2022 Cumulative Updates for K2 Five versions 5.5 and 5.4, a new April 2022 Cumulative Update for K2 blackpearl 4.7, as well as new versions of the main installers. These are all available for download on Nintex Customer Central.If you are planning to upgrade to one of these versions, please make sure you download the latest installer version as well as the applicable cumulative update.If you have K2 blackpearl 4.7, or K2 Five 5.4 or 5.5 installed, make sure you download and install the March 2022 Cumulative Update to ensure that the Microsoft Azure AD Graph API changes are up to date in your environment.As previously communicated, Microsoft has deprecated the Azure AD Graph API and is replacing it with Microsoft Graph functionality. K2 relies upon the Graph APIs to integrate with Azure Active Directory (AAD) resources, which can be used for an Identity Provider within K2 natively, or to integrate with SharePoint Online. The March/April 2022 Cumulative Updates inc

Check out what our MVP's love about Nintex!   

I came across a situation the other week where we needed to set up a document for signature by two people and we don't mind the order they sign.  The default setup with Nintex AssureSign is that person #1 signs and person #2 only gets a request to sign after that is complete. In some instances that isn't the most efficient method of communication when we don't mind what order the two people sign in.  Additionally, what happens if we have a third signer who should only be notified when the first two people have signed?  If either of the first two people decline to sign, the third person should not be notified.  We can achieve all of this by modifying the default workflow. Using a concrete example, we have someone who wants to join a club.  We'll refer to them as the Candidate.  We also have someone who is going to sponsor their membership (the Sponsor).  When the application is made, we want to send notifications to the candidate and the sponsor at the same time and when both of them ha

This question comes up fairly often, and it may seem like a no brainer but here it is any way..You have a workflow and it is calling an external web service.. Now for whatever reason the call has failed.. A 99% of the time this has nothing to do with the workflow itself, it is just the service didn't respond for any number of reasons.A trick that I have been doing for a while now is to place the web service call inside a loop along for a pause action. "But how does this help?" you ask.. Well by using the OOTB feature of capturing errors of course J Opening the "Call Web Service" action scroll to the bottom under advanced. Change the settings to "Yes" capture error, Create a "Yes/No" variable to store whether or not there was an error and then if you wish to be emailed or store the error within the WF History, create a multiline Text Variable to store the error message.In the logic of the loop conditions stay in the loop until "Error y/n" = N..Expanding on this, I have also extended thi

The Nintex How-To Center will be your new go-to source for how to get things done quickly with the Nintex Process Platform. You will start noticing changes on the Community from the 12th April. Content within the Nintex How-To Center helps bridge the gaps between the educational content contained in Nintex University, product knowledge contained in Nintex Help, and self-help content contained in Nintex Community. You will be able to access the Nintex How-To Center from the left-hand side navigation in Nintex Community:Content is tagged by product and experience level, so you can quickly sort through specific Nintex how-to content and find what you need. You will also be able to continue to use the product-specific how-to links by navigating to the left-hand size menu of Nintex Community. All product specific how-to links in the navigation will redirect you to the Nintex How-To Center. Another feature of the Nintex How-To Center is the ability for you to submit your own requests for con

Hi, Everyone,I wanted to let you know that we released an updated version of Bot today – 17.7.1 – that fixes a few issues. There’s also a new Chrome Extension that we released earlier this week, so make sure you’re already using that.Check out the release notes for detailed information.Thanks,Mike

Often you will see forms that contain List Lookup controls that draw their data from some list in Sharepoint that contains hundreds or even thousands of elements. This gives the user a less-than-friendly experience trying to find their relevant selection among all those items. Just look at that scroll bar in the following picture - this tells us that there are LOTS of item to select from...  I set out to create some functionality for filtering those items, so that only items that contained some string entered by the user, would appear. This is the effect I got after implementing the solution described in this post: These are the steps necessary to accomplish this: 1) Save the attached JavaScript file in a place from where you can reference it. I usually store my scripts under Site Assets/Scripting. For this example I have stored it as Site Assets/Scripting/NF-Utilities/NF-OptionsFilter.js. I actually use Sharepoint as my source control system, where I only let my users see the publishe

Nintex Analytics now contains full inventory visibility for Nintex Workflow Cloud and SharePoint Online forms enabling users to view all their Forms data directly in Nintex Analytics. The new forms data will allow you to identify the total number of forms published across your tenants and environments including the type of form, the exact location of the forms, as well as the number of submissions made from each form.   Those with an enterprise workflow subscription have access to Nintex Analytics for no additional charge. To get started, please reach out to your account manager or Nintex Support. 

While working on a POC for a client I had a situation where we would be creating a document from any combination of 3 document generation templates that we were using, creating a document that would be sent to AssureSign for signature. What I am going to show in this blog is how to create signature Jotblocks using embedded text tags in your templates and how to setup the AssureSign template to handle for this situation. Creating Your Template in Nintex AssureSign As we talked about in my previous post even though we are generating the document in the workflow we will still need a template in AssureSign.  In this case however we will be using embedded text tags in the generated document in order generate the signature Jotblocks for us.  So we will be configuring the AssureSign template a little differently instead of using Jotblocks on the template for each signature, we will just be placing one hidden field on the template. In this case after we add a signer all we are going to add to

You can now see the highly requested Forms data in Nintex Analytics. Nintex Analytics contains full inventory visibility for Nintex Workflow Cloud and SharePoint Online forms. It is presented as widgets in the new Inventory dashboard and the Forms table.    The new forms data will help you identify the total number of forms published across your tenants and environments. The widgets give you an overview of forms by type. The Forms table provides the exact location of your forms so you can easily locate them. You can also see the number of submissions made for each form so you can identify which are the most and least used forms. 

Hi, Everyone,I wanted to let you know that we’ve released Nintex RPA Central 2.7.1, a minor update to our release earlier this month, and Bot 17.7.0.These releases bring performance and reliability enhancements so I encourage you to move to these versions as soon as you can, especially if you’ve experienced botflows getting stuck in a queued state and bots going offline.RPA Central’s performance at the API level, which can be seen in the UI as well, is up by about 30%, while we’ve reworked the communications from Bot to Central to increase the speed as well as improve the reliability of the connection.Also new in Bot is quicker and more reliable targeting in Google Chrome and Microsoft Edge (with the new extension – 1.5.0.0 - that we released 2/22/22). The speed of boxing when targeting is 3x-4x faster. We’ve also introduced a new formula – CleanRegEx – that is much quicker at cleaning up unprintable characters in any given amount of text that you pass in.Check out the release notes fo

In our latest release of Nintex Analytics, we have made significant improvements to provide a seamless user log-in experience for both Nintex Analytics and Nintex Workflow Cloud. If you have an active Nintex Workflow Cloud (NWC) tenant, there will be no change to how you currently log in. You will simply log in to Nintex Analytics with the same NWC credentials you use today. If your organization uses a single-sign-on provider, there will be no change and you will continue to log in via SSO. For customers using Nintex for SharePoint or Nintex for Office 365, without a Nintex Workflow Cloud tenant, each user will receive an email to reset their Nintex Analytics password. For users who miss the email, there will also be a link to reset their password on the login screen. In both situations above, if any external accounts have access to your current Nintex Analytics workspace, you will need to create a new log in for them using your corporate domain. Their external domain will no longer be

Hi, RPA Community,We are happy to announce the availability of RPA Central 2.7.0.The main new feature in this release is support for multiple, trusted Active Directory domains. This means you can now add users that reside in a domain other than the domain where RPA Central is installed. For example, if you work with someone in a different branch to help you manage your Nintex RPA, you can add them to your RPA Central server even if their account is not in the same domain as yours. For more information on the necessary trust relationship, please see the help documentation located here.For those of you that had scheduled botflows running an hour earlier or later when a daylight savings change happened, please upgrade before the next time change happens. Here in the USA where I’m based, that’s on March 13th.The corresponding Nintex Bot release will be available later this month. In the meantime, feel free to upgrade your Bots (if you’ve not already done so) to 17.6.0.For the full release

Another successful release for Nintex AssureSign! New features Improved Updated Knowledge Based Authentication submission user flow. Updated the look and feel of simple setup JotBlocks. Resolved issues Resolved an issue with the import and export of classic templates when working with SFTP document transmission. Resolved an issue with hidden toggle button and required fields on JotBlocks.  Release notes: https://help.nintex.com/en-US/platform/ReleaseNotes/NintexAssureSign.htm