Skip to main content

I have an application that I am connecting to DocuSign esignature and connect. I have configured connect event to for recipient signed/completed and reassign. When a recipient signs the envelope it is working fine and sending a recipient-completed action via connect. However, when I reassign via the email sent as part of the envelope - connect sends a recipient-completed event for the initial signatory, immediately followed by a recipient-reassign event. I would expect it to only send the reassign event. 

 

Is there a way to configure it to only send the reassign event in this scenario? Or is it possible in the recipient-completed event to tell whether the recipient actually signed or not?

@AllieOlson 

  • No—there is not a way to configure DocuSign Connect to send only a reassign event when a user reassigns instead of signing.
  • Yes—it is possible to determine from the event data that the recipient did not actually sign, by examining the Connect payload details. Typically, you’ll see that a reassign event follows shortly after the initial completion event. Combining both notifications will let your system accurately reflect “reassign” vs. “sign.”

When using DocuSign Connect and subscribing to both the Recipient Signed/Completed and Recipient Reassigned events, the behavior you are seeing (a recipient-completed event followed immediately by a recipient-reassign event) is normal and expected. In other words, DocuSign’s event pipeline will first emit that the previous recipient’s action is “completed” (insofar as that person is done with the envelope—whether by signing or reassigning) and then emit the reassign event.

Unfortunately, there is no configuration option in Connect to suppress the recipient-completed event in the case of reassigning. DocuSign always treats the reassign action as a completion of the current recipient’s role.


Reply