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

If you require support, please visit Nintex Customer Central

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

Status Completed
Categories General
Created by Guest
Created on Aug 9, 2019

Declining approval or publishing request by at least one Promaster should return process to draft or edit state

If a Promaster declines or rejects an item in the approval/publishing queue, the item should be returned to draft/revision state, preferably with a notification to the owner/expert on why.

Current state is that ALL Promasters must decline/reject item before it disappears from approval/publishing queue. This leaves the item open for accidental approval or publishing.
  • Attach files
  • Michelle Pavel
    Reply
    |
    Sep 7, 2022
    Our process owners are responsible for approval/publishing of processes and the Promaster is only for backup if an owner is away and a process needs to be published. We ignore our list of processes for review or approval on the Promaster dashboard, as they are not our responsibility. We put the ownership onto the business for that.
  • Guest
    Reply
    |
    Sep 7, 2022
    This change would be amazing, current behavior is cumbersome and not scaleable... we have dozens of such processes where 1 promaster has declined and it shows on all other promaster dashboards. we could easily have hundreds of processes in this state in the future

    BTW not convinced that it goes away when all promasters coordinate a "decline"
  • Anne
    Reply
    |
    Sep 7, 2022
    Any update on this? The decline process is still cumbersome.
  • Guest
    Reply
    |
    Sep 7, 2022
    It's odd that "Declined" comments show up as negative feedback on the process which need to be responded and closed by the Process Owner and Process Expert.
  • Guest
    Reply
    |
    Sep 7, 2022
    Definitely need this improvement. It gets in the way of efficient publishing.
  • Tim
    Reply
    |
    Sep 7, 2022
    I would add that this new behaviour should have a toggle in the config settings, it is a good thing to have but not everyone will want it to work this way, I think.
  • Guest
    Reply
    |
    Sep 7, 2022
    Timing TBD in August 2019 - any updates? It is 2021. There are multiple open suggestions for this same thing with various votes. The votes should all be added to one enhancement or at least linked together to see the high interest in fixing this issue.
  • Guest
    Reply
    |
    Sep 7, 2022
    This would be a handy addition to the decline function. Right now, we have two Promasters and things sort of linger around after they are declined.
  • Guest
    Reply
    |
    Sep 7, 2022
    Please update us on this implementation.