Assign a task to multiple users

Use the Assign a task to multiple users action A tool for building the processes, logic, and direction within workflows. Actions are the steps the workflow performs to complete a process. to assign a task to one user or multiple users at the same time. The workflow will continue based outcome provided by the assignees.

When you configure an Assign a task to multiple users action, a Form-based, Express approval, or combination task type is created. The workflow sends the task to the task assignees Recipient of a task. and then pauses until an outcome is decided. Depending on the completion rule you select, the task can be completed by assignees when the rule is satisfied; otherwise, the default outcome is used.

Configure the Assign a task to multiple users action

Important: 

Emails from tenants with a trial license can be sent only to email addresses of domains registered in the tenant. To see the list of registered domains in your Nintex Workflow tenant, go to Settings and then select Domain management. For more information about domain management, see Domain management.

  1. Add the action to the workflow and open the action configuration panel. For more information, see Add an action to the workflow.

  2. Type a Task name.
  3. Type a Task description.
  4. Enable the Task type you want for the action. You can select one or both task types. To view a description of the available task types, see Task type.
  1. If you enabled Task form as a Task type, configure the form:
    1. Click Design form to open the forms designer.
    2. Note: After you design a form and apply changes, this changes to Edit form in the configuration panel. You can then click Edit form to make additional changes to the task form.

    3. Define controls, rules, and styles as required for this task form.
    4. Click Apply changes.
  2. Define the Outcomes for the task. For more information, see Add multiple outcomes. The Outcomes fields that are displayed depend on the Task type and Outcomes you choose.

    1. If you want to define task outcomes, enable Multiple outcomes and type the Outcomes you want. Click Add outcome to add more outcomes to the action. A branch is created for each task outcome you define.
    2. If you select Express approval as the task type, type the Express approval term that your assignees must respond with to complete the task.
    3. Select Completion rules.
  3. If you want users to sign in to Nintex Workflow to access the task form, enable Assignee authentication. For more information, see Enable Assignee authentication.

  4. Add the Assignees and select the Assignment behavior.

  5. In the Message section, type the Subject and the Message body of the email. To expand the message body window and to see more options in the toolbar, click (Expand editor). For email file attachment information, see Add file attachments to the task email.

  1. If you want to send reminders to the assignees at intervals you specify, enable Reminders. For more information, see Assign a task to multiple users fields, buttons, and settings.

  2. If you want to escalate the action and send the task to the recipient you specify, or complete the task with an Autocomplete outcome, enable Escalation. For more information, see Define the task escalation.

Assign a task to multiple users fields, buttons, and settings

Section

Field Description

Variable types

(Unlabeled)

 

Task name

The name of the task. See Tasks.

Text, Decimal, Integer, Boolean, DateTime, Collection

Task description

Description of the task the action sends to the assignee.

Text, Decimal, Integer, Boolean, DateTime, Collection

Task type

Task form

Allows you to design and save a task form for the action. You can use this task type when you want to collect information. For example, use a task form to collect information from a new employee or for a support ticket. Users can respond to the task via My Nintex, Nintex Mobile, or by clicking the form URL in an email. This task type can also be used in conjunction with the Express approval task type.

Click Design form to open the forms designer.

Note: After you design a form and apply changes, this changes to Edit form in the configuration panel. You can then click Edit form to make additional changes to the task form.

(n/a)

Disable send email When enabled, task email notifications are not sent to assignees. This option doesn’t apply to Express approval tasks and isn’t displayed when the Express approval toggle is enabled.  
Express approval

Use this task type when you need a simple outcome from users, like Accept or Reject. Users who respond via email can also enter comments (up to 500 characters) with the task response.

Note: 
  • Sensitivity labels in email messages are not supported and will result in an invalid response to the task.

  • If your Express approval task response emails are not allowing user comments in a workflow that you previously created, disable and re-enable the Express approval task type for the task.

You can also use this task type with an action with only one branch when assignees do not need to select an outcome, but are required to acknowledge that they have completed the task. For example, use this task type with one branch (no multiple outcomes) if you simply need users to acknowledge a task.

When Express approval is enabled, the Smart response detection toggle is displayed. This is available only if the feature is enabled in the AI features for the tenant.

When Express approval is enabled and Multiple outcomes is disabled, the Outcomes are not displayed and you can specify the Express approval term.

When Express approval is disabled and Multiple outcomes is enabled, you can configure the action to allow assignees to select an outcome.

Users can respond to the task via My Nintex, Nintex Mobile, or by replying to an email. This task type can also be used in conjunction with the Form task type.

(n/a)
  Smart response detection

Displayed when the feature is selected in the AI features for the tenant and the Express approval toggle is turned on for the action.

Enable the toggle to turn on smart response detection for express approval task responses. With this enabled, task responses from assignees don’t need to be an exact match to one of the Express approval terms. Smart response detection will analyze and evaluate the response, considering things like the tense, spelling mistakes, and similar terms, and select the closest approval term.

Smart response detection requires a certain confidence level to function effectively. If the response doesn't meet that level and seems too unclear, it's taken as an invalid response. The task assignee will get an email about the invalid response and is asked to respond again.

(n/a)
Outcomes

Multiple outcomes

Enable to allow task assignees to choose from multiple task response options. Each outcome has its own branch in the action.

When Multiple outcomes is disabled and Express approval is enabled, the Express approval term field is displayed, which requires assignees to respond with the Express approval term.

Note: Disabling Multiple outcomes deletes all branches and contained actions, and causes any form rule that references the outcomes to error.

(n/a)

Express approval term

This field is displayed only when Multiple Outcomes is disabled and Express approval is enabled.

The message that you want an assignee to respond with after completing a task.

The Express approval term you specify is displayed in the Footer text of the email that is sent to assignees. For information about what's displayed in the footer, see Footer text.

Text

Outcomes

The possible responses for completing the task.

The outcomes you define here determine the branches of the action.

By default, the Assign a task to multiple users action creates Reject and Approve outcomes. You can add, edit, and delete outcomes. To edit an outcome name, type in the outcome name field.

If you add a new outcome, another branch is added to the action. The outcomes appear as options in the Required outcome and Default outcome drop-downs.

(n/a)

Add outcome

Click to add task outcomes.

If you add a new outcome, another branch is added to the action.

If you add an outcome while Multiple outcomes is disabled, the Multiple outcomes toggle switches to enabled.

The maximum outcomes that you can add is 30.

(n/a)

Delete icon

Deletes an outcome.

The Delete icon is displayed only if you define more than two outcomes.

(n/a)
Completion rules

The rule that determines the overall outcome of the task based on the response from assignees.

Select one of the following options:

  • All assignees must respond: A task is completed when all assignees respond. The workflow proceeds using the outcome with the majority of responses. For example, if the majority of the assignees respond with Approve, then the workflow will use the Approve outcome.

    In the case of a tie, the outcome received with the first response is used. For example, if the outcomes are Approve and Reject and an equal number of three responses are received for both outcomes but the first response received is Reject, then the workflow uses the Reject outcome.

  • First response completes the task: A task is completed when one assignee responds. Without waiting for more responses, the workflow will proceed using the outcome from the first response. For example, if the first response received is Reject, the workflow proceeds using the Reject outcome immediately.

  • Wait for a specific response: The task will wait until the required outcome is received. If the required outcome is not received, the default outcome is used. For example, there are three outcomes, Approve, Reject, and Review, and the default outcome is Review. If the required outcome is Approve but all assignees respond with Reject, then the workflow will use the Review outcome.

    The Wait for a specific response rule is available only if Multiple outcomes is enabled.

  • Wait for percentage of a response: The task will wait until the required percentage of the required outcome is achieved. If there are no outcomes, the task will wait until the required percentage of responses is achieved. For example, if you need 60% of assignees to agree on an outcome, and you set the required outcome to Approve, then the task will wait until 60 percent of the assignees respond with Approve outcome.

Note: The Default outcome, Required percentage, and Required outcome fields that are displayed depend on the completion rule you choose.

(n/a)
Default outcome

The outcome to use if the required outcome is not received or if the required percentage of a response is not achieved.

The Default outcome field is displayed only if you select one of the following completion rules:

  • Wait for a specific response

  • Wait for a percentage of a response

(n/a)
Required percentage

The percentage of a specific response from assignees that must be achieved.

The Required percentage field is displayed only when you select Wait for percentage of a response.

Integer
Required outcome

The response that must be received or achieved before a task is completed.

The Required outcome field is displayed only if Multiple outcomes is enabled and options for the required outcome depend on the outcomes you specify.

(n/a)
Assignee Assignee authentication
  • Enable (enabled by default): The assignees must sign in to Nintex Workflow to access the task form.
  • Disable: The assignees can access the form without signing into Nintex Workflow

If Assignee authentication is disabled and Express Approval is enabled, the Verify responder's email address is displayed.

(n/a)
Verify responder's email address

Requires assignees to respond only from their email address. Responses received from other email addresses will not be accepted.

This field is available only if you enable Express approval and disable Assignee authentication.

 
Assignees

Recipients of the task.

Type in the Assignees field to filter and select users. Use semicolons to separate multiple email addresses.

Note: 
  • You can search for and select up to 20 users.

  • Tasks are sent to assignees, depending on the selected assignment behavior.

Tip: If using a variable in the Assignee field, we recommend using the assignee's email address in Text format. Searching for a user's first name and last name may not return a unique value, causing the action to fail.

Text, Collection
Assignment behavior

The order that a task is assigned to users.

  • Parallel: assign to all users at the same time: Tasks are assigned to all users at the same time.

  • Sequential: assign to users one at a time: A task is assigned to the next user only after a response is received from the current user.

(n/a)
Message

Sender display name

The From name in the email that the action sends. The sender display name is followed by the default sender.

For example, if your Sender display name is "Marketing Team" and the default sender is nintex@workflowcloud.com, the From field in the email displays as: Marketing Team <nintex@workflowcloud.com>.

If you don't enter a sender display name, then the email shows the default sender in the From field.

Text, Decimal, Integer, Boolean, DateTime, Collection

Cc recipients Email addresses for the Cc line in the email message sent by this action. Cc recipients receive a copy of the task email, and all recipients can see who was included in Cc. Use commas or semicolons to separate multiple email addresses. Do not select a null variable.
A maximum of five recipients are supported. If more than five addresses are added, only the first five will receive the email.
Text, Decimal, Integer, Boolean, DateTime, Collection
Bcc recipients Email addresses for the Bcc line in the email message that the action sends. Bcc recipients receive a copy of the task email, but their addresses are hidden from all other recipients. Use commas or semicolons to separate multiple email addresses. Do not select a null variable.
A maximum of five recipients are supported. If more than five addresses are added, only the first five will receive the email.
Text, Decimal, Integer, Boolean, DateTime, Collection

Subject

Subject of the email message that the action sends.

Text, Decimal, Integer, Boolean, DateTime, Collection

File attachments

Variables representing files to attach to the email that the action sends.

Collection, File

Message body

Body of email message that the action sends. To expand the message body window and to see more options in the toolbar, click (Expand editor).

Text, Decimal, Integer, Boolean, DateTime, Collection

Footer text

When the toggle is enabled, footer text is automatically added to the end of the message body in the email that the action sends. The footer text that is included is based on the task type.

  • Task form: You may complete this form: [URL link to form].

  • Express approval with multiple outcomes: You may reply to this email with: "Reject", or "Approve" followed by a comma and any comments.

  • Express approval with one outcome (no multiple outcomes): You may reply to this email with: "Proceed" followed by a comma and any comments.

  • Express approval with one outcome (no multiple outcomes) and Task form:  You may complete this form: [URL link to form], or you may reply to this email with: "Proceed" followed by a comma and any comments.

  • Express approval with multiple outcomes and Task form:  You may complete this form: [URL link to form], or you may reply to this email with: "Reject", or "Approve" followed by a comma and any comments.

This footer text cannot be edited. If you want to add your footer text, disable the Footer text toggle and append the required footer text to the end of the message body.

When the Footer text toggle is disabled, the email the action sends does not automatically include footer text after the message body. You can add your own Task form links using variables so your assignees can access the forms and respond appropriately.

(n/a)

Reminders

 

 

 

 

 

 

Reminders

When you enable Reminders, the action sends reminders to the assignees at intervals you specify.

When you do not enable Reminders, reminders are not sent to the assignees.

Example: If you enable Reminders, set Number to 1 and Unit of time to Hour(s), a reminder will be sent 1 hour from the start of the task assignment.

(n/a)

Number

Displays when you enable Reminders.

The quantity of Unit of time before the action sends the first email reminder to the assignees.

Decimal, Integer

Unit of time

Displays when you enable Reminders.

Time unit used with the Number field for the first email reminder.

(n/a)

Customize email

Displays when you enable Reminders.

Presents the Custom email section and fields for reminder emails the action sends. See the Subject, Message body and Footer text information above.

(n/a)

Subsequent reminders

When you enable Subsequent reminders, the configuration panel presents additional Number and Unit of time fields. The action sends subsequent reminder emails for the task to the assignees as frequently as you define in the Number and Unit of time fields until the task is completed.

When you do not enable Subsequent reminders, the action does not send additional reminders for a task.

Example: If you enable Subsequent reminders, set Number to 2 and Unit of time to Hour(s), subsequent reminders will be sent for every 2 hours after the first reminder.

(n/a)

Number

Displays when you enable Subsequent reminders.

The quantity of Unit of time before the action sends subsequent email reminders to the assignees.

Decimal

Unit of time

Displays when you enable Subsequent reminders.

Time unit used with the Number field for the subsequent email reminders.

(n/a)

Escalation

 

 

 

 

 

Escalation

When you enable the Escalation toggle, the configuration panel presents additional fields. The action escalates and sends the task to the recipient you specify, or completes the task with the selected Autocomplete outcome.

By default, Use date variable is selected, which presents Due date and Escalation assignee fields.

When you do not enable Escalation, the action does not escalate nor autocomplete.

(n/a)

Use date variable / Calculate date

Select to either use a date variable from your workflow or a set amount of time after the task is first created to escalate the task.

This is selected, by default.

(n/a)

Due date

Displays when you select Use date variable.

The date the action escalates or autocompletes the task.

DateTime

Number

Displays when you select Calculate date.

The quantity of Unit of time before the action escalates or auto-completes the task.

Example: If you enable Escalation with Calculate date, set Number to 2 and Unit of time to Hours(s), an escalation email will be sent 2 hours after the start of the Assign a task to multiple users action.

Decimal

Unit of time

Displays when you select Calculate date.

Time unit used with the Number field for the escalation email that is sent to the assignees.

(n/a)

Activity on due date

Defines the activity that occurs when an assignee fails to respond to a task by the due date. Select one of the following:

  • Escalate: Escalates and sends the task to the Escalation assignee.

  • Autocomplete: Applies the Autocomplete outcome to the task on the due date.

(n/a)

Escalation assignee

The recipient of the task escalation.

This field is displayed only when Activity on due date is set to Escalate.

Text

Customize email

Presents the Custom email section and fields for escalation. See the Subject, Message body and Footer text information in the Message section above.

This field is displayed only when Activity on due date is set to Escalate.

(n/a)

Autocomplete outcome

The outcome that is applied automatically when an assignee fails to respond to a task.

These are the options for the Autocomplete outcome:

  • If Multiple Outcomes is enabled, you can choose the Autocomplete outcome from the list of outcomes that are identified in the Multiple outcomes section.

  • If Multiple Outcomes is disabled and Express approval is enabled, the Express approval term is selected automatically as the Autocomplete outcome.

  • If Multiple Outcomes is disabled and Express approval is disabled, the Autocomplete outcome is automatically set to Autocompleted.

This field is displayed only when  Multiple Outcomes is enabled, Escalation is enabled, and Activity on due date is set to Autocomplete.

When a task is autocompleted, the status of the task in the Tasks page is displayed as Autocompleted.

(n/a)