News

This is a short workaround i've put together on how you can use a component workflow within Office 365 to capture workflow information and append it to a history list on the item that your workflow is running on. Check out the video below on how it works:   How to use this: 1. Download the component workflow i've built2. Create a column called "Workflow History" on the document or list you'd like to log3. Import the workflow as a site workflow4. Update it to connect to your list and update the "Workflow History" column you created.5. Update your list/library workflow to call this component workflow.  Enjoy!!

Nintex is thrilled to announce the AI Form Translator, part of the Nintex Forms capabilities of Nintex Automation Cloud. This new capability helps forms designers leverage Generative AI to automatically translate forms into multiple languages on the fly.This capability follows on the heels of the recently released AI Form Generator feature, adding real-time translation capability to this automatic form generator.Once forms designers enter plain language text to specify the form they want, the AI Form Generator goes to work to create the form

Sometimes we remember about inline functions and runtime and use them on different parts of the design of our Nintex Forms, but we don't get the expected result by us, and sometimes it's simply because we haven't considered when they are executed. The difference is that Inline functions are run when the form is loaded., although the Runtime Functions will run while you have the form open, changing a control 's value, so filling a text field will cause the Runtime function to evaluate again. This is a simple reminder for me and you.

In this month’s user spotlight blog, we’re talking to Eric Rhodes (bamaeric), a Senior Developer for Fulton County Schools in Atlanta, Georgia.Eric RhodesWhat is your current role, and your career background?I am currently a Senior Developer for Fulton County Schools in Atlanta, Georgia. It’s hard to believe, but I have been in the Information Technology field for 30 years as of October 2023. My first job out of college was COBOL programming. During the course of my career, I have been a support technician, network administrator, webmaster, developer, consultant, and trainer. I have been building applications using the Nintex Process Platform since 2009, when I started using Nintex Workflow 2007. I have been fortunate in my care

Nintex is thrilled to announce the AI Form Generator, part of the Nintex Forms capabilities of Nintex Automation Cloud. This new capability helps forms designers leverage Generative AI to automatically generate forms from plain language written input. Simply type what you want in your form, and the Nintex Forms Designer does the rest! Create user-friendly forms more efficiently and with less manual effort.  Avoid time-consuming efforts to build complex forms structures and logic.  Accelerate your project’s time to value for customer- and employee-facing forms used in automated workflows.  This exciting new capability provides AI-powered suggestions and guidance

I’m a big fan of applying technology where it makes sense.  There’s massive interest in Chat GPT since it was released and people (myself included) have had a great time asking it questions.  I have also seen some early adopters try to shoehorn it into their products but all they’re doing is putting their product UI over the Generative AI (GAI) engines.  That’s not a very useful application of the technology. Nintex takes a balanced approach to AI.  We need to apply it where it makes sense and we also need to apply it responsibly.  One example where GAI makes a significant difference to building applications on the Nintex platform is the newly released AI forms builder. Prior to the AI forms builder, our options to build forms were to think about the fields that need to be on a form and then use the drag and drop interface to add and configure them.  It’s fast and efficient.  If you have existing forms, you can use our PDF import function.  You save a pic

New Singapore data center now available for flagship Nintex Automation Cloud offering.Nintex continues to invest in additional data centers around the world to ensure customers have secure, compliant, and performant access to all our cloud-based offerings. In response to continued customer demand for cloud-based workflows in the Asia Pacific region, today Nintex is proud to announce it has activated a new data center in Singapore for the company’s flagship Nintex Automation Cloud product. New customers will now have immediate access to this new data center, powered by Microsoft Azure, in addition to existing data centers in Australia, Canada, Ireland, the UK, and the U.S.Customers in Singapore or neighboring countries can now adopt Nintex’s market-leading automation capabilities with complete confidenc

Get product strategy and roadmap insights, learn what's new, and see in-depth demos.Nintex customers and partners, I’m thrilled to announce our on-demand Process Platform update webinar!Nintex has embarked on a new path forward to help organizations quickly and easily define, manage and automate business processes with AI-based, low-code/no-code tools.In this webinar, you’ll get a behind-the-scenes look at our product vision and plans to deliver the most complete, connected and convenient process platform in the industry.Watch this webinar and:Get executive in

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 l

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

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 integra

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

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, generat

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