Docusign 2024 Release 3 Is Live! Discover the New Capabilities
Find answers to your Docusign Embedded Signing questions.
Recently Active
We require embedded signing functionality within a customer portal mobile application. The signer will log in to the mobile app and complete the signing process through an embedded signing experience using an iframe. Is it feasible to implement IDV Liveness for signer identification within this iframe?
Hello DocuSign Community, My teammate and I are participating in the DocuSign "Unlocked" Hackathon, and we’re working on a project to enhance the signing process by introducing interactive document features. Specifically, we are trying to add the ability to:1. Highlight specific sections or lines in a document to draw users’ attention to key details. 2. Display contextual bullet points or notes alongside the document to provide additional guidance or explanations. We’re exploring how to best integrate these features into the signing flow using embedded signing. At this point, we’d love some guidance on:- Whether embedded signing is the right approach for implementing such dynamic features. - Any tips, tools, or APIs within DocuSign that could simplify this process. If you’ve worked on enhancing the signing experience or have insights on building customizations like this, your advice would be greatly appreciated!Thank you for your time and help!
Hello everyone,Im not really used to docusign, i work in a project where there is some screen with a docusign iframe, and recently there is a new popup modal that appear in the modal (it didnt before) that i dont want to show, any idea how to avoir it please ? English trad of the popup : check and continueHello, please consult a new document converning ...
Hello, I’m trying to display the embedded signing view using DocuSign's focus view, but I’m encountering an issue. Here’s the screenshot and the error message from the console log. This is occurring in my local environment. Could someone please help me understand why this is happening? Below is an example of the code I’m using. I’d really appreciate it if you could point out anything I might be doing wrong. Thank you!
Unlike with EnvelopeViews:createRecipient, which has options to configure clickjacking protections via x-frame-options or csp frame-ancestors, there are no such options for the createSender view.Due to this when displaying the sender view within an iframe element the browser blocks the request.How can we add Clickjacking protection to the embedded sender view to avoid this and add security.Here’s an example of the error on Firefox:
In my application i am using iFrame to display the docusign embedded view.i am able to complete the sign and read the event and perform operations and navigations in my app successfully in local environment. But the issue is when this is tested in production environment, I am able to sign and redirect url is being called giving 200 response but nothing is happening after that. same code is working fine with local environment and failing in production environment. I am not understanding is it because of any configuration issue or what.The difference I could see in the network requests is below request is failing. I don’t know exactly this is the problem. PFA belowI am using react router Route to handle the docusign url redirection like below<Routepath={urls.docusignComplete}component={() => <CustomDocusignCallback />}/> In the CustomDocusignCallback component, i am handling the event and calling backend api to update the document status and after that navigating back to
Hello,I’ve been trying all weekend but I just cannot get this to work, so hopefully the experts here and guide me through what I’m missing. I’ve tried a number of combinations and nothing is working. What I want to do, is create an In Person Signing event, where the delivery driver (under the host account) signed the document saying he has delivered the shipment, and then passes the device to the customer for them to sign their portion. In a mockup, I got it to work but I can’t get it to work in a full run through with an embedded signing request with the PHP SDK.Heres what I got:$document = new DocuSign\eSign\Model\Document( [ 'document_base64' => base64_encode($file_content_in_bytes), 'name' => 'TestFile', 'file_extension' => 'pdf', 'document_id' => '1' ] ); //Find Driver Area $deliverySignature = new DocuSign\eSign\Model\SignHere( [ 'anchor_string' => 'Signatu
When the user clicks on the finish button after signing the document, I want to show a pop up message while staying on the page. Is it possible to do?
We have built an integration with DocuSign, which essentially shares the envelope with the signer via our (Zingly’s) application.This is good, because it keeps the engagement between sales and service reps and their customers in the workspace. Having said that, in addition to the signer (customer) being notified that they can review and complete signing via Zingly, we would like to ensure the signer continues to get their “An envelope has been shared with you to review and sign” email from DocuSign.HOWEVER -- it appears that with DocuSign integrations (such as embedded signing), the integrations SUPPRESS all but the “completed signing” emails. (See link: https://support.docusign.com/s/articles/Why-aren-t-my-signers-receiving-DocuSign-Notification-emails?language=en_US)Can someone confirm whether embedded / integrations CAN or CAN NOT allow DocuSign’s native email / sms notifications to the signers to continue, in addition to the embedded integration?
I created an app to prove the Docusign JS embedded signing with Focused View. I am using C# at the server and JS/jQuery at the client. I followed all of the steps in the article “How to request a signature using focused view” (https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-focused-view).Everything on the server side is fine, but when the JS code runs to load the document for signing, I get the following permission errors:Refused to frame 'https://apps-d.docusign.com/' because it violates the following Content Security Policy directive: "default-src 'self' https://js-d.docusign.com/". Note that 'frame-src' was not explicitly set, so 'default-src' is used as a fallback. Refused to connect to 'http://localhost:49618/05e7fec…/browserLinkSignalR/…ationData.browserId&browserId=b7e3-320d&clientProtocol=1.3&_=1728595245739' because it violates the following Content Security Policy directive: "default-src 'self 'https://js-d.docusign.com/". Note that
When trying to create recipent view url from an envelope created from a template i recieve this error.How does one idenify the valid recipient? UNKNOWN_ENVELOPE_RECIPIENTThe recipient you have identified is not a valid recipient of the specified envelope.using PHP SDK $envelopeDefinition = new EnvelopeDefinition();$envelopeDefinition->setEmailSubject("Please Sign this Document");$envelopeDefinition->setTemplateId('f8c7bf7d-xxxx-1201e093fdc9');$envelopeDefinition->setStatus('created');$envelopeDefinition->setTemplateRoles([$signerTemplate]);$recipient_view_request = new RecipientViewRequest([ 'assertion_id'=> $assertion, 'authentication_method' => 'none', 'client_user_id' => $GLOBALS['JWT_CONFIG']['ds_impersonated_user_id'], 'return_url' => 'https://localhost', // Where to redirect after signing 'user_name' => $name, 'email' => $email,]);try { $envelopeSummary = $envelopesApi->createEnvelope($accountId, $envelopeDefinition); echo
Hello,I have integrated the Docusign signature for my customer orders via the Focused view mode.However, I encounter 2 problematic issues:1. The buttons are not translated into french even though the default language of my account is set to french. Via the JS setting, we can only change the last button but all the others and the start popup are in english. Is it possible to choose the language somewhere?2. The zoom on the documents by default does not suit me.It is too high and I do not know how it is calculated.Is it possible to adjust it in one way or another?Thanking you in advance for your answers,Regards,Flav
We are successfully using the embedded view “default” style to allow our users to sign documents, and then proceed onto the next step. However, we do allow the user to refresh the page and get back into the “signing step”, and that works well, except if it has already been signed. When the document is signed, and the page is refreshed, we successfully show the document again, and this time instead of “Sign” or “Finish”, Docusign UX displays “Close”. When that “Close” is pressed, the “endSession” event isn’t triggered as normal, but the nested iFrame is destroyed. This workflow does works well with the “focused” style in all cases (meaning that by just changing “displayFormat” to “focused” it fixes the issue), however, we would like to use the “default” UX. How could we have “endSession” trigger when pressing “Close” on an already signed document?
Back to Docusign.com
