Developer

HI Team, Can someone help me to Integrate DocuSign On my Application Below are the Details:-<add key="ClientId" value="" /><add key="Userid" value="" /><add key="AccountId" value="" /><add key="AuthServer" value="account-d.docusign.com" /><add key="RSAPrivateKey" value="”/>For Userid key - I used user ID from user profile For ClientId key :- I used Integration keyFor RSAPrivateKey :- I user RSA Keypair private key For AccountId key :- I used org

Hi Team,  I’ m integrating docusign Embedded Signing in React js Application.   I create below component : import React, {useEffect} from 'react';import PropTypes from 'prop-types';function DocumentSignUI({integrationKey, docUrl}) { useEffect(() => { const loadDocuSign = async () => { const docusign = await window.DocuSign.loadDocuSign(integrationKey); const url = `${docUrl}&output=embed`; const signing = docusign.signing({ url, displayFormat: 'focused', style: { /** High-level variables that mirror our existing branding APIs. Reusing the branding name here for familiarity. */ branding: { primaryButton: { /** Background color of primary b

How do I correlate from my WebApp DocuSign REST calls to the Splunk docusign index?  Docusign Event ID looks like the best correlation but I can not figure out how to get it from the response on my WebApp activity. --Steve Sample searchindex=docusign sourcetype="docusign:monitor"| eval json_payload=_raw| spath output=userId input=json_payload path=userId| spath output=user_action input=json_payload path=action| spath output=user_device input=json_payload path=userAgentClientInfo{}.device{}.family| spath output=user_device_model input=json_payload path=userAgentClientInfo{}.device{}.brand| spath output=user_agent input=json_payload path=userAgent| spath output=user_agent_family input=json_payload path=userAgentClientInfo{}.browser{}.family| spath output=signers_recipient_guid input=json_payload path=data{}.RecipientInfo{}.RecipientId| spath output=signers_recipient_id input=json_payload path=data

Unable to Connect with Coupa.I am using the same Email to connect with Coupa, but it keeps throwing “password/email invalid”

Hi, Summary: status not refreshed after correcting an envelope, setting another invalid email via API Explanation:Tested in the demo acountI have created an envelope containing 2 signers, putting an invalid email in the first signer. Through the API, I can get the ‘autoresponded:smtp; 550’ status, so I know I must correct the first email address.Using the API,when I correct the email address giving another invalid email address, the status remains ‘sent’, no matter what I attempt to do (UpdateRecipients with resendOption to true, Update with resend option or even resend through the DocuSign website)… Am-I missing something ? When I correct the first signer address through the DocuSign website, the ‘failed’ status of the second invalid email address is shown :

Dear Colleagues,My name is Mikhail Pliss, and I am the CIO of the startup Solify.me. We are developing a platform for solar panel installations in the US market. We require a solution that allows our customers to electronically sign contracts with us within their personal accounts on our website. Would you be able to assist us in implementing this feature? We anticipate approximately 1000 customers per year, who are homeowners interested in installing solar panels. They will register on our website using their email addresses.Thank you for your time and consideration.Sincerely, Mikhail Pliss CIO, Solify.me

Hi, I used the SDK for Java (Version 6.0.0) and i tried to use the function for Routing Order, but doesn´t works.  My Code IntStream.range(0, userSigners.size()).forEach(i -> {Signer signer = new Signer();signer.setEmail(userSigners.get(i).getEmail());signer.setName(userSigners.get(i).getName());signer.recipientId(String.valueOf(i+1));signer.setRoutingOrder(String.valueOf(i));signer.setTabs(tabs); signers.add(signer);}); Recipients recipients = new Recipients();recipients.setSigners(signers);recipients.setCurrentRoutingOrder("true");envelope.setRecipients(recipients); This is correct?

Hi, I am working on setting up an integration with Docusign for Salesforce, the last thing I did was update the token, then I tried to send an envelope and got the error message:  The specified Integrator Key was not found or is disabled. Invalid account specified for user” in a demo account.Checked in salesforce that integration key is matching with integration key is matching DocuSign account integration key. The below url I am using is this, please advise. Thank youDocusign Account URL https://account-d.docusign.com/oauth/token

I'm unable to connect in production mode.

 Hello everyone, how are you?I'm having this problem when sending a file to my client.I believe it is because the Co-Buyer or Co-Seller fields are not filled in, how can I do to remove the requirement to fill them in?   

Hi team, I have a Custom button calling screen flow in Salesforce. The flow is setup to “Send with DocuSign” as per below:  I have quite extension Screen documentation for errors, and the flow completes successfully:The envelope (related to the ID I’m using above) works when I execute it directly - however, when the flow completes, I don’t get any errors, it completes, but the Envelope is not sent. If I edit the envelope template ID slightly, the flow fails - so I knwo the ID is correct… Similiarly, I know the correct object is being sent through…Is it possible to get any feedback from the APEX action so I can tell if it worked or not. As you can see the fl

Hello everyone, We have Salesforce and DocuSign integration, I have a requirement to setup a DocuSign envelope template on custom object and that record is created by a guest user via a form on a cloud experience site. I designed the Record-Trigger flow on creation a record with a condition as in the screenshot below:  The flow is running well, but the DocuSign component is not sending the envelope and i can see the following error message in the debug log : Failed to process batch for class 'dfsle.EnvelopeConfigurationBulkSend' for job id '000Ty00000jkmnU' caused by: dfsle.UnauthorizedException: You must have DocuSign sender permissions to perform this operation Class.dfsle.Permissions.verifyIsDocuSignSender: line 414, column 1Class.dfsle.Permissions.verifyIsDocuSignSender

I am trying to use this example from the API request builder. As can be seen in this example, the signer 1 is not assigned any tabs (text1, text2).. All tabs (fields, checkbox etc) are assigned only to Signer2. Yet both Signer1 and Signer2 are able to see the data (values of text1 and text2 tabs) when the envelope is sent for signing. why is this happening? // DocuSign Builder example. Generated: Fri, 20 Sep 2024 21:06:56 GMT// DocuSign (c) 2024. MIT License -- https://opensource.org/licenses/MIT// @see https://developers.docusign.com -- DocuSign Developer Centerusing System.Collections.Generic;using System.IO;using System;using DocuSign.eSign.Api;using DocuSign.eSign.Client;using DocuSign.eSign.Model;namespace CSharp_example{    class Program    {        // Note: the accessToken is for testing and is temporary. It is only good for 8 hours from the time you         //       authentica

Hi Team,Could anyone help me with the following issue:I have to make the hyperlink clickable using createEnvelope API. The steps I have followed:Created one Anchor string on the PDF file with prefix #HREF. Configured that Anchor string as well with the same name. Then tried creating envelope with the above-mentioned file. When I have opened that envelope, I could see one link clickable but whenever I click on that link it is getting redirected to a blank page. Please refer to attached image below. Clickable Hyperlink

Hi Team,I am getting below error while invoking docusign  makeEnvelope  test@gmail.comcreatingEnvelopeAn uncaught exception occured!Error: Unauthorized    at Request.callback (/home/finacle/node_modules/docusign-esign/node_modules/superagent/lib/node/index.js:696:15)    at /home/finacle/node_modules/docusign-esign/node_modules/superagent/lib/node/index.js:906:18    at IncomingMessage.<anonymous> (/home/finacle/node_modules/docusign-esign/node_modules/superagent/lib/node/parsers/json.js:19:7)    at IncomingMessage.emit (node:events:539:35)    at endReadableNT (node:internal/streams/readable:1345:12) This works fine for me in local, however the same is failing through an application deployed in cloud.I have added redirect uri

I need to send a DocuSign Gen template using the Apex Toolkit within Salesforce. My goal is to automate document generation based on specific Salesforce records and trigger it programmatically. Need to incorporate Gen templates into the process. Are there any best practices, examples, or specific considerations when using Gen templates with Apex? Any guidance or code samples would be appreciated!

Getting Socket Exception while connecting the Production base path. It is running successfully with demo base path.We have followed the same set of procedure for creating RSA key and consent requirement completion.We are not sure, why it is getting Socket Connection reset exception and in detail exception shows “javax.net.ssl.SSLHandshakeException: Remote host terminated the handshake”Could any one please advise?

I’m trying to use the phone number auth for my python API. I’m already using the API to get the workflow ID and I’m getting this value:'c368e411-1592-4001-a3df-dca94ac539ae' However, I’m still getting this error:HTTP response body: b'{"errorCode":"IDENTITY_WORKFLOW_INVALID_ID","message":"The identity workflow ID specified is not valid."}' Any idea on this?Thanks!

I am in the process of building out a Connect webhook call to notify our app when a document is signed. This webhook goes through a proxy for security and resilience reasons and then on to an AWS API Gateway.the JSON payload for our Document is VERY large (38000 lines) due to lots of repeated fields with drop downs that themselves have lots of options.This has proven interesting in that one of the proxy’s scans for malware in the payload is taking 18 seconds. However, if I feed that payload through a json minifier it scans in about 1 secondI dontt have a way to test it as I cannot point the Connect config to our proxy because its not exposed to the internet and (as its a large corp) I cannot just put the proxy into a higher environment without lots of rigor.The payload I am testing with was copied from the Connect logs (UI) so I don’t fully trust that its a faithful representation of the payload formatting….so: Can someone tell me if the Connect pay

In the past few weeks account-d Docusign is broken, it does NOT happen in account DocuSign website. We use Java API and have not changed a single line of code in over a year, but in the past few weeks the MS Word .docx that we send to get signed is showing to everyone the Content Controls that are in the document. This has never happened before, all content controls are hidden in production Docusign and was always hidden on account-d. But now in the past few weeks they are showing, something has broken on account-d.  

I am using Docusign.eSign .NET package to integrate with docusign. I am trying to use BulkEnvelopesApi.CreateBulkSendRequest. I have two roles - Admin and Supervisor and I am assigning two emails to each of these two roles something like this (captured the model as JSON) {   "bulkCopies":  [  {    "recipients":[      {"email":"admin@contoso.com","name":"Admin","roleName":"Admin"},      {"email":"supervisor-1@contoso.com","name":"Supervisor-1","roleName":"Supervisor"},      {"email":"supervisor-2@contoso.com","name":"Supervisor-2","roleName":"Supervisor"}]}    ],    "name":"Demo"}  }  ]}Now, when I call createbulksendlist, i get the error BULK_SEND_ROLE_NAMES_MUST_BE_UNIQUE. I believe this is because I have Supervisor role twice in the JSON. So how do i send the request where multiple recipients share the same role? 

Hello,  We are unable to fill the customfields of a template when we try to send an envelope on Docusign API REST.The endpoint we are using is: {{baseUrl}}/{{apiVersion}}/accounts/{{accountId}}/envelopesThe body is the following: {  "templateId": "xxxxxxxx-4240-4951-bdb1-f43315509f6e",  "templateRoles": [    {      "roleName": "Signer",      "name": "Test Name",      "email": "test@test.com",      "tabs": {        "textTabs": [          {            "tabLabel": "Custom1",            "name": "Custom1",            "value": "Esto es el custom 1",            "documentId": "1",            "pageNumber": "1"          }        ]      }    }  ],  "status": "sent"} 

Is there a way to automate medical consent forms.  Recently I have had to fill out and sign forms for my minor children for religious & civic organizations.  The forms have many check boxes and signature lines as well as text fields.  Both organizations sent them in PDF with the intent of parents printing them, manually filling them out, & returning them in person.  Returning them required standing in long lines while  volunteers visually checked them and verified they were properly filled & signed.  Then all the forms were gathered and put into a box and taken on the trips with the groups to various activities.  As a parent it is a little disconcerting that my child's medical info is on a piece of paper reviewed by volunteers and in a box somewhere.  My question is:   Is there some way to collect and automate that info on DocuSign?  Is there a way that DocuSign forms can populate a database which could be later linked to some sort of QR code on a bracelet so that

Hello !  We have a integration project for Esignature. I see the OAuth configuration work on Connect RestAPI but for SOAP Connector, the authentification isn’t working.I didn’t find in a documentation if the OAuth works with legacy Connect (custom connect SOAP) Thanks,

Hello, I have an integration with my client’s custom software and DocuSign’s rest api. We are creating envelopes from a template. This all works well except we do not want the signer to have to answer the authentication questions before signing. We tried turning this off on my clients DocuSign account but the changes do not work when the envelope is created via the api. Support says we can turn off authentication via the api call but I do not see it anywhere. Can someone point me in the right direction?