News

Note: I found an issue where setting up the inactive filtering on the form in the List Lookup control caused the control to break in Nintex Mobile. I've updated the steps so the filtering is now done on the list instead of on the form. I've been working on a form that contains a dropdown list populated by a lookup list and requires the ability to inactivate items in the lookup list. When an item in the lookup list is inactivated it should no longer be available to select on a new form but still needs to be displayed on previous forms where that value was selected so that historical data is preserved. I looked through the Nintex Community to find a way of doing this but didn't come across anything. Now that I've completed my solution I thought I would share it in case others are looking for ideas on how to accomplish this. In my example I will use the scenario of a mobile device request form. The list of mobile devices that can be ordered through our Service Desk is updated regularly. W

Hello again!I wanted to take some time and go over the Query List action as there has been a rise in questions from the community on how to leverage it. Not only the query, but what to do with the data after we query it. Let's dive right in.  Query List ActionThe action is straightforward enough; query a list for specific results. An example could be all items where [Created] = {varDate} or [ID] = {varLookupID} or even just return all items (I would advise against this if possible). But how do we store the resulting data? What about if we get multiple results? If you know that the query is going to return only one item every time, then a normal variable (based on the data type it will be storing) will suffice. Otherwise, you are going to want to store your results in a Collection variable for every piece of data you want to do something with. So, if you are querying a list with 10 columns, and you only need 4 of them (to send a notification), you will need to create 4 collection variab

In a continued effort to invest in feature parity between our DocGen for Salesforce Classic and Lightning designers, Nintex is pleased to announce that DocuSign eSignature capabilities are now available as a delivery option within the Nintex DocGen for Salesforce Lightning designer experience. This is now available in addition to our legacy DocuSign integration for the Salesforce Classic interface.With DocuSign now available within DocGen for Salesforce Lightning, DocGen customers using the Salesforce Lightning environment can now seamlessly use DocuSign for e-signing of the documents they generate with Nintex, providing an easy, efficient document execution experience for everyone involved in a document-centric transaction.This new integration leverages the DocuSign App Launcher Salesforce app, and like our legacy DocuSign delivery option, this integration allows the designer to complete all fields needed for the DocuSign envelope, right from within DocGen. Nintex DocGen then dynamica

By now, you’ve heard that we’re changing the names of several Nintex products, including Nintex Automation (formerly known as K2 Five). The name and colors may change, but the features you know and love are still there, and some new things are now available! Available now to download on Nintex Customer Central (be sure to filter for “Nintex Automation” in the products drop-down menu), the latest version includes some great new features, including:Style Profile: preview form. Select your own form to use as the preview form in the Style Profile Designer, and now you can see the impact of your chosen colors and linked CSS/JS files on your own form, without having to have multiple tabs open or check-in your form or style profile. Style aware controls. Building on the Style Profile color variables, now the ratings control, radio buttons and checkboxes, and toolbar buttons respond to the color variables to automatically change color and match your branding profile. Nintex Automation product

IntroductionThis is a follow-up to the post where I describe how we configure and complete asynchronous server events. I showed you how one can complete the server event using a REST call, but sometimes a REST call is not needed or possible. In this post I will extend the mechanism to make use of SmartObjects on a SmartForm. Use CaseFor this scenario, I am a technician, repairing customer machines on-site and I may not always have all the replacement parts on hand. When that happens, I can submit an order to the supplier which will deliver the part directly at the installation site. But, as we all know, deliveries are unpredictable and I won’t always be able to determine the actual delivery date and time.To handle the variability, K2 will start a process when I submit the order, generate a QR code as part of the weigh bill and then wait for the next step. When the part is delivered, the receiving department will scan the QR code, which in turn will proceed to the next step where I will

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 forum. Alternatively, for customers who prefer to continue with SharePoint On-Premises, more mig

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:   Use the following HTML to follow the example: <p>Crystal Palace</p><div class="container">  <div class="goals palace">9</div></div> <p>Liverpool</p><div class="container">  <div class="goals liverpool"&

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 to remove history list items for workflows that have a state of Running, Completed, Cancelled, Error or All state. The default is Completed if -State is left off.Don't use -state All in production. Only purge completed workflows that you don't need to review the history of. If you purge running instance data, it will not be able to continue.To ge

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

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

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 the instance manager. If you want to add this same capability to a workflow started via a Nintex f

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

 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