nintex

Nintex Approval Action Comparision

Blog Post created by nintex Expert on Dec 31, 2014

Title

Assign Flexi Task

Assign To do Task

Request Data Action

Request Approval

Request Review

Purpose

Flexi task action allows user to respond with either approve or reject the task but able to create custom outcomes.

Assign To do Task action allows user to respond with either approve or reject the task.

The request data action is used to retrieve some information from the user based on the content type configured within the action.

Request Approval action allows the user to respond with either approve or reject.

The request review action is similar to the approval action but the user does not have to enter an outcome, just review the item and then select continue.

Creates Multiple Tasks?

Yes

Yes

No

Yes

Yes

Content Type

No

Choose to use an existing, or instruct Nintex Workflow to create a new content type.
Note:
The ‘Nintex Workflow Task’ content type is reserved for request approval and request review actions.

Choose to use an existing, or instruct Nintex Workflow to create a new content Type.

No

No

Reviewer Response

5 Options
•First response applies
•All must agree
•Majority decides
•Majority must choose a specific outcome
•All must agree on a specific outcome

2 Options
•All must review
•First response applies

No

4 Options
•All must approve
•First response applies
•Only one approval is required
•Vote

2 Options
•All must review
•First response applies

Enables you to Customize the task form?

Yes

No

Yes

Yes

No

Task Notification

Yes
(Multiple User or group)

Yes
(Multiple User or group)

Yes
(single user or group)
Note: If it is assigned to a group, the first group member to respond will act on behalf of the entire group.

Yes
(Multiple User or group)

Yes
(Multiple User or group)

Not Notification Required

Sent when the user no longer needs to respond to the task. This can occur when:
•A task is assigned to multiple users but only one is required to respond.
•The workflow is terminated prior to the task being processed.
•An error occurs in the workflow at runtime.

Sent when the user no longer needs to respond to the task. This can occur when:
•A task is assigned to multiple users but only one is required to respond.
•The workflow is terminated prior to the task being processed.
•An error occurs in the workflow at runtime.

Sent when the user no longer needs to respond to the task. This can occur when:
•The workflow is terminated prior to the task being processed.
•An error occurs in the workflow at runtime.

Sent when the user no longer needs to respond to the task. This can occur when:
•A task is assigned to multiple users but only one is required to respond.
•The workflow is terminated prior to the task being processed.
•An error occurs in the workflow at runtime.

Sent when the user no longer needs to respond to the task. This can occur when:
•A task is assigned to multiple users but only one is required to respond.
•The workflow is terminated prior to the task being processed.
•An error occurs in the workflow at runtime.

Escalation

Yes
2 Options:
•Delegate task
•Complete task

Yes
2 Options:
•Delegate task
•Complete task

Yes
2 Options:
•Delegate task
•Complete task

No

No

Reminders

Yes

Yes

Yes

No

No

Lazy Approval

Yes (only applicable with email delivery)

No

No

Yes (only applicable with email delivery)

Yes (only applicable with email delivery)

Delegation
Exception:
A site administrator can delegate tasks that are not assigned to them or if delegation is not enabled.

Yes

yes

No

Yes

Yes

set user permissions for the Task

yes

yes

yes

yes

yes

Outcomes