@Akhila 

Please have a look at this Docusign Developer article. The section “Handle agreement events” describes the event handlers. The sessionEnd event that you need to use after signing is completed.

@Michael.Rave

Thank you for your reply Michael, I have read this Docusign Developer article and tried using Focused view but I’m getting Violation Error like lviolation] permission policy violation: “Geolocation access has been blocked because of permission policy applied to the current document” while integrating DocuSign with our angular application using focused view.

Could you please help me for clearing this policy violation error.

error:

Refused to frame 'https://developers.docusign.com/' because it violates the following Content Security Policy directive: "frame-src 'self' https://docucdn-a.akamaihd.net/ https://apps-d.docusign.com https://demo.docusign.net https://account-d.docusign.com https://proof-d.docusign.net https://identity-d.docusign.net https://azure-demo.docusign.com https://content.googleapis.com https://docs.google.com https://players.brightcove.net https://www.youtube.com https://accounts.google.com https://docusign.sjv.io https://apps.usw2.pure.cloud https://docusign.co1.qualtrics.com/ https://sawmill-stage.docusigntest.com https://docusign.okta.com https://demo.forms.docusign.com".

Thanks and Regards,

Akhila.

Thank you for your message, @Michael.Rave. I have read the DocuSign Developer article and tried using Focused view, but I am encountering the same policy violation error as Akhila when integrating DocuSign with our application using Focused view.

Refused to frame <return url> because it violates the following Content Security Policy directive: "frame-src 'self' https://docucdn-a.akamaihd.net/ https://apps-d.docusign.com https://demo.docusign.net https://account-d.docusign.com https://proof-d.docusign.net https://identity-d.docusign.net https://azure-demo.docusign.com https://content.googleapis.com https://docs.google.com https://players.brightcove.net https://www.youtube.com https://accounts.google.com https://docusign.sjv.io https://apps.usw2.pure.cloud https://docusign.co1.qualtrics.com/ https://sawmill-stage.docusigntest.com https://docusign.okta.com https://demo.forms.docusign.com".

Could you please help us resolve this policy violation error?

Thanks and regards,

@Akhila @lvincent 

Unfortunately not, as I do not have any personal experience with deploying Web Forms or how to handle policy violation errors. 

I suggest to open a Docusign Support ticket to reach out to the API/Development teams to help you resolve the specific error message regarding Geolocation. There is an option related to geolocation in the Docusign Signing resource file, which allows to enable or disable that feature. Maybe changing the setting may help?

Not sure if you can include the “https://developers.docusign.com” in the policy below, where it does not seem to be listed alongside all the other URIs.

@Akhila were you able to figure out on getting the signer response back to our angular app after signing the document from focusView or Iframe? appreciate your time.