I've experienced this frustration as well. One option is to not use the built-in parallel transitions, use group specific approval transitions, then add a field to the data card that represent each approval group. Make the default values "Awaiting <group> Approval" then set up saved searches to monitor the fields with the value "Awaiting Engineering Approval" or "Awaiting Quality Approval" or "Awaiting Management Approval".
You can put these fields on a tab control that only the admin can see if you want to hide it.
Then share the saved searches with the teams...or use a dashboard to monitor those fields.
Hope this helps,
Looking at the workflow above, I see that you are not using notifications. Are you not utilizing automated notifacation somewhere in the workflow to tell users when their document is approved?
I ask because we do use them, and I don't see a good way to utilize the notifications with the custom built parallel workflow as once on of the approvers changes the state and it loops back to in review, when the next review changes the state, the previous review will get the notification instead of the person who submitted it for review. Toggling to send it to the creator only is also not an option as someone who is revising a document is not always the person who created it. I don't see any capabilty to utilize a variable to control who the notification goes to, and selecting an entire group is not preferable.
It appears there is a conundrum as I see folks complaining that the built in parallel transitions are not desirable because they don't notify users that approvals are occuring until all approvers sign off, in addition to not populating the fields correctly when selecting specific mapped approvers (at least in my experience for sure, but I have seen the complaint on a few other threads). Or go the custom route so you can get a notification each time it is reviewed. While yes, it does populate each approver field in real time, it doesn't appear doable to push notifications back to the orginal submitter for every reviewer that is required, only the first one.
Any thoughts on this?
Jason L., CSWP
PDM Pro 2018
All your points are spot on. And exactly why we went to a custom add-in to do notification emails based on card variables. Thanks Tim and your team!
I think 2019 has this built in: 2019 SOLIDWORKS PDM Help - Defining Conditional Notifications