DocuSign API - Recipient email address changed automatically by DocuSign
We have a very straight-forward DocuSign integration where the users can add signers and send document for signing from our document management tool and the signer level updates are automatically fetched by tool and available to requester within our tool itself.
We recently ran into a rather unexpected situation with our DocuSign integration, wherein DocuSign updated/changed/resolved one of the signer's email address to a different email address. Thus, whenever we (tool) tried to fetch the updates corresponding to that signer, DocuSign kept returning null pointer exception (as the signer with that email no longer existed for the DocuSign).
On after retrieving the audit details for this envelope, we were able to understand the above issue. This was logged in DocuSign envelope history as "Recipient email resolved". On DocuSign Admin account, this entry is shown as below:
DocuSign Envelope History Screenshot
I have tried to dig into DocuSign documentation (product & API both) to know more about "Recipient email resolved" action but to no avail.
My queries are -
- Has anyone run into similar situation in past?
- What is the root cause/reason because of which DocuSign automatically resolves (changes) the email address of the recipient?
- Is there a way to suppress this behavior? If not, is there a way to retrieve the status update against original email address instead of having to manually update the email in our tool?
Additional Information:
- Our tool is built such that it allows the customers to configure their own DocuSign account
docusignapi
asked Jan 3 at 13:38
NakulNakul
32
add a comment |
We have a very straight-forward DocuSign integration where the users can add signers and send document for signing from our document management tool and the signer level updates are automatically fetched by tool and available to requester within our tool itself.
We recently ran into a rather unexpected situation with our DocuSign integration, wherein DocuSign updated/changed/resolved one of the signer's email address to a different email address. Thus, whenever we (tool) tried to fetch the updates corresponding to that signer, DocuSign kept returning null pointer exception (as the signer with that email no longer existed for the DocuSign).
On after retrieving the audit details for this envelope, we were able to understand the above issue. This was logged in DocuSign envelope history as "Recipient email resolved". On DocuSign Admin account, this entry is shown as below:
DocuSign Envelope History Screenshot
I have tried to dig into DocuSign documentation (product & API both) to know more about "Recipient email resolved" action but to no avail.
My queries are -
- Has anyone run into similar situation in past?
- What is the root cause/reason because of which DocuSign automatically resolves (changes) the email address of the recipient?
- Is there a way to suppress this behavior? If not, is there a way to retrieve the status update against original email address instead of having to manually update the email in our tool?
Additional Information:
- Our tool is built such that it allows the customers to configure their own DocuSign account
docusignapi
asked Jan 3 at 13:38
NakulNakul
32
add a comment |
We have a very straight-forward DocuSign integration where the users can add signers and send document for signing from our document management tool and the signer level updates are automatically fetched by tool and available to requester within our tool itself.
We recently ran into a rather unexpected situation with our DocuSign integration, wherein DocuSign updated/changed/resolved one of the signer's email address to a different email address. Thus, whenever we (tool) tried to fetch the updates corresponding to that signer, DocuSign kept returning null pointer exception (as the signer with that email no longer existed for the DocuSign).
On after retrieving the audit details for this envelope, we were able to understand the above issue. This was logged in DocuSign envelope history as "Recipient email resolved". On DocuSign Admin account, this entry is shown as below:
DocuSign Envelope History Screenshot
I have tried to dig into DocuSign documentation (product & API both) to know more about "Recipient email resolved" action but to no avail.
My queries are -
- Has anyone run into similar situation in past?
- What is the root cause/reason because of which DocuSign automatically resolves (changes) the email address of the recipient?
- Is there a way to suppress this behavior? If not, is there a way to retrieve the status update against original email address instead of having to manually update the email in our tool?
Additional Information:
- Our tool is built such that it allows the customers to configure their own DocuSign account
docusignapi
asked Jan 3 at 13:38
NakulNakul
32
We have a very straight-forward DocuSign integration where the users can add signers and send document for signing from our document management tool and the signer level updates are automatically fetched by tool and available to requester within our tool itself.
We recently ran into a rather unexpected situation with our DocuSign integration, wherein DocuSign updated/changed/resolved one of the signer's email address to a different email address. Thus, whenever we (tool) tried to fetch the updates corresponding to that signer, DocuSign kept returning null pointer exception (as the signer with that email no longer existed for the DocuSign).
On after retrieving the audit details for this envelope, we were able to understand the above issue. This was logged in DocuSign envelope history as "Recipient email resolved". On DocuSign Admin account, this entry is shown as below:
DocuSign Envelope History Screenshot
I have tried to dig into DocuSign documentation (product & API both) to know more about "Recipient email resolved" action but to no avail.
My queries are -
- Has anyone run into similar situation in past?
- What is the root cause/reason because of which DocuSign automatically resolves (changes) the email address of the recipient?
- Is there a way to suppress this behavior? If not, is there a way to retrieve the status update against original email address instead of having to manually update the email in our tool?
Additional Information:
- Our tool is built such that it allows the customers to configure their own DocuSign account
docusignapi
docusignapi
asked Jan 3 at 13:38
NakulNakul
32
asked Jan 3 at 13:38
NakulNakul
32
edited Jan 3 at 13:53
Nakul
asked Jan 3 at 13:38
NakulNakul
32
asked Jan 3 at 13:38
NakulNakul
32
asked Jan 3 at 13:38
NakulNakul
32
32
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54023422%2fdocusign-api-recipient-email-address-changed-automatically-by-docusign%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54023422%2fdocusign-api-recipient-email-address-changed-automatically-by-docusign%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
