Saving a Document Prior To Send To Sign

Hi Bikram,

 

Yes, I think what you described is achievable. In order to leverage the feature, first step is to contact our support team and have the feature turned on at your account. Afterwards, when building the package JSON, you can build an "approval" node without signature field, see below:

 

 

{

  "roles": [

    {

      "id": "Signer1",

      "signers": [

        {

          "email": "[email protected]",

          "firstName": "John",

          "lastName": "Smith",

          "company": "OneSpan Sign"

        }

      ]

    }

  ],

  "documents": [

    {

      "approvals": [

        {

          "role": "Signer1",

          "fields": [

            {

              "page": 0,

              "top": 100,

              "subtype": "TEXTFIELD",

              "height": 50,

              "left": 100,

              "width": 150,

              "type": "INPUT"

            }

          ]

        }

      ],

      "name": "Document1"

    }

  ],

  "name": "No Signature Fields",

  "language": "en",

  "emailMessage": "",

  "description": "New Package",

  "autocomplete": true,

  "status": "SENT"

}

Let me know how it works for you.

 

Duo

Hi Bikram,

 

Thanks for your post! I recollected that we used to have a conversation about using Custom Field as a placeholder and later replacing it with a LABEL field. Is this still the case for your integration? I think it's expected that the sender can't see the Custom Field value, but after the value was injected from your database, if you refresh the designer page before the final send, the sender should be able to see the LABEL field value.

 

Duo

Hello Duo, 

Yes, the case regarding the custom fields are still same, we are converting it to label field after the data gets inserted from database. We are looking to preview the final document with the data before send to sign(only data without those label field). 

 

 

Thanks,

Bikram 

Hi Bikram,

 

There's a new feature introduced in 11.48 which might be related, but not so sure this is what you are looking for. You can now have a mix of input fields (including Custom field and Label field) and accept-only document. That's to say, you can bind this field to your sender and have your sender review/accept the content as the first signer. Let me know if you want to follow this path and I will provide more detailed information.

 

Duo

Yes Duo, 

This sounds interesting, if the agent can have the accept only document with those prefilled data there, we can give that agent index 1 and after he views the accept only document, we can give the index 2 and so on to other recipient. If this can be achievable, I would like to know more about it. 

 

 

Thanks,

Bikram 

Hi Duo, 

I have tried updating an approval with only role name and no signature field via onespan api sandbox. It succeeded but while sending the document to sign, I have got the error, the screenshot of which is attached herewith this email. Is it because the settings are not applied yet in my account or it has got something to do with another problem. It says there is a role with no signer but this feature should allow this case for sending to sign right ? Am I missing something? Can you please help. 

Hi Duo, 

That was awesome, it worked. Thanks a lot.