News

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.    

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:

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

In a perfect world, we will have anything we need in the way we want it, but the world we living in is not perfect, so we will need to go around to get things done. If we have a local OCR system which could take any format of documents for OCR, we can simply get our scanned PDF/tiff document OCR. In my next blog post (i.e. part 3), I am planning to send our document(s) to be OCR using google Vision API. Google Vision API only takes/supports PDF file that is stored in the cloud drive. When come to store important documents in the cloud, it concerns the banking and finance institutions users. Before we get into Google Vision API, let us examine the built-in Simple OCR of Foxtrot. I am demonstrating the two ways I know on how to use the Simple OCR action: Creating OCR Action with Selector (e.g. OCR an openned PDF file)1. Open the PDF that we wanted to OCR.Before we could use the Selector to create

Products: Nintex Workflow 2013, Nintex Workflow 2010 We often encounter a situation where the performance of a SharePoint farms workflow infrastructure could be drastically improved if fragmentation on Nintex Workflow databases were minimal. This script will provide a way to review the fragmentation of all table indexes inside of the Nintex Workflow ConfigurationStandalone Content database. Run the below (attached as well as a *.txt file for your convenience) PowerShell script (PowerShell ISE works well) from a SharePoint Server:  PowerShell Script Add-PSSnapin Microsoft.SharePoint.PowerShell   [void][System.Reflection.Assembly]::

I'm re-surfacing an old blog post I did a few years back over on my personal blog site http://www.sharepointpub.com as it has come up in conversion a bit in the past few weeks.. I'll leave the SP2010 screenshots as the process is the same for 2013.This is a pretty common scenario, and yes in most cases escalation isn’t setup.. By design, SharePoint will not allow anybody other than the task owner or an administrator the rights to approve a task. In Nintex Workflow by selecting the “Allow Delegation” a link will be placed on the task approval page. Allowing the task owner easy access to re-assign the task..

Continuing from my previous post on Latitude and Longitude UDA, the process that I was discussing this week was around a company whose employees would go on business trips and they would stay at a hotel.  What they want, was to automate a process that at a particular time of the day, a notification would be sent out to their employee with information on how much it would cost them to get an Uber ride from the hotel they are at and also the duration of the ride to the airport they need to go to.  Requirements In order to get that information from Uber, you will need to h

We are excited to announce the latest release of Nintex eSign that makes esigning a document faster, easier, and more intuitive than ever before.Watch the video of the new signing experienceUpdates to the signing ceremony kickoff include:First-page preview of the document to sign First-page view of number of fields to complete for the document to sign Default agreement to terms and conditions when initiating the signing processWe’ve also made updates to the signing process itself, including:The Left-Right orientation in a desktop browser is now Top-Bottom, the same experience as signing on a mobile device, making the document being signed even easier to read Improved prog

The Nintex Community will be undergoing essential maintenance on 22 -23 February.Notification emails will not be sent from the Community during this time. You will still be able to ask questions but new registrations won’t be possible.This downtime is required for essential maintenance and content updates to our Community.  When: 22 February 08:00 Tuesday, Eastern Time (ET).How long: The process will start at 08:00 Eastern Time (ET) an

Nintex is retiring the Assign a task action, which will no longer be available for new workflows as of 31st December 2022. Instead, use the Assign a task to multiple users task action to take advantage of many new capabilities around assigning tasks.    Details:Although the Assign a task action will not be available for use in new workflows, it will still be available in the following scenarios:Existing workflows that use the Assign a task action will continue to run. If you have an existing workflow using the Assign a task action, you will still be able to update the configuration and publish your workflows. Support cases for the fundamental functionality of Assign a task will still be addressed. Non-critical support cases can be more quickly resolved by moving to the Assign a task to multiple users action. We recommend replacing th

Recently, I was approached with an interesting use case. The ask was to create a unique password, have that sent to a customer, and then provide that customer with a task form that would only enable them to access the data on the form if they have the proper password. For this use case, the data on the task form would be the URL to a Nintex Sign agreement that the customer would then be able to fill out. Luckily enough, we have a really simple solution.  First things first, we needed to create a unique password. This can be anything you want it to be. It can be a combination of the customer's first name, last name, or company name. We can also throw in some random letters and numbers as well. What I ended up doing, was combining the user's last name, and took apart the current time, and added the numbers before and after their last name. For example, if the time was 11:30, and I was the customer, it would look like: "11chu30".

Happy New Year from the Nintex team! Over the last few months, we’ve had the opportunity to meet many of our customers and partners to get feedback on our products and how we can best support you with your automation needs. During our conversations, we received consistent feedback about our K2 products and your desire to hear more about future investment plans for both K2 Five and K2 Cloud.We want to take this opportunity to affirm our commitment to our K2 customers and to share the following updates regarding our K2 products with you:K2 Five remains a core product in the Nintex portfolio, offering best-in-class automation and app development capabilities for customers in hybrid, private cloud, and on-premises environments. New features and capabilities will be added on an annual release cadence. We previously updated ou

To accommodate rapid Nintex customer growth, we are scaling out our data centers around the world to ensure maximum performance.The small number of customers who will need to take action as part of this data center expansion will be notified separately and individually during December/January.If you are a customer intending to use Nintex DocGen’s FTP or SMTP delivery options in the future, or have Salesforce IP Restrictions configured in your Salesforce Orgs, check out the new DocGen IP Allow List to update your IP allow lists in your network and Salesforce settings.NOTE: This is an updated IPs list since December 2022.For future maintenance updates, consider subscribing to

Today I am going to illustrate practically how to capture LAZY approval comments from inside mail body in NINTEX on-premise. There could be different ways but the way I have implemented in recent project seems to be very easy and useful. Actually from any task component inside in the workflow if you enable LAZY approval recipient will get an email in his mail box.(Configuring lazy approval : Click here)User can then simple reply back to the mail putting his opinion (Like Approved, Reject, Rework etc) in the first line and additionally can put comments in the next line

Nintex is thrilled to announce the latest major updates to the Nintex Process Platform. With these updates, Nintex continues to unify its Process Platform, while existing customers can now modernize their workflows up to 4x faster than starting from scratch.The Nintex Process Platform transforms the way people work through process intelligence and automation. The next-generation cloud platform provides easy-to-use tools for visually discovering, quickly automating, and continuously optimizing business processes and workflows. The platform consists of intelligent forms, advanced workflow, digital document generation, eSignatures, robotic process automation, process discovery technology, and powerful process management.The most recent updates to the platform include enhancements that integrate multiple automation components and provide migration utilities that he

In this blog I am going to go through the recently released manual delegation feature for Nintex Workflow Cloud.  Please also refer to our how to guide Nintex-Workflow-Cloud-Task-Manual-Delegation-feature  Manual DelegationWith a recent update in Nintex Workflow Cloud, we now have the ability for a user that is assigned a task to delegate that task to another user/s.  This only works for authenticated forms and it uses the assign a task to multiple users action.   In the form settings make sure to have Nintex Mobile and My Nintex checked as the delegation will happen in My Nintex. 

A customer recently reached out wondering how we could get the manager and manager email from Okta so that it could be used to assign tasks in a Nintex Automation Cloud workflow. We do have a few Okta actions out of the box, but none of them would allow us to retrieve the data we needed.In order to be able to pull back the user profile data a custom Xtension would have to be created to call the Okta users API.  The new Xtension along with instructions for it's setup and configuration can be found at the following link:  Nintex Gallery - Okta User Profile SearchOnce you have the Xtension installed and connected it will show up in the left-hand navigation along the other connectors. Now that we have th