Delete Document and Signer Status

Hi Michael,

Following the same process as you described, the status of Signer 2 in my testing package remains SIGNING_COMPLETE as you expected. See below log trace:

Signer 1 signed
{"status":"SIGNING_COMPLETED"}
{"status":"SIGNING_PENDING"}

Signer 2 signed
{"status":"SIGNING_COMPLETED"}
{"status":"SIGNING_COMPLETED"}

Delete Document 2
when the package was still in draft mode
{"status":"DRAFT"}
{"status":"DRAFT"}

when sent out the package
{"status":"SIGNING_COMPLETED"}
{"status":"SIGNING_COMPLETED"}

Could you provide me a package ID where the Signer 2's status is SIGNING_PENDING?

Duo

Just tried again with the same result. Package is n65WzkWbEXyeflGm-rEMbTppaDc=

I am using the Java SDK

                     Mike

To be clear, no one in my scenario has signed anything yet (I see I described that poorly). But  I have deleted the only document that signer2 was assigned to sign.

Here is my scenario:

Create package with signer1 assigned to sign document 1 and signer 2 assigned to sign document 2.

Delete document 2

Hi Mike,

I can reproduce the issue now and I think this is somehow related to Default Consent. Not sure how important is Default Consent to your use case, but you should be able to avoid this issue if you delete the default consent with:

        eslClient.getPackageService().deleteDocument(packageId, "default-consent");
 

At the same time, I will look into previous tickets and check if this is a known issue. We can fill in a support ticket and report this to R&D team if necessary.

Duo

I will check - I am not sure if we need the default consent.This may provide us a workaround. But if you find the expected behavior is to set signer2 to SIGNING_COMPLETE I would appreciate the ticket to fix. Thanks

And just to note I verified if I delete the default-consent the signer is properly set to SIGNER_COMPLETE as you said.

Duo, deleting the consent form worked on my personal sandbox, but I get the below error when I try it on our development sandbox. Do we need another permission to do this? The failing account is [email protected]

{"error" : "Cannot process request","reason" : "Could not delete document from package. Exception: HTTP DELETE on URI https://sandbox.esignlive.com/api/packages/Lqsic-uLDB8-0kZpXpfINq04PPk=/documents/default-consent resulted in response with status code: [403, Forbidden]. Optional details: {"messageKey":"error.forbidden.removeConsentDocument","technical":"The Electronic Consent Document cannot be removed.","code":403,"message":"The Electronic Consent Document cannot be removed.","name":"Access Denied"}","stack" : "com.silanis.esl.sdk.internal.EslServerException: Could not delete document from package. Exception: HTTP DELETE on URI https://sandbox.esignlive.com/api/packages/Lqsic-uLDB8-0kZpXpfINq04PPk=/documents/default-consent resulted in response with status code: [403, Forbidden]. Optional details: {"messageKey":"error.forbidden.removeConsentDocument","technical":"The Electronic Consent Document cannot be removed.","code":403,"message":"The Electronic Consent Document cannot be removed.","name":"Access Denied"}

Hi Michael,

For your development sandbox account, you've turned on an account level setting "Prevent Removing Electronic Consent Document". This disables the options to remove default consent in transaction edit page, designer page as well as to delete via API/SDK call. If you didn't have it enabled on purpose, you can contact support team ([email protected]) and revert it to default value (false).

Duo