Reply to: Force Notary to have to accept the default consent
Thursday, June 6, 2019 at 10:57am
1
votes
Hey Ryan,
After some investigate, I found out that once the package was notarized, the default-consent document was converted to accept-only document by OSS system, it consists with the behavior that in notary signing, default-consent document was no longer a blocking for signing process. Namely, the "approval" node in default-consent document's metadata was no longer empty as it normally to be and at the same time, notary's name was not in the array list.
normal signing:
{
"status": "",
"description": "Must be accepted and agreed to before starting the signing process.",
"id": "default-consent",
"data": {
"ese_document_texttag_extract_needed": "false"
},
"external": null,
"approvals": [],
...
}
notary signing:
{
"status": "",
"description": "Must be accepted and agreed to before starting the signing process.",
"id": "default-consent",
"external": null,
"signedHash": null,
"approvals": [ //only signer was added, not notary
{
"role": "956cfd92-d31c-44cb-8d90-1b57db85c153",
"id": "6f4dd1c1-6c13-42c1-b604-9edb196ebaba",
"optional": false,
"accepted": "2019-06-06T18:54:47Z",
"enforceCaptureSignature": false,
"signed": "2019-06-06T18:54:47Z",
"data": null,
"fields": [],
"name": ""
}
],
......
}
To work it around, if you added an accept approval for notary by REST in separate call after notary role id was chosen but before the package was finally sent:
Reply to: Force Notary to have to accept the default consent
Thursday, June 6, 2019 at 10:57am{ "status": "", "description": "Must be accepted and agreed to before starting the signing process.", "id": "default-consent", "data": { "ese_document_texttag_extract_needed": "false" }, "external": null, "approvals": [], ... }notary signing:{ "status": "", "description": "Must be accepted and agreed to before starting the signing process.", "id": "default-consent", "external": null, "signedHash": null, "approvals": [ //only signer was added, not notary { "role": "956cfd92-d31c-44cb-8d90-1b57db85c153", "id": "6f4dd1c1-6c13-42c1-b604-9edb196ebaba", "optional": false, "accepted": "2019-06-06T18:54:47Z", "enforceCaptureSignature": false, "signed": "2019-06-06T18:54:47Z", "data": null, "fields": [], "name": "" } ], ...... }To work it around, if you added an accept approval for notary by REST in separate call after notary role id was chosen but before the package was finally sent:HTTP Request POST /api/packages/{packageId}/documents/{documentId}/approvals HTTP Headers Accept: application/json Content-Type: application/json Authorization: Basic api_key Request Payload { "role": "notary_role_id", "id": "approval_id", "name": "approval_name" }Notary will be forced to accept the default consent. Hope this could help! Duo