Hi, I believe you need to publish the process for the new owner/expert/approver to show, then resubmit for approval and it should go to the right line of approval. 

Thank you Stapleer for your reply.  I had considered doing this, but as the process has not ever been published it seems odd we would need to publish it, edit it, then republish it for the change to ‘stick’.  This makes for a very messy change log.

Draft form really should be draft form until the point of publishing for general consumption.  Once you have a version greater than 1.0 I could understand doing this for the approval workflow to action appropriately.  But UNTIL we have a published version this feels very clunky, and more of a work around than standard practice.

Yes I agree - the way around this being published without review would be to send to the new approvers to review separately, once they have given approval you could then publish a confident process.  Other wise what I have done is publish it with the comment in the change log reflecting why this would be the case.  Keen to know if there is another way as well. 

I agree and feel your pain! I reported the issue to support but the response was that it is working as intended, which makes no sense. However, they did propose a workaround. I haven’t tried it yet, but if you edit the originally designated Owner/Expert in “Users,” then use the “Transfer” button next to Process or Processes and select and transfer only the process you want to reassign, this is supposed to get around the problem.

Thanks Tonyajeank - I appreciate that.  That workaround seems an awfully long way to go about it, but would have been a better option than publishing it, editing it, then resubmitting for approval.  Oh well, something to try for next time! :D 

I agree with this, it is not practical to first approve the “approver change/update”, so the new approver can approve. It sound’s messy and not logical at all.