There are many different types of task actions available with Nintex Workflow. But sometimes knowing which one you should use can be about as clear as mud. What’s the difference between Assign Flexi task and Request approval? They both have an Approve and Reject/Decline branch, right. So, how different can they be? How about Request data vs. Request review? And then there’s Assign to-do task. You might think, “That seems familiar, maybe I’ll just use that one and not worry about the others.”
The truth is, some of the actions behave similarly, but have different features and built-in capabilities. The action that you choose will depend on the specific requirements you have to meet with each step of your workflow. To help you in your quest to create the most useful and user-friendly automated processes, I will share with you some of the main differences between the various task actions. Continue reading
“Can I move my Nintex workflows from on-premise to O365?”
Recently, this is the question we have been hearing more and more frequently from clients and potential clients.
If you are considering moving from something like SharePoint 2010 or 2013 to Office 365 OR if you are considering a hybrid environment (where you maintain both on-prem and cloud implementations of SharePoint) you might have had the same question.
Up until now, the answer has been a simple “No”. But with the announcement last week of a new partnership between Nintex and Sharegate, the answer will soon be “Yes!” Continue reading
I came across an interesting (and unexpected) challenge today and thought I would share my solution in case there are others out there who may be facing a similar set of requirements.
The Business Scenario
We have a document library with Document Sets enabled and there is a WF that runs on each Doc Set. At a certain point in the WF there is a requirement to find all documents inside the doc set that are a certain content type and create a new PDF document in the Doc Set.
Turns out, it was not as straightforward as I was thinking it would be. Allow me to explain…
Ever wondered what the user experience will be for users in your site with varying SharePoint permission levels when it comes to Nintex Workflow and Forms?
- Who can create WFs?
- Who can see the WF Designer?
- Who can interact with running WFs or kick off new WFs?
- Who can customize forms with Nintex Forms?
Let’s take a look at what the Nintex user experience is like for some of the main SharePoint permission levels: Read, Contribute, Edit, Design, and Full Control. Continue reading
I am self-taught when it comes to SharePoint and Nintex. Everything I know has been picked up over the years through a combination of trial-and-error, troubleshooting with coworkers, reading posts online, investigating answers to questions from clients, pushing the limits of the OOB capabilities, and just plain poking around to see what’s available and what can be done. While this process can be fun and fluid, it also means that not all features and functionality are uncovered immediately. I didn’t have someone to walk me through all of the cool, useful, and sometimes discreet settings that were just sitting there waiting to be leveraged. So with that in mind, I want to be that person for you!
One of my goals with this blog is to shed a bit of light onto some of the often overlooked areas of Nintex so that you start to have a full set of tools in your toolbox as you dive into automating your business processes.
It took me awhile to discover the Common settings available in the action configuration dialog of the Nintex Workflow actions and I wish someone had pointed this little gem out to me a lot earlier. So without further adieu, let’s talk through the features available with the Common settings. Continue reading