You are viewing limited content. For full access, please sign in.

Question

Question

Send back for Modifications

asked on May 28 Show version history

I have a process that send tasks in parallel to 3 user tasks. If any one sends it back for resubmission, it needs to route to just that person again for approval. What is the best way to achieve this.

0 0

Replies

replied on May 29

If a resubmission is requested, should the other two tasks be terminated or can they still approve, deny, request a resubmit?

1 0
replied on May 29

Thanks. The other two tasks cannot be terminated, they need to be able to approve/deny/resubmit. 

0 0
replied on May 29

If its internal, you could set a loop with each approver and assign it back to the initiator.  Within the parallel they can go back and forth until its approved or denied until all 3 are done and the gateway closes. 

If you truly want them to start a new instance and resubmit the entire form again you could use hidden fields to store the approvers credentials, send the form to WF and use Invoke Business process to start a new form, assign it to the initiator of the original form and route to the right approver based on the stored credentials.  Just use gateways in your BP to route as either a starting submission or a resubmission.

I think the route you choose depends on whether this is an internal vs external submission and if you want corrections vs a brand-new instance.  

2 0
replied on May 29

Thanks so much.

0 0
replied on May 29

There are probably multiple ways to tackle this, but I would probably have the approval decision as a radio button instead of using the system buttons. Then, if they select "Return for Correction" as that radio choice, I'd set a hidden field to a value that I could use in my routing decision later on.

So... approver marks their decision as "Return for Correction," hidden field gets set to "TRUE" (or whatever - if you're using the Modern Designer, you should consider also making the Task Comment Box required with this selection), the process routes the form back to the Initiator, the form is resubmitted, and it returns to a Gateway where the condition is "if that hidden field is TRUE, route to approver."

I hopefully explained that well. Others may have different suggestions, but that would be my approach.

0 0
replied on May 29

Thanks.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.