Skip to main content
Nintex Community Menu Bar
Question

Dashboard: Processes for Publishing

  • March 5, 2025
  • 1 reply
  • 61 views
  • Translate

staciakato
Forum|alt.badge.img+2

This may be a recent issue, but I wanted to see if anyone else noticed it? 

I’m familiar now that the processes that land in the Dashboard: Processes for Publishing are ones that have an error in them that requires a Promaster to check. For example, the editors may have submitted for approval a process that has links to an archived process. That would be an error and it has been up to us Promasters to help the editors resolve the error. 

Recently, I noticed a process that had such an error (output link to an archived process), both editors had approved, and it didn’t land in the Processes for Publishing queue, but rather stayed in the Processes for Approval queue with just a Publish Now button. 

Curious if anyone else noticed this behavior within the Promaster’s view of the My Dashboard?

Did this topic help you find an answer to your question?

1 reply

BrettHutchinson
Nintex Employee
Forum|alt.badge.img+8

I don’t believe Nintex has a way of knowing if a process has an error or not. Processes don’t route to Publishing because there are errors (unless that is new, and I’m out-of-date). Processes go to Processes in Publishing if you require publishing as part of your approval workflow. This can happen if you have publishers set on a Process Group folder, or your settings require it. You can also have Publishing skipped if desired.

As Promaster, you may also have rights to override processes in the Approval Queue with the Publish Now button, if that setting is enabled as well.

But here is the help documentation to learn more: https://help.nintex.com/en-us/promapp/PAW/PAW.htm

And specifically, here where you can Publish (it may also been a caching issue or some similar display, hard to know exactly imo without the example): https://help.nintex.com/en-us/promapp/PAW/Approve.htm#:~:text=Do%20one%20of%20the%20following%3A

 

If you see it consistently happening and believe it is in error, please raise a support ticket for investigation. There have been dashboard updates so this could be a potential side effect of a release as we are modernizing our action dashboard :).

Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings