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 ideas@nintex.com

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact sales@nintex.com

Add a new idea Subscribe
Status Already Exists
Workspace K2 Cloud
Categories Management
Created by Danny Knudsen
Created on Apr 28, 2022

RELATED IDEAS

Disable SmartActions on Specific Workflows

We would like to be able to disable SmartActions on individual workflows. We want to prevent users from being able to reply to the notification emails with "Approve" without even opening the form for review. It's fine in some scenarios, but can allow the users to circumvent validation procedures in others.

Currently this appears to only be on or off for the entire instance. Thanks.
  • Attach files
  • Admin
    Codi Kaji
    Reply
    |     Apr 17, 2023

    Thanks Danny for your feedback! You can customize the task notification email per user task and remove the sections for actioning your task via email. By removing the task serial number, even if the end user does reply to the task notification, the workflow server will not process the task via email. This can be configured per task, thus allowing you flexibility in which tasks can be responded to via email and which only have the link to the worklist item. Hope this helps!

  • Harm Wieringa
    Reply
    |     Oct 5, 2022

    Can you give an example where for one instance you would allow a SmartAction and another where you would not want this? I find it difficult to see for the same Task when you would want to make a difference in the way the user can interact.

    If you would have a way to disable it on-demand, you would need a mechanism to decide if the setting is to be toggled on or off. As an alternative to this, maybe you can use a Decision step using that mechanism and create a separate path with the same Task? In one path you have the setting enabled and in the other you set it to disabled.