0
votes

When the user redirected from docusign to my app, docusign append an event.

The event parameter will have one of the following values:

  • cancel (recipient canceled the signing operation)
  • decline (recipient declined to sign)
  • dexception (an exception occurred)
  • dfax_pending (recipient has a fax pending)
  • dsession_timeout (session timed out)
  • dsigning_complete (signer completed the signing ceremony)
  • dttl_expired (the time to live timer expired)
  • dviewing_complete (recipient completed viewing the envelope)

So few days before when user sign the contract it returned correct event=signing_complete, but today I noticed that in the same scenarion it returns me event=viewing_complete.

Is it bug or not, that instead of signing_complete I get viewing_complete as it was before? Because I have some check accordingly to this event

1
What is the question? - Robert
@Robert Is it bug or not, that instead of signing_complete I get viewing_complete as it was before? Because I have some check accordingly to this event - VitaliB
We also started seeing this yesterday. Seems to be limited to sandbox environment, at-least for us. - 343_Guilty_Spark
@343_Guilty_Spark, yeah also reproduced it on demo account I'm not able to test it on live account. So I hope that it works there - VitaliB

1 Answers

1
votes

The correct behavior is event=signing_complete, as you stated above. There is a patch that will be a DocuSign needed to address this, I do not have an ETA.