I had a weird thing happen on a SharePoint 2013 client site a couple weeks ago and thought I would share with you all in case you ever find yourself with the same situation.
As you may be aware the Flexi task in Nintex Workflow uses a custom form provided by Nintex by default. This form displays all defined Outcomes as a radio button choice list on the form along with Comments and Item Properties. However, instead of the default form we are used to seeing, what we saw on our client environment one day was that all the Flexi task forms in one site were displaying what looked to be an OOB SharePoint task form. Continue reading “Nintex Flexi Task form reverted to OOB SharePoint form”
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 “Nintex Workflow Task Actions Feature Comparison”