Skip the outcomes on a Nintex task form on Office 365

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.
Add button on Nintex task form to edit main item with JavaScript
Remove claims token with regular expressions and Nintex on Office 365
Change Nintex Form background color on Office 365
Getting started with Nintex on Office 365
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.
Nintex Workflow and Forms with multiple yes/no radio buttons
Replacing the outcome control on the Nintex Flexi Task form

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.
Hide the ribbon on a Nintex 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.
Add a webpart to a view on any SharePoint list or library

One of my favorite features in SharePoint is the sheer power available in lists and libraries. I love teaching this part of the platform because there are so many hidden gems, functionalities that people really don’t know about but can make such a difference.
This post is about adding a webpart to a list or library view page. This functionality has been available since SharePoint 2010. Did you know that every single view in SharePoint is its own page and has its own URL, so that you can link directly to it? This means that every single view page can be edited so that you can add a webpart to it.