To Enable Accept only feature via JSON

Tejaswi, If your email is the package owner, you won't receive an activation email. (even if you have signatures on the document) So I believe the requirement can be boiled down to this one: "How to let my package owner email receive an activation email"? Here're few potential solutions OneSpan Sign can provide: (1)You can contact support team and add your email as CC, for "email.activate" template. The side effect of this solution is, you'll receive multiple copies when there're multiple recipients. (2)You can assign another sender under your main account as the owner of this package (documentation here), and add your email as a normal reviewer: simply by adding your email to the "roles" array. Duo

Hi Tejaswi, If you want to create an "accept-only" document, you can use below payload for a document:

{
      "approvals": [
        {
          "role": "signer1_role_id"
        },
       {
          "role": "signer2_role_id"
        }
      ],
      "index": 1,
      "id": "document_id",
      "name": "Sample_consent",
      "isConsent": false/true
    }

The "isConsent" indicates whether this document is a default consent or normal accpet-only document. There can be only one default consent document in a package.

You can use this payload during package creation or to upload a new document afterwards. But here's few facts you would be interested to know: (1)you can't have other signatures or fields in an accept-only document. (2)you can only add signer 1 to this document, other signers will be considered as reviewers. On top of that, if you don't want signers to view this document, you can set up document visibility to this particular document. Let me know if I've misunderstood you. And hope this could help! Duo

Hi Duo, Thanks for the reply. Can you please how to extract the document id? What I am trying to do is, while integrating Oracle and one span sign, I want myself to receive an email notification whenever I execute the PLSQL package. So, that I can understand that a document is pending with me. But, I am not included as signer just a reviewer. I tried passing the "optional signature" : "true" in json. But still did not receive any email.

Hi Tejaswi, Do you mean that, you want to add a reviewer to a package, and potentially you want to control the visibility of this reviewer to a specific document? You can utilize document visibility feature on this one, instead of accept only feature. But I think it's better that I understand your requirement entirely before we continue to discuss about the details of the solution. Duo

Hi Duo, Yes I want to add a reviewer to package. But that reviewver is me. Also, the transaction is initiated from my one span sign account. I dont want to control the visibility of reviewver to a specific document. There is only one attachment (pdf).

Hi Duo, I implemented the second solution provided and its working fine. (REST API method) I am also adding an email message just for the 1st signer to not sign the document. So, added the json accordingly using the below link: https://developer.esignlive.com/guides/feature-guides/email-message/ But, the email message is not getting reflected in the notification. JSON : { "signers": [ { "name": "Tejaswi Pable", "created": "' || v_date2 || '", "id": "Reviewer", "language": "en", "auth": { "scheme": "NONE", "challenges": [] }, "updated": "' || v_date2 || '", "firstName": "Tejaswi", "lastName": "Pable", "email": "[email protected]", "signerType": "ACCOUNT_SENDER", "emailMessage": { "content": " Note: Please do not sign the document." } } ], "name": "Tejaswi Pable", "type": "SIGNER", "index": 1, "id": "role9", "attachmentRequirements": [] }

Hi Tejaswi, Please note that the "emailMessage" node should be directly under "roles" array and outside the "signers" array, like below:

{
  "emailMessage": {
    "content": "Note: Please do not sign the document."
  },
  "name": "Tejaswi Pable",
  "type": "SIGNER",
  "signers": [
    {
      "name": "Tejaswi Pable",
      "id": "Reviewer",
      "language": "en",
      "auth": {
        "scheme": "NONE",
        "challenges": []
      },
      "firstName": "Tejaswi",
      "lastName": "Pable",
      "email": "your_sender_email",
      "signerType": "ACCOUNT_SENDER"
    }
  ],
  "index": 1,
  "id": "role9",
  "attachmentRequirements": []
}

And the email should resemble the following Duo

Hi Duo, Thanks for the help. Now I am able to see the message intended for 1st signer. How to remove the 'Electronic Disclosures and Signatures Consent' document? I know its a default document. But, is there any way to remove it.

Hi Tejaswi, You can contact our support team([email protected]) to remove this default consent from your account level, in which case, all newly created transactions will be without this document. Duo

Thanks Duo Earlier I was able to see the Optional signature button. But now, it is not visible in sandbox e-sign account. PFA.

Hi Tejaswi, Optional Signature is a feature in your account level settings, please contact our support team to enable this feature through backoffice. Duo

Okay. Can you please tell me what is the difference between these signer types: SignerType [ ACCOUNT_SENDER, EXTERNAL_SENDER, EXTERNAL_SIGNER, GROUP_SIGNER ]. I was unable to find any document regarding this.

Hi Tejaswi, I think you referred to our Swagger API site, "role" model. Actually you don't need to specify the signer type when creating a package (that's why we haven't documented it yet, from my understanding). OneSpan Sign system will automatically detected the signer's type and inject to your package JSON. To clarify these four types: ACCOUNT_SENDER -- if the signer is a sender under current API Key holder's account. EXTERNAL_SENDER -- if the signer is a sender in OSS system, while not under your current account. EXTERNAL_SIGNER -- if the signer is not a sender in OSS system, within the particular environment. (Sandbox US/Production US, etc) GROUP_SIGNER -- if the signer is a group type signer under your account. (guide here) Based on above, you don't need to specify or not necessary to know the signer's type. Duo