News and Guidelines

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

TopicHow to Create a case on Nintex Customer Central.InstructionsNavigate and login to Nintex Customer Central. Select Create Case on the main dashboard or select Cases on the left side navigation menu. Select Create Case to display a new case form. Fill out the case form. Enter a Subject for the case. The subject field will predict any solutions relating to the case. You can click on the link to view the Knowledge Base articles or Help Documentation. Select a Platform from the dropdown menu. Select a Product from the dropdown menu. The dropdown menu will only populate if you select a platform. Select a Severity level from the dropdown menu, to flag the type of the case. Enter case details in the Description field. Remember to provide enough information. This will give the support engineer, assigned to the case, context to provide a solution or the required information. Keep other individuals informed by entering their email address in the Cc field. Attach files using the Add Files lin

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

In this video, we are going to explore navigation and learn more about the different ways and types of badges you can earn on Nintex Community.  For more guidelines and information, see the following articles.Welcome to Nintex Community! - Nintex CommunityView your new badges and ranks! - Nintex Community

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 

Here are some useful articles for Nintex Customer Central and Nintex University: Adding and Editing Contacts in Nintex Customer Central Delegated Access to Customer Central for Partners Managing Training Seats for Nintex University

Whether you are a customer that is building solutions for your organization, or you are a partner that is delivering solutions for your customers – Nintex is committed to your success. Today we are excited to bring you even more innovative and intelligent process automation (IPA) software solutions by acquiring Kryon, a process discovery innovator and robotic process automation (RPA) leader, to further extend the IPA capabilities of the Nintex Process Platform. Kryon is Nintex’s first acquisition under its new majority investor TPG, and the company’s third acquisition in 16 months. Nintex acquired K2 Software, Inc. in October 2020 to deepen its digital process automation (DPA) capabilities and AssureSign in June 2021 to bring native eSignatures to its platform, now marketed as Nintex AssureSign®. “We are excited to welcome the Kryon team and look forward to offering Nintex customers and community members more advanced automation capabilities and automated process discovery technology w

This document demonstrates and explains how to optimally design a more complex, data-set-driven workflow in Kryon RPA. Please note: This will be presented and explained using an example (and Excel), not an actual productive workflow. The design approach and methodology still apply and can be easily adapted for data in Flat-files, databases, etc.

Our Nintex Ideas site allows you to submit new enhancement requests or vote on existing requests that add value to the Nintex Process Platform. Our Product Management regularly visits the site to check the feedback left. When creating a new enhancement request, please:Check if there is an existing enhancement request already for the feature. Votes significantly increase the weight of the enhancement request. Adding a vote and commenting on an existing feature request is the best way to raise its priority. If there are no existing feature requests for the idea: Create a brief title describing what the idea is about. Write a summary of the enhancement, the problem it solves, and what the current product does instead. Include a use case for the new feature. (i.e., when doing XYZ, this would allow the Nintex product to do ABC). Describe the impact this feature would have, for example, how much time or resources this would save. Add any additional material that could help Product Manage

Process lies at the heart of how a business operates. It’s a determining factor in a wide range of business outcomes. It affects how agile, productive and competitive your organization is. Ultimately, broken processes hit businesses' bottom lines. For organizations of all sizes, automating processes is essential to digital transformation success. How should an organization prepare for the journey to automation maturity? Learn more in Nintex’s Process Automation Maturity Model: https://resources.nintex.com/process-automation-platform/process-auto-maturity-model?utm_source=direct

! This article is out of date! Please reach out to your account manager or CSM if you are interested in running the script in your environment. The Know Your Workflow ScriptThe Nintex Know Your Workflow (KYWF) script is a handy tool provided by Nintex that allows you to get a better understanding of the workflows that are running within your SharePoint On-Prem environment. In this post we're going to review how this script can be used to not only audit where your workflow are, but also help build a Master Workflow List to help you prepare for your migration to cloud. This download will include the script itself and instructions on how the script can be run. You will run the script on one of your Web Front End SharePoint Servers that are licensed for Nintex, and script will output a zipped file with several different csv files inside. While each of these files are used for different purposes, the file that we're most interested for this exercise is the WorkflowStatistics file (which wil

 In order to update the k2 application certificate you need to do the following steps on the IIS and the k2 application, this is one way of updating the certificate as I'm sure there's others. In this approach you will be able to access both the old url "localhost" and the new one.   Prerequisite:SSL Certificate for your new DomainURL, and its added to the K2 server certificates. Login in into the K2 server as administrator or as the setup account.   Configuring the IIS:  Step 1: Open the IIS by typing IIS on the Windows search. Step 2: Expand the Sites to reach to the K2 website and select it, On the Right on the Actions section click on the Bindings.. under the Edit Site section then Click on Add.. under the Site Bindings page. Step 3: On the Add Site Binding page select the type as https then type the Host name "the new DomainURL" and select the right certificate under the SSL Certificate once all done click on OK.  Configuring the K2 Application:  Step 4: Go to Management > Auth

Our biggest event of the year, Nintex ProcessFest® 2022, is just weeks away. Registration is free and open to all Nintex customers and partners, and anyone interested in automating, digitizing and transforming work. Save the date and register now. Nintex ProcessFest® 2022 is taking place virtually over 24-hours, kicking off with a global broadcast of the keynote on Tuesday, March 1, 2022 at 12 p.m. Eastern. The agenda includes global and local sessions scheduled for various time zones to ensure participants from every region of the world may network with their peers in real-time.And we want to YOU to have a role in the event. Send your questions for Nintex CEO Eric JohnsonIf you could ask Nintex CEO Eric Johnson anything about Nintex and our technology, what would you ask? Eric wants to answer your questions and share his insights. Comment on this post with your question – or as many as you have – and give kudos to the other ones you like. Eric will answer the best and most-liked quest

Very often we have a scenario where it is difficult to upfront decide on the number of level of approvals or eye checks needed in a workflow. Have got the same request twice this week so thought of putting it down in a blog. Today I will show you on how we can achieve dynamic level of approvals straight out of the box from NWC itself without having to do any major customization. Do note, though the screenshot and references are of NWC, the same can be achieved in Nintex for SharePoint on-premise as well as Nintex for office 365. To achieve this, I have used the best friend of a workflow designer, Branch by Stage Action.In my example I have 3 parties who will evaluate the requestLegal Procurement ManagementIn the screenshot above you will see an extra stage, Decision stage. Let me explain why we need that in a while.Now while in legal stage my customer wants N-number of approvals. It can go back and forth to multiple people with different expertise. The user may also send to the request

To date in Nintex Workflow Cloud (NWC), designers and developers have had the capability to publish changes to any type of workflow. If this works for you, you can leave this setting in place...however, if your organisation insists on additional governance or demands greater visibility of when changes are being made, NWC now offers configuration options to specify who should have the ability to publish changes to workflow. Let's find out more! Your admins will find new options available on the Workflow settings page under Settings. The Workflow publishing section is where to look to begin configuring the new feature.  When you first visit this page, the Designer and Developer option will be selected under Workflow publishing. This is the status quo...how NWC has worked up until now. If you are happy with this model for publishing, you need do no more! Now let's look at the second option...Groups. Toggling the main setting to Groups allows us to add one or more groups of users who will

Update - August 20th (17.4.1 now available)Hello, RPA Community,Thanks again for your patience while we got the Google Chrome issues fixed in the latest release. Nintex Bot 17.4.1 is now available -- I strongly encourage you to install this version as soon as possible, and not only if you're targeting Chrome in your botflows.  You do NOT need to update RPA Central as long as you updated it last week. Note that we released a new Chrome Extension today as well -- 1.2.0.0. The combination of 17.4.1 and the new Chrome extension should greatly improve the speed and reliability when designing or running botflows that target Chrome. Thanks again,MikeProduct Manager - RPA Update - August 16thHi again, Everyone, We are planning on releasing 17.4.1 mid-week. Thanks again for your patience as we work through the targeting issues with Chrome and Edge. For a little more detail, some of these changes that caused the instability in our web table targeting were to support what we internally call Shado