Thomas_Lang

Signing order

0 votes

Hello everybody,

 

I try to implement a signing order, but it doesn't work. All three Emails are sent at the same time.

What's wrong? Here is my json code:

{

"documents": [

{

"approvals": [

{

"id": "ExampleSignatureId",

"role": "Signer1",

"fields": [

{

"page": 0,

"top": 100,

"subtype": "FULLNAME",

"height": 50,

"left": 100,

"width": 200,

"type": "SIGNATURE",

"name": "ExampleSignatureId1"

}

],

"role": "Signer2",

"fields": [

{

"page": 0,

"top": 100,

"subtype": "FULLNAME",

"height": 250,

"left": 100,

"width": 200,

"type": "SIGNATURE",

"name": "ExampleSignatureId2"

}

],

"name": ""

}

],

"id": "samplecontract",

"name": "Test Document"

}

],

"status": "SENT",

"type": "PACKAGE",

"roles": [

{

"id": "Signer1",

"index": 0,

"type": "SIGNER",

"signers": [

{

"email": "[email protected]",

"firstName": "Thomas",

"lastName": "Lang",

"id": "Signer1"

}

],

"name": "Signer1"

},

{

"id": "Signer2",

"index": 1,

"type": "SIGNER",

"signers": [

{

"email": "[email protected]",

"firstName": "Karen",

"lastName": "Schulz",

"id": "Signer2"

}

],

"name": "Signer2"

},

{

"id": "CC_RECEIVER",

"index": 2,

"type": "SIGNER",

"signers": [

{

"email": "[email protected]",

"firstName": "Peter",

"lastName": "Schmitz",

"id": "Signer3"

}

],

"name": "CC_RECEIVER"

}

],

"name": "Unser OneSpan Example Package"

}


Reply to: Signing order

0 votes

Hi Thomas,

 

From my test with the same payload, Signer1 (reviewer, index of 0) and Signer 2 (actual signer, index of 1) received the emails at the same time, this is because Signer1 doesn't have any signatures, therefore not a blocker for the signing flow. While Signer 2 finished signing, Signer 3 / CC_RECEIVER (reviewer, index of 2) received the email, together with a package completion email.

Hence could you confirm that Signer 3 received the email before Signer 2 has signed? Also, if you can share the package ID, it would also help.

 

Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Reply to: Signing order

0 votes

YOu are right, the Json was wrong. It works as expected when I design it like:

 

{

"emailMessage": "Nicht fragen, unterschreiben!",

"sender": {

"name": "MeinSenderName",

"type": "REGULAR",

"content": "MeinEmailContent"

},

"documents": [

{

"approvals": [

{

"id": "ExampleSignatureId",

"role": "Signer1",

"fields": [

{

"page": 0,

"top": 100,

"subtype": "FULLNAME",

"height": 50,

"left": 100,

"width": 200,

"type": "SIGNATURE",

"name": "ExampleSignatureId1"

}

]

},

{ "id": "ExampleSignatureId2",

"role": "Signer2",

"fields": [

{

"page": 0,

"top": 200,

"subtype": "FULLNAME",

"height": 50,

"left": 100,

"width": 200,

"type": "SIGNATURE",

"name": "ExampleSignatureId2"

}

]

(etc)


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off