Introducing Task Outcomes for Nintex Workflow for Office 365

Nintex Employee
Nintex Employee
11 8 8,871

Since we launched Nintex Workflow for Office 365 building workflows with task actions hasn't been as simple or as easy to use as we’d like. Today we've rectified that by releasing a new capability into Nintex Workflow for Office 365 called Task Outcomes.

With Task Outcomes, workflow designers can quickly and easily create and view multiple outcomes for tasks that meet their process need, even if they have three or four different possible outcomes directly from within the workflow designer.

Faster and easier to design

By default when you drag on a task action, you can now see that there are two outcomes, Approved and Rejected and their associated branches, which you can easily drag on other actions to further define what you want to occur depending on the outcome.


Whilst in many cases the Approve and Reject outcomes are sufficient, it is important to give the designer the flexibility to configure the outcomes to meet their specific needs, perhaps using Yes and No, or adding a third option such as More Information. With Task Outcomes you now have the flexibility to change these options as you need, directly from within the designer without the need to understand complex SharePoint concepts such as site content types and inheritance (although if you understand these, we do support their use too).

Task Outcomes Options.png

Automatically upgrading your workflows

We've also done a lot of work to make sure that your existing workflow designs will be upgraded seamlessly to use this powerful new capability. When you open an existing workflow design that captured the task outcome in avariable for evaluation later on, we will automatically populate the variable for you in the correct branches, making sure your design continues to function the way you expect it to, whilst still giving you option to redesign your workflow to leverage the task outcome branches.


Upgrade the app to get the most out of Task Outcomes

We're rolling out the Task Outcomes capability into Nintex Workflow for Office 365 now which will let you see the branches on tasks for your existing defined outcomes. However, to get the most out of the app and activate the ability to change the outcomes from within the designer, you will need to update the Nintex Workflow for Office 365 app inside your SharePoint Online site to version by clicking on the update link visible in the Site Contents view or visiting the SharePoint Store, this may take a day or so to propagate in the store and be visible in your specific tenant.

Some common questions

Q. I already have workflows designs that use Conditional Branch actions to check the outcome of a task, will these still work?

A. Absolutely. If your workflow design evaluated a variable to determine the outcome of a task, we will seamlessly upgrade your design to ensure that variable is still populated and ensure your workflow design continues to work as you would expect.

Q. What about my running workflows with tasks?

A. They will continue to run as normal with no impact. When you republish the workflow, it will be upgraded to use the new task outcomes feature.

Q. I can’t seem to edit these new task outcomes in my tasks inside Nintex Workflow for Office 365?

A. The new task outcome feature requires you to upgrade the Nintex Workflow for Office 365 app on the site to the latest version which request additional permissions to allow the designer to change content types, only once you have done this and accepted the trust request will task outcomes become editable, until then they will reflect the outcomes defined for your default workflow task content type.

Q. How does Nintex Workflow for Office 365 store these different outcomes?

A. The Task Outcomes feature leverages out of the box Site Content Type functionality of SharePoint. When you first publish a Nintex Workflow with the new task outcomes, we will create a new content type in the site collection root site that all child Nintex workflows will inherit from, this ensures our configuration is isolated away from normal SharePoint Content Types.  We do a lot of housekeeping to ensure the most efficient use of content types.

Q. I want to use my existing site content types, can I?

A. Yes you can. The task actions still allow you to choose an existing configured Site Content Type by choosing ‘Content Type’ in the action configuration.

Q. What happens when I move workflows using tasks between sites?

A. We record the configured task outcomes in the exported .NWP file and will either match them against existing content types, or take care of creating them again for you in the target site. No need to manually create the outcomes again in the target site.

Q. Will the Task Outcome variable be available for use in my new workflow moving forward?

A. With this new feature, we’ve striven to improve the usability and simplicity of the task action by adding the branches and moving the outcomes onto the canvas for the designer to see visually, removing the need for the Task Outcome variable option at all.

Q. This is great, but what about the other task features we have in on-premises?

A. Thanks We know how important having a complete task experience in Nintex Workflow for Office 365 is, look out for more key task features coming soon including Lazy Approval.

Nintex Newbie

Oh I really like this!

Not applicable

Is it possible to have a task without outcome, a simple assignment with a "complete" button? From our tests we could delete one of the default two options.Thanks.

Nintex Newbie

From what I understand you have to have at least 2 options. If you like the 'Complete' option. You can create 'Complete' and 'Incomplete'. Then delete the others. I have done that in one of my solutions.

Not applicable

Thanks for your answer. I should be able to simply assign a task. In this case I don't see the point on having an incomplete action/button. The "incomplete action" is having it still assigned. 

A forward action for instance would also be useful (I'm new with the product - perhaps it already exists).

Not applicable

Thanks for the informative article.


Observed that when we add custom outcomes for a flexi task activity Nintex is creating new column (for every workflow)in Workflow Tasks list (I understand as this happens because of site columns addition). If there is an API available from Nintex for GetFlexiTaskOutcomes then we wouldn’t care about it. Do we have this API as we had in onpremise.

However we like to know what is the GUID associated there.

Nintex Observer


Strangely, I seem to have lost the ability to define outcomes....I can only pick from the content types already created. Any idea how this would happen?

Design Dabbler

Thanks Alex, very good article.

Quick Question - how can we add Content type in Task Outcomes (retrieving form the site content types)- see below


Nintex Newbie

Any method how i can store the task outcome in a workflow variable(like nintex workflow on-premise versions) and get the current date and time as well of the outcome?