In case you weren’t able to join us at the Nintex ProcessFest Training Conference a few weeks ago, you can check out the recording from my breakout session on the Abel Solutions website.
My breakout session, titled “Implementing Scalable Solutions with Nintex Workflow and Forms”, walks you through a client case study with a large utility industry customer. Continue reading “ProcessFest 2019 – Implementing Scalable Solutions with Nintex Workflow and Forms”
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”
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…
Continue reading “Query Inside a Doc Set for Specific Documents to Convert to PDF”
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 “SharePoint Permissions and the Nintex User Experience”