News

We are announcing the end of life for Nintex for SharePoint 2007 and 2010, which will take effect on September 1, 2023. In line with the Nintex Subscription Support Policy, we will offer support for these versions for a period of 24 months beyond this date. This support will consist of troubleshooting issues, identifying workarounds, and resolving critical security concerns. We are aware that most customers have already moved away from these products as they are no longer supported by Microsoft. However, if you haven't made the transition yet, Nintex provides various migration paths to simplify the process as much as possible.  Many Nintex customers are taking this opportunity to modernize and transition to the cloud, utilizing our upgrade tools, services, and support to migrate to Nintex Automation Cloud. For additional information or to begin the process, please refer to our Modernization 

Note: Nintex Workflow Cloud (NWC) is now called Nintex Automation Cloud (NAC) With the latest release of NAC, we now can modify and add custom CSS to any NAC form. Which not only enables granular control with the look and feel, but now you also have the ability to display information in a more graphical way…..like using workflow data in a bar or pie chart.   In the above screenshot, I have added custom CSS to each of the inputs, a background image (a great way to make your forms pop) and I’ve converted some html in a label to a CSS based chart. Lets look at how I put together the bar chart. First thing we need to do, is drag and drop a label control on the form and add some HTML to a label (using the HTML option). Example below: 

Purge items in a large Nintex Workflow History listIMPORTANT: This article applies to Nintex Workflow 2010,2013,2016, and 2019.If you have more than 5,000+ records in your Nintex workflow history list, you may need to review other options to purge these items as the GUI may fail its purge operation.History List Purge—Method 1: Use NWAdmin.exe -o PurgeHistoryListDataNWAdmin.exe is included as a part of your Nintex install. Here is an example using the PurgeHistoryListData:SharePoint 2013 Management ShellNWAdmin.exe –o PurgeHistoryListData -siteUrl http://yoursite.com/ -lastActivityBefore 2014-07-01 00:00 -state SELECT STATE‍‍‍‍‍‍‍‍‍‍‍‍‍‍Specify

In this month’s user spotlight blog, we’re talking to Jake Dennison (Jake), a Senior Solutions Engineer at Nintex. What is your current role, how long have you worked at Nintex, and your career background?I am a Senior Solutions Engineer. I have been at Nintex for over 4 years, but I have used Nintex for nearly 13 years through various partners and customers. I started my career as a Microsoft apprentice learning Windows Server and Operating systems but also early versions of SharePoint 2007. I worked in IT at first as a project support specialist. Still, I quickly moved into consulting on IT Service desk improvements for mostly Banks and Financial organizations focusing on IT, Cyber-crime and Financial crime. I found myself using Nintex for quite a lot of that, and over the years, I built up my Nintex and SharePoint knowledge until finally deciding to join the company I invested so

​Nintex Forms, a part of Nintex Automation Cloud, has long been a go-to solution for enterprises seeking to create and manage electronic forms, streamline workflows, and collect data efficiently. However, until now, the software's functionality was limited to its core features and was not expandable. Enter the Nintex Forms plugin feature, which will revolutionize how users create interactive forms interfaces. So, what are plugins in

Workflows can fail for a variety of reasons, anything from communication issues with external systems, incorrect data, workflow logic, all the way through to unexpected workflow engine failures. However, regardless of the reason for the failure, the most critical factor is that when it happens, someone is notified, and the cause is identified. In Nintex for Office 365, we fully understand that identifying when a workflow terminates or suspends has been extremely challenging due to the lack of any kind of notification or indication that something went wrong. There are numerous factors as to why we’ve not been able to provide this capability; however, let’s not dwell on the past. The Nintex team is extremely excited to announce the introduction of Workflow failure notifications, which, as the name suggests, is the ability to configure workflows to send email notifications when it fails! I’m sure after reading tha

Applies to: Nintex Forms for Office 365, Nintex Forms for SharePoint 2010, 2013, and 2016 As a forms designer, you can add a signature control into a form for a signature capture that is delivered to Nintex Mobile app using the Multi Line Text Box control and custom JavaScript. The person filling out the form can write their signature as proof of a transaction when the signature capture is active in the app. Note: The signature control is available for Nintex Mobile only. To add a signature capturePrepare the signature catpure layout as follows: From the Forms Controls toolbox, drag and drop the Multi Line Textbox control onto the layout. Double-click the control. The control settings dialog box appears. For Name, enter Signature. Save your changes. Copy the script in the attached file to the clipboard. F

You’re missing out! Get Salesforce Lightning experience, integrated eSign and workflow, scheduled doc gen, mass send, and much moreAre you running an older version of Nintex DocGen (formerly Drawloop)? If so, you’re missing out on these exciting new features:Salesforce Lightning Experience for DocGen Designer including managing DocGen Package templates Integration with Nintex eSign, Nintex Automation Cloud (formerly Nintex Workflow Cloud) and Salesforce Flow Schedule your document generation Mass/Batch Document Generation available in Lightning Simplified Button creation without Javascript (for mass/scheduled packages) SharePoint Online/Office 365 Support - Ability to view, edit, delete, and add New DocGen Package templates from SharePoint Online/Office 365

In early 2020 Nintex Promapp is introducing Checklists, a new feature to tie the activities of a process together by connecting the people responsible at every step, and providing greater visibility and accountability for the handovers between activities. With checklists, each activity relates to an individual responsible to give full accountability, and they’re notified when their role comes into play. They also have all the process information at their fingertips to ensure easy compliance. As they complete the work required, their signoff is recorded in the checklist for tracking purposes and the records of completed checklists provide a picture of the process execution for ongoing improvement. From any process, users simply select the ‘Checklists’ tab and click the button to create a checklist that follows the process steps. The checklist is automatically named with the process name and time and date of creation but can be customised to suit. The user then assigns e

Hello, Today I am going to explain how you can add a simple state machine design to allow a workflow to resume where it left off after a failure or perhaps a re-open request, this can be used with both the restart instance capability with the instance manager and manually restarting the workflow via an external source. The only requirement for this to work is to have a place to store the workflow data, in my example I am using SharePoint but you can just as easily use Salesforce or even SQL. The start event:It is not important what the start event is as you want to build the workflow to be re-usable by design. if you do however want to restart the workflow from a target system then you will only be able to use a start event that can begin based on a connector and configure to start when an item is new/update. Otherwise you will be restricted to only being able to resume the instance using t

We’re excited to announce the release of a new forms designer within the Nintex Process Platform. Now users across Office 365 and Nintex Workflow Cloud can design forms using the same easy-to-use yet powerful and flexible designer to create forms. This is a completely new forms designer – built from the ground up and focused on performance, usability, and flexibility. This will be our new engine going forward for Nintex Workflow Cloud, Office365, and SharePoint. So, what’s new: Clean modern UI  Improved geolocation control that supports Google Maps API on the web Native signature control that works across web and mobile and stores an image of the signature  Barcode scanner is now available in the toolbox for use in Nintex Mobile  Rules improvements Set the property of any control on the form (Including value)  Set the properties of multiple controls in one rule Easily

In order to reduce vulnerabilities and ensure your K2 solutions are secure, we have been working on updating all jQuery libraries used in the K2 platform, both runtime and design time. The jQuery version used in Nintex Automation (formerly known as K2 Five) and Nintex K2 Cloud has been upgraded to jQuery 3.7 and all jQuery libraries updated to reduce vulnerabilities and ensure your solutions are secure. All out of the box usage has been updated to mitigate security vulnerabilities and refactored to remove deprecated components and maximize compatibility with this jQuery version.    To minimize upgrade and backwards compatibility concerns with any custom controls or extensions created by customers or partners, we are releasing this work in stages.  In this first phase, we will release our updates alongside the jQuery migrate plugin. This will allow you to test your solutions and see any warnings in the browser console to help you see where you will need to replace your

Business Owner Role Ever have users in your organization that need to have oversight into a workflow or workflows?  With the addition of the Business Owner role you can assign those users to a workflow/s that they need to be able to monitor, track and have insight into.  This will allow them to see the My Nintex Activity feed, start and task forms submissions and all active and completed tasks for those workflows.  Granting Users the Business Owner Role Here is how we to assign those users to the Business Owner role for the workflow/s they need to have oversight of. From the automate section of Nintex Workflow Cloud find the workflow you want to add the user to, click on the ellipses to the right of the workflow and select permissions.  

We're well aware that many of you have been looking for workflow restart / resubmit functionality in NWC...and I'm pleased to introduce you to the new workflow resubmit feature that has just gone live! There are two primary use cases for this function: Restarting a workflow that has previously failed - perhaps there was an issue with a connection or the logic in a version of the workflow Restarting the workflow for an item that previously completed normally.In this post we'll take a look at how different roles will be able to access this function, and what they'll see once it has been used. Let's first consider the experience that a workflow designer might have - the scenario might be that we had a problem with actions using a connection in the workflow and many workflows have Failed status as a result. While users can resubmit their own workflows, we're going to do it on their behalf. 

Nintex eSign version 7.11 is now available, providing customers with these exciting enhancements, updates and resolved issues:Bulk Send EnhancementsNow includes error message for duplicate headers in CSV files. Added export function for failed envelopes.Usability UpdatesNow includes improved default signature and initials instructions. Added download document option to Action menu.Resolved Issues and Other UpdatesFixed white spacing on iPhone 14. Restored Settings tab visibility. Resolved duplicate signing instructions issue. SMS Compliance: Updated SMS copy for compliance, including Terms and Conditions and Privacy Policy and resolved responsiveness issue with HELP and STOP SMS replies.For more details about this release,

We are pleased to announce the latest release of our RPA LE product, featuring enhanced browser actions in IE mode for seamless compatibility with Edge for Nintex Bot, ensuring reliable task automations involving the Edge browser. This release includes updates to RPA Central 2.13.0, RPA Bot 17.13.0, and RPA Chrome Extension 3.1.0.0. Key release highlights:  Improved detection and handling for IE legacy web apps in Edge.  New Chrome Extension version for newly created actions, maintaining compatibility with existing actions.  Target rule enhancements for reliable action execution across instances of target elements.  Various fixes including support for Bridged Tables in Chrome, diagnostic tool improvements, and email action compatibility enhancements.  For more details on these enhancements, please refer to the

Back in the olden days when I used Nintex for SharePoint, one of my go-to functions was the  UserProfileLookup.  It was so handy to look up details of the person.  Now with my main tool of choice, Nintex Automation Cloud, I don't need to use it because I've got features like Azure Active Directory lookups.  However there are properties that are only stored in SharePoint - most of these revolve around the social aspect of SharePoint such as "About me", "Ask me about" and "Interests". Those who are used to this query, you had to go and find the internal name and then query that.  If you're interested, here's the list of the default properties and internal names however before you get ahead of yourself, you don't need that list any more in Nintex Automation Cloud because we do it for you. 

Are you ready for the early 2023 release for your K2 Cloud environments? Starting to roll out in May, this version includes a lot of stability and performance improvements, including:The Workflow Designer previously used SignalR to autosave changes at every click. SignalR has been removed in this version to enhance performance in the Workflow Designer. The autosave that triggers every two minutes still remains. If a workflow closes unexpectedly, it now remains locked and reverts to the last saved version. When you edit the workflow, a pop-up allows you to unlock it and retrieve the last saved version. The owner of the workflow can also unlock it from the workflow menu in the category tree of the Designer. Each release includes all bug fixes from preceding releases; see the release notes for more details.And a

 Nintex DocGen customers can now write signer data back to Salesforce with our new write-back feature. With this powerful feature it is now possible to capture information a signer gives when signing a Nintex eSign document, and write that data back into Salesforce records related to your DocGen Package.    Take advantage of this new capability to keep your Salesforce records accurate, and leverage signing activity to automatically progress your salesforce opportunities, cases, claims and more. How it WorksSimply create a Nintex DocGen package and add a Nintex eSign delivery as you normally would. Then update your Signer inputs (Jotblocks) in your Nintex eSign template with the Salesforce records those inputs should write back to. When your Document package is executed, the generated document(s) will be sent out for signing as usual, but now the data filled in by your signers appears back in Salesforce.

Nintex continues to build upon the range of data sources that can be managed as data source variables (DSVs) on the forms designer External Data tab. The latest data source to be added is Azure Active Directory (AAD) permitting functionality that has been regularly noted in feature requests. Let's look at an example. In this instance, I've already created a connection to AAD on the connections page. Now let's create a data source. For the most part, this screen hasn't changed, it still contains the same configuration options seen below: However, there is a new option at the bottom of this screen to specify the columns to be made available in the data source - as with other data sources, you can leave this empty to retrieve all columns. 

Ever wondered how to display SQL table inside your Nintex Form? Indeed, there is the “SQL Request” action, but it only allows you to show data from database as a dropdown, list of options, etc… and always – just a single column.However there is an easy solution for that. The approach I am using includes usage of the “FOR XML” command in a SELECT statement (source). It is available in SQL Server starting from version 2008. It returns data from a query using an XML format, concatenated in a single row, in a single column. Perfect format to parse it!Step by step1. First prepare your SELECT query. Mine is for example:SELECT TOP(1

Nintex eSign customers can now benefit from our new bulk send feature. Increase your team’s efficiency by sending your envelopes for esignature to multiple recipients at once with ease, rather than one by one.This time saving feature helps you bulk-send your envelopes to up to 1,500 recipients at a time—up to five times more than other competing offerings.*With the new bulk send feature, you can eliminate hours of time and effort spent sending these individually and ensure important documents can be signed in a timely manner.How it WorksUsing your simple setup templates, upload your list of signers to a CSV file to specify the recipients for signature. Users can preview their signer list, schedule release, search bulk send instances and track the status of each document. In minutes, all bulk send envelopes are sent f

Nintex Promapp® process variation shared activities are here.  An improved way to manage process variations is now available. This new shared activity model for managing process variations means you'll have increased visibility over how changes are propagated, in addition to some other great improvements: Conduct side-by-side comparisons between variations. Drag and drop activities from one variation to another. Better highlighting for shared content. Accept/Reject model for changes coming from other variations. Use parallel activity functionality. Why have we made these changes? Client feedback suggested that with the current variation capability they lacked visibility when making changes to standard processes and clarity in understanding the flow-on impacts to other linked processes.    Other enhancements requested were: Making stan

In this blog I am going to go through the recently released data source variables for Salesforce.  For information on the data source variables please check our help article Data Source Variables. Salesforce Data Source Variable’s With a recent update in Nintex Workflow Cloud, we now can pull data from Salesforce Objects into the workflow start form.  For example, in the image below we are loading some data related to the Account and Case Number selected in the form.  Let's take a look at how this was setup, first thing we need to do is setup two data lookups for the Account Name and the Case Number, the Case Number drop down is filtered on the Account selecte

Nintex Community Update Last December, we launched our new Nintex Community. During the design process, we took feedback from customers and created an open Archive section to store older content that would be accessible, but not a distraction, with the ultimate goal of creating a more effective and valuable experience for our customers. Most of that content has been migrated into the Nintex Community Archive. Once completed, we’ll provide regular updates to the Nintex Community. As always we value your feedback. If you have any questions, we are always happy to help! Please reach out to our Community team at nintex.community@nintex.com.