venuraju's account

Hi Duo,

Thanks for the quick reply!

-Venu

Hi Duo,

Follow-up question:
If I have signer and a co-signer, signing one after the other, which event gets triggered after the first signer completes signing? In other words, how do I identify that one signer has completed signing, and now it is co-signer's turn?

Thanks,

-Venu

Hi Duo,

We are planning for two different flows:
1) Hybrid flow: Signer, co-signer, sender, in that order: First signer will sign in an embedded flow. Co-signer will sign through an email link. Once these two are complete, (me as a) sender will sign last.

2) All remote:  Signer, co-signer, sender, in that order: Signer will get email and complete signing. Then co-signer will get an email to complete the signing. And finally, the sender will sign.

In both flows, we would want to know the status of the package at any given point of time. For example, if the package is waiting for co-signer for more than a day, we would want to initiate a follow-up call/email.

Does package (packageId) contain one "sessionUser" for each signer? In the webhook event payload, I do see these attributes. How do we map these attributes back to signer, co-signer or sender?

Thanks,

-Venu

Hi Duo,

Thanks for all the details. Will take a look.

-Venu

Never mind. The tool worked after I happened to restart my machine!