docusign / code-examples-node Goto Github PK
View Code? Open in Web Editor NEWNode.js code examples and launcher
Home Page: https://developers.docusign.com/
License: MIT License
Node.js code examples and launcher
Home Page: https://developers.docusign.com/
License: MIT License
$ npm i
...
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /home/tylercollier/repos/code-examples-node/docusign-webforms-1.0.2-rc11.tgz
npm ERR! errno -2
npm ERR! enoent ENOENT: no such file or directory, open '/home/tylercollier/repos/code-examples-node/docusign-webforms-1.0.2-rc11.tgz'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
Looks like it happened here. 796a3f7
Not sure why a local file was committed.
Hi, What is the authentication method suggested for aws lambda to make API call to eSignature APIs?
Scenario : Once Connect notifies a lambda that a doc has been signed, we are making a call to eSignature api
https://demo.docusign.net/restapi/v2.1/accounts/{{accountId}}/envelopes/{{envelopeId}}/form_data
to get the data entered on that form/envelop.
This is the example we are following closely that sends message to SQS once Connect triggers a Lambda.
We are just adding one more step to this to get the form data.
https://github.com/docusign/connect-node-listener-aws/blob/master/index.js
Ideally there should have been an option to get the form data right on the Connect configuration pictured bellow.
As it saves the extra steps needed to authenticate and verify again...and then make another API call.
Considering we already did Basic Auth and HMAC verification on above sample code; There should be an easy way to get the form data than authenticating again.
I have a situation where I was forced to switch from Implicit Grant to Authorization Code Grant.
Is it possible to use docusign-esign lib requestJWTUserToken
method to generate token for an integration that was setup with Authorization Code Grant ?
While trying to test authentication flow using the "Send an envelope with a remote (email) signer and cc recipient" option, after being redirected to the DocuSign login page I immediately get the message:
"Invalid authentication request: The response type is not supported."
And then continue to receive the message after entering my username and password.
I am trying to update the value of text tabs of an envelope, so i am using envelopesAPI.listTabs api to get all values, and envelopesApi.updateTabs to update them, but i keep getting error 'The request body is missing or improperly formatted. No tabs specified'. Can anyone provide example code to update textTabs?
I tried to follow along with the demo on website found here: https://www.youtube.com/watch?v=5iUq00IRaTk&embeds_referring_euri=https%3A%2F%2Fdevelopers.docusign.com%2F&source_ve_path=MzY4NDIsMjg2NjY&feature=emb_logo
It appears that the folder structure is not longer the same for eg001EmbeddedSigning.ejs is no longer in the root.
I did the quickstart download.
npm install
npm start
Then I got the below error
Error: C:\Users\RMcAvoy\code\easier-tester-node.js\views\pages\examples\eg001EmbeddedSigning.ejs:1
>> 1| <%- include("../../partials/examplesHead") %>
2|
3| <%- include("../../partials/exampleInfo") %>
4|
Could not find the include file "../../partials/examplesHead"
at getIncludePath (C:\Users\RMcAvoy\code\easier-tester-node.js\node_modules\ejs\lib\ejs.js:185:13)
at includeFile (C:\Users\RMcAvoy\code\easier-tester-node.js\node_modules\ejs\lib\ejs.js:311:19)
at include (C:\Users\RMcAvoy\code\easier-tester-node.js\node_modules\ejs\lib\ejs.js:701:16)
at eval ("C:\\Users\\RMcAvoy\\code\\easier-tester-node.js\\views\\pages\\examples\\eg001EmbeddedSigning.ejs":10:17)
at eg001EmbeddedSigning (C:\Users\RMcAvoy\code\easier-tester-node.js\node_modules\ejs\lib\ejs.js:703:17)
at tryHandleCache (C:\Users\RMcAvoy\code\easier-tester-node.js\node_modules\ejs\lib\ejs.js:274:36)
at exports.renderFile [as engine] (C:\Users\RMcAvoy\code\easier-tester-node.js\node_modules\ejs\lib\ejs.js:491:10)
at View.render (C:\Users\RMcAvoy\code\easier-tester-node.js\node_modules\express\lib\view.js:135:8)
at tryRender (C:\Users\RMcAvoy\code\easier-tester-node.js\node_modules\express\lib\application.js:657:10)
at Function.render (C:\Users\RMcAvoy\code\easier-tester-node.js\node_modules\express\lib\application.js:609:3)
File is currently called examplesAPI.json.
Easiest fix would be renaming the file
https://github.com/docusign/code-examples-node/blob/master/config/appsettings.example.json
/config/appsettings.example.json: This may be obvious for most, but it would be helpful to provide a brief description and link to the DocuSign Developer authentication online documentation.
dsClientId: "{INTEGRATION_KEY_AUTH_CODE}",
dsClientSecret: "{SECRET_KEY}",
dsJWTClientId: "{INTEGRATION_KEY_JWT}",
impersonatedUserGuid: "{IMPERSONATED_USER_ID}",
signerEmail: "{SIGNER_EMAIL}",
signerName: "{SIGNER_NAME}",
gatewayAccountId: "{GATEWAY_ACCOUNT_ID}",
quickstart: "{QUICKSTART_VALUE}",
In views/pages/examples/eg044Embed.ejs
, there is this on line 27:
<script src='https://js.docusign.com/bundle.js'></script>
Shouldn't it be
<script src='https://js-d.docusign.com/bundle.js'></script>
Also, I'm not sure where else to report this, but the source maps are missing in the file https://docucdn-a.akamaihd.net/demo/1ds/widgets/@ds/signing/24.3.40-4/signing_iframeless_mobile.172.js?cs=539be489332502f5e410. Can you add the sourcemaps?
The reason I report it is because I'm having trouble with embedded signing. I'm trying to combine examples 13 and 44 to use a server side template but with embedded+focused signing, which I can get working with redirect signing (I think this is called embedded signing as opposed to remote signing, but it's not focused), but not embedded+focused signing. With the non-modified example 44 that uses window.DocuSign.loadDocuSign()
, I can see that signing_iframeless_mobile.172.js
issues an XHR request for https://demo.docusign.net/Signing/DocuSignXML.aspx?abc=123..., but it's not making that fetch with my attempt to piece together examples 13 and 44. If I had the sourcemaps, maybe I could figure out why.
I'm attempting to create a responsive signing envelope using the htmlDefinition property in a document. I receive an error message:
PLAN_ITEM_NOT_ENABLED: A requested plan item is not enabled for this account. This account is not enabled for Smart Sections.
Specifically passing through a html template.
I want to cancel or delete an envelope
I have create a basic repo to recreate and demonstrate the issue: https://github.com/fullStackRyan/next-docusign-example-problem
Clone the repo.
npm install
npm run dev
using POSTMAN do a POST to http://localhost:3000/api/docusign
Next is a fullstack framework anything within app/api with a file route.ts is considered the server side from my understanding.
- error ./node_modules/docusign-esign/src/index.js
Module not found: Can't resolve 'ApiClient'
Did you mean './ApiClient'?
Requests that should resolve in the current directory need to start with './'.
Requests that start with a name are treated as module requests and resolve within module directories (node_modules, C:\Users\RMcAvoy\code\next-docusign-example-problem).
If changing the source code is not an option there is also a resolve options called 'preferRelative' which tries to resolve these kind of requests in the current directory too.
https://nextjs.org/docs/messages/module-not-found
Docusign now supports PKCE. As a demonstration of best practices, it would be great if this repo updated the client side code grant flow to use PKCE instead of implicit grant, if that's now possible.
How can I redirect my user to template creation page of the docusign web UI to create his template and then he'll redirect again to my app and can send them to anyone
Error: Cannot find module './eg001EmbeddedSigning'
Works if I move ./embeddedSigning.js to ./lib/eSignature/examples/embeddedSigning.js and move ./lib/eSignature/controllers/eg001EmbeddedSigning.js to ./eg001EmbeddedSigning.js
There is no example with regards to this in the Node SDK example list. Also can I add a date picker? Please do reply as I am unable to figure this out and I am looking for a while.
When following the README the JWT section says we need to update some variables in the appsettings.json file. It doesn't say what those variables are in the file. It also doesn't say what they are called on the api-integrator-key page on the Docusign site. It would be really helpful to have a clear mapping of what the values are in the appsettings.json file and precisely what they are called in the api-integrator-key page. This makes it difficult to get the test app up and running.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.