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.
It’s common have a main item or document with associated tasks when working with a workflow. If you need a link from the task form to the main item form, perhaps to update the main item, here’s how to do it. This was tested on Office 365.
When you get the value of a person via Nintex Workflows, you often get a bit of a messy string back – it starts with “i:0#.f|” and may also be “i:0#.f|membership|” . That string is the claims token. Here’s how to get rid of it using the Regular Expression action on Office 365.
Changing the background color of a form on Nintex’s on premise solution is easy. The setting is under the big “form settings” button. On Office 365, it’s not in the form properties but in the layout settings.
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.
As part of a much larger case management system, a client wanted to have one form with multiple yes/no radio buttons. These questions act as gatekeepers: the user cannot proceed to the next question until the previous question has been answered.
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.