News and Guidelines

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 much time in. Which Nintex Product are you most passionate about and why?My background and the hardest l

​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 Nintex Forms software? Plugins are web components adhering to a form contract developed by third party developers. Form Plugins Once registered, the plugin appears in the Forms Designer control toolbox as a custom control, which can then be dragged onto the canvas and configured by the designer. The custom control can utilize all the functionality offered by the form ecosystem like a native control, providing flexibility to meet specific business needs. The screenshot below shows plugins appearing in the control toolbox on the left under user-defined catego

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 that, you are clapping and cheering or at least have a smile on your face ?This

ATTENTION: The go-live for the new system has been pushed to 23AUG23. Good day!We’re thrilled to announce a new training experience coming to Nintex University. We're transitioning to a new learning management system to provide the best training experience for our customers and partners.This transition requires significant data migration, resulting in a week-long blackout beginning on August 14th, 2023. During the blackout week, access to Nintex University will be restricted – no new courses or certifications can be initiated or completed to ensure data integrity during the migration. If you need assistance during the blackout period, please ask questions and get answers through Nintex Community. All complete course and certification records will be migrated to the new system. Incomplete course or certification records will not be migrated. Questions? Please see the attached Nintex U FAQ, reach out to my team, or message any one of us directly here: @Nintex_Sam @Nintex_Wasim @Yotam @JR

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. From the Nintex Forms tab, click Settings on the ribbon. Expand the Custom JavaScript section in the Settings dialog box. Paste the signature capture script into the provided space. Clo

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-person Signing which allows for on-site signatures to be collected immediately after preparing a document for signature DocuSign Support in Lightning + OAuth Support for easy single-sign-on to DocuSign electronic signatures User

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 each activity to a

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 build AND/OR logic with clicks, not code  ELSE conditions in the rule builder Formula builder Type-ahead when building

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 code for the late

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.  In the workflow permissions popup, you will see two sections, one for Workflow Owners and the other for Business Owners.  Click on the Business Owners section and select the user/s you wish to add to the role for this workflow.  You can have multiple us

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. We'll navigate to the NWC Automate section and the Instances page...so what's new? First...at the top

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, please see the full release notes.Thank you for choosing Nintex eSign. We appreciate your ongoing support!

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 release notes.  Nintex is committed to ongoing support of these new versions along with Nintex RPA Foxtrot 15.1.13, and we remain dedicated to providing a robust and reliabl

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. In my example form, I've put a people picker in place so I can easily select a person's name.Of course you don't have to use this - all we need to look up someone's profile details is their email address

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 feature enhancement too:In the Style Profile Designer, you can now browse for your own preview form to see how your colors and linked CSS files will impact your existing SmartForm

Get ready to revolutionize your learning experience with our brand-new learning paths, designed to fuel your curiosity and ignite your passion for knowledge on the Nintex Process Platform! This innovative addition to Nintex University offers carefully crafted learning paths to match your unique goals, interests, and skill levels with Nintex products.Our learning paths combine a perfect blend of short but impactful courses, interactive quizzes, and hands-on projects, providing a seamless and engaging journey toward mastery. As you navigate this dynamic, user-centric approach, you'll experience learning like never before—enjoyable, efficient, and deeply rewarding. Embrace the power of Nintex University learning paths, and unlock a world of possibilities as you take the reins of your personal and professional growth!Currently, available paths include:Process Manager Essentials for Beginners Automation Cloud for Participants Automation Cloud for Designers and Developers - Beginner Automati

 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. For even more power, combine this new capability with Salesforce Flow to trigger fu

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.  Now, I'm going to build a simple form that allows selection of a user from AAD, and then populates other form controls with data related to that user i.e. Department, Job Title, Office and Mobile Phone - here's my form. You'll note that the related fiel

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) (SELECT name, lastname, email, role FROM users RIGHT JOIN roles ON roles.Id = users.roleId ORDER BY lastname ASC FOR XML) as datatable FROM usersWith such statement I am sure, that I will receive just a single row and column, that will return the data in a proper XML format. Each row will be built using the following structure:<name>value</name><la

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 for signature, and signers will receive notifications when a document has been signed.This feature is for our Nintex eSign customers only, and is not yet available in our Do

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 standard processes visible to everyone.  Increasing editor visibility so they can see linked content.  Enabling parallel activity. Enabling archiving for indi

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 selected in the Account Name dropdown. Account Name data source example: We will then filter the Case number data source based on the selection in the account name.  Now let's setup the data source variables for the case data we want to pull back and display in the form.  We are going to need two data sources to populate the data due to

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.    

Original Publish date: Feb 2, 2017PrefaceAs there is some mystery to where Nintex Forms are stored in O365 I have written a short document explaining how to find the elements that are created when you publish a Nintex Form to your list. In the unfortunate event where your Nintex Form has somehow become orphaned you can use this guide to either delete the form from the list manually or recover the form saved at the content type level. What we store when a form is publishedWhen a Nintex Form is published three things are created on your list/site:1) The content type form linkWhen a form is published links are added to the content type at the list level. This is used to launch the form when you attempt to create a new item or edit/view an item of the same content type. These can be found using SharePoint Designer by navigating to the content type on the list:2) The run time formWhen a Nintex Form is called, the NFForm.xml file is used to render the form. This can be found inside the conte

We are thrilled to announce the release of Nintex for SharePoint Subscription Edition, which integrates all the features and capabilities of Nintex Workflow and Nintex Forms into the latest version of SharePoint. Further details and answers to frequently asked questions can be found at the provided link.In addition to this release, we are also announcing the end of life for Nintex for SharePoint 2013, in line with Microsoft's end of support announcement for SharePoint 2013. The Nintex for SharePoint 2013 product will reach its end of life on April 11, 2023. However, Nintex will continue support for the product after this date as per the Nintex Subscription Support Policy, Section III, C, 3:End of Life: Nintex will provide Support for a Product Release or Release containing new features, modifications, or enhancements up to twelve (12) months after the issuance of the end of life notice. After such time, for an additional twelve (12) months, Nintex will provide limited Support to Custom