docusign-esign-node-client
docusign-esign-node-client copied to clipboard
phoneNumber for Signer parameter is not in @types package
Hello DocuSign,
I work on a project using the docusign-esign 5.20.0 npm package and its types package 5.19.0. Using the Signer class, I noticed that my linter doesn't accept the phoneNumber parameter. I checked on the types docusign-esign package, it is not in the Signer interface.
Is the types package not updated or is the parameter deprecated?
Thanks in advance!
This is the old way to do this, this has moved under workflow. See full code in https://github.com/docusign/code-examples-node/blob/master/lib/eSignature/examples/phoneAuthentication.js
let signer1 = docusign.Signer.constructFromObject({
email: args.signerEmail,
name: args.signerName,
recipientId: RecipientId,
routingOrder: "1",
deliveryMethod: "Email",
tabs: signer1Tabs,
identityVerification: { workflowId: args.workflowId, steps: null, "inputOptions":[{"name":"phone_number_list","valueType":"PhoneNumberList","phoneNumberList":[{"countryCode":args.countryCode,"code":"1","number":args.phoneNumber}]}], "idCheckConfigurationName":""}
});
So the doc needs to be updated: https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-sms/
@peiofour for the most up-to-date reference for this SDK, please refer to http://docusign.github.io/docusign-esign-node-client. These get automatically updated during our release process and will be the most consistent reference to the SDK
@peiofour I'm confused, is this about SMS delivery or SMS authentication? these are two different things.
@InbarGazit It's for SMS delivery (https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/sms-delivery/)
OK, thanks, do you still have an issue? or can I close this out?
Yes ! The issue didn't change, tslint does'nt accept phoneNumber parameter as we can see here : https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/sms-delivery/

And there is no additionalNotifications field for the Signer type