Sometimes the data that you need for your business process lives in a separate site or site collection than the one where you are building your Nintex Workflow. Fear not! You don’t have to get up to your neck in the CAML Editor of the Query List action to extend the functionality. Allow me to show you how! Continue reading “Query Cross Site Collection with Nintex”→
When you search the web for “nintex update managed metadata field” you will find many posts with potential solutions to this challenge. However, you may also find that all of these posts only get you a part of the way there. So, this post is intended to aggregate all of the great information that’s already out there, but hopefully make it simpler for you to combine it all together into one cohesive solution. Continue reading “Update Managed Metadata (MMD) column with Nintex Workflow”→
This post walks you through the steps I use to surface key Workflow History details onto a SharePoint list item. So, rather than having to navigate down into the Nintex Workflow History page to see who has Reviewed/Approved/Rejected/Completed an item and any associated comments, all of those details are more readily available on the Nintex form for the SharePoint item itself. This is also a good solution to make sure that these details are not lost with the workflow history when recommended database cleanup actions are performed—automatic, scheduled, or otherwise. Continue reading “Capture Workflow Approval History on SharePoint Items”→
I was working on a Nintex Form for a client recently where there were several disabled fields. Actually, based on the type of request they were submitting, anywhere from 2 to 20ish fields could be disabled. The problem was that the default styling of disabled fields is not much different than enabled fields and our client wanted to make it more obvious which fields the user should be focusing on for certain scenarios. Allow me to explain… Continue reading “Update the Styling of Disabled Input Fields on Nintex Forms”→
I had a requirement from a client recently to show all list item attachments on the various task forms in an approval process – which, if you think about it, makes total sense. With any project, we always have a common goal of making the user experience as seamless as possible for our users and approvers. So, why wouldn’t we provide all pertinent information needed (including related documents) to complete the requested review and approval, right there on the task form?
This past weekend, I had the pleasure of presenting at the 9th annual SharePoint Saturday event in Atlanta. For those who aren’t familiar, SharePoint Saturday is a community‐focused event dedicated to educating and engaging members of the local SharePoint community. The event is unique in that it is “for the community, by the community” and is free for all who attend.