Hi Community!
Recently, in two separate workflows, I changed the counterparty signer [from the Ironclad workflow] midway through the signature process after our side signed, and the [DocuSign] signature packet was not cancelled and the document was automatically rerouted to the new signer for signature!
I haven't seen this update in any support articles so I wanted to know if this is a new and permanent product update? Anyone experience the same thing?
I'd also like to suggest an IDEA for this change: include the activity of the reroute in the activity feed of the workflow. When I first made the change, I was expecting the signature packet to be cancelled and it wasn't, but I also didn't see anything in the activity feed of the workflow that would indicate that the document was successfully rerouted to the updated signer, so I wasn't sure what was going on [i.e. if it was a bug/if the counterparty actually got the document to sign. Therefore, it would be super helpful if the activity feed was updated accordingly with this new process.
Best,
Lynn
@Joe_Nguyen
