SharePoint lookup columns and lists haven’t completely been replaced by the managed metadata service on SharePoint. Using them on a Nintex Form and processing the output is easy, once you know how.
Nintex introduced task outcomes in Office 365 back in February 2015. That’s great- if you use task outcomes. Task outcomes are powerful functionality. However, if you don’t want to use the outcome block, there are ways to avoid it.
One of my clients has made the jump from on premise to Office 365 for their SharePoint solution. It’s now my job to get their Nintex workflows running on Office 365 – here are some of the resources that have helped me out.
The standard outcome control on a Nintex flexi task form is a selection of the possible outcomes, either in a radio button list or a column of buttons. This is fine for many, many situations where the flexi task can be implemented, but sometimes you need to replace the outcome control on the Nintex Flexi task form.
I needed to hide the ribbon on a specific Nintex form. Yes, the client had heard my arguments about why you should keep the ribbon and decided to remove the ribbon regardless. Removing the ribbon from that one form did not turn out to be quite as straight-forward as I expected.
Hannah's SharePoint 