Skip to Main Content
Nintex Ideas

đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!

If you have questions about Nintex Ideas, please contact

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact

Status Open for voting
Categories Workflow Designer
Created by Guest
Created on May 30, 2024

Assign a Task Escalations should be targeted, not inclusive of all assignees

Assign a Task Escalations (not reminders) could/should serve as an SLA guardrail, allowing an escalated alert to be sent to a supervisor, oversight group, etc...however, because the Escalation includes all original assignees, this limits the use as we do not want the client (Requestor, initiator, individual who completes the Form that starts the workflow) or the associate(s) to whom the task was assigned to be notified of a potential SLA breach.

While there are examples when copying everyone makes sense, there are also many cases in which this escalation should be limited/targeted to specific individuals or groups.

Utilizing separate emails (requiring separate entry for all emails to be included in the Escalation email, rather than automatically copying the "Assigned to" Emails from the task) for the Escalation (not collecting emails from the task assignment) might allow for the Escalation to function both ways.

  • Attach files