abhijit_davray

URGENT - Delegation (ROLE_REASSIGN)

0 votes
Hi, In the JSON retrieved for a Package is there a way to figure out Who (Role/Email) has delegated to Who (Role/Email). After delegation we get the ROLE_REASSIGN event. { "@class": "com.silanis.esl.packages.event.ESLRoleReassignEvent", "sessionUser": "4f124151-9ab9-4956-bf8b-c67454f2b63d", "packageId": "u4aKSxuKuDbI3JtPm1mAjsvYSIc=", "newRoleId": "2bb31fae-fe60-4200-a469-3e71e0c9f81e", "message": null, "name": "ROLE_REASSIGN", "documentId": null } I know we get the link the old Role to the new Role. But unfortunately we do not store it. When the new role signs, we get the DOCUMENT_SIGNED event. Here I get the sessionUser of the new Role. { "@class": "com.silanis.esl.packages.event.ESLProcessEvent", "name": "DOCUMENT_SIGNED", "sessionUser": "1a9ced99-d712-42af-97df-5a19f0ed05ff", "packageId": "u4aKSxuKuDbI3JtPm1mAjsvYSIc=", "message": null, "documentId": "DOCUMENT_ICMContract" } We do get reassign: true on the new Role. Here is there a way to figure out who (email) delegated to this Role. If this does not workout I will have to modify the JSON after the ROLE_REASSIGN event. Which field on the new Role can be used to hold the ID of the old Role. Thanks, Abhijit

Approved Answer

Reply to: URGENT - Delegation (ROLE_REASSIGN)

0 votes
Did you make sure you put the package in DRAFT status before attempting to change the company? If not, you won't get an error, but it just won't change the value. Let me know.

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: URGENT - Delegation (ROLE_REASSIGN)

0 votes
Follow up question on the above: I am trying to update company using the following call: PUT https://sandbox.esignlive.com/api/packages/u4aKSxuKuDbI3JtPm1mAjsvYSIc=/roles/2bb31fae-fe60-4200-a469-3e71e0c9f81e This is not working. Please Help. { "id": "2bb31fae-fe60-4200-a469-3e71e0c9f81e", "emailMessage": { "content": "werwew-werwewer-werwewer" }, "attachmentRequirements": [ ], "locked": false, "reassign": true, "specialTypes": [ ], "data": { "eslColorIndex": null }, "index": 1, "type": "SIGNER", "signers": [ { "group": null, "language": "en", "signature": null, "id": "1a9ced99-d712-42af-97df-5a19f0ed05ff", "external": null, "updated": "2017-04-17T05:00:09Z", "company": "", "email": "[email protected]", "firstName": "ddd", "lastName": "ddd", "phone": "", "professionalIdentityFields": [ ], "userCustomFields": [ ], "delivery": { "email": false, "download": true, "provider": true }, "knowledgeBasedAuthentication": null, "auth": { "scheme": "NONE", "challenges": [ ] }, "data": null, "title": "", "address": null, "created": "2017-04-17T05:00:09Z", "name": "", "specialTypes": [ ] } ], "name": "Signer1" }

Reply to: URGENT - Delegation (ROLE_REASSIGN)

0 votes
By Deleation (ROLE_REASSIGN), you're meaning the signer passing the signing to someone else, right? Not what we refer to as Delegation, which is on the Sender side of things where you're able to delegate access to your account to others within the account? Let me know. For the first post, have you looked in the audit info for the post to see if this info is available? I have not looked, yet, but this is what I would check, first. Another option could be to use the notification you get from esignlive and update the package JSON to add the old role as an attribute on the package. Or even just do this by default. Add an attribute to the package with the original signer info. For the second post, what is the error you're getting? You're trying to clear the company value?

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Reply to: URGENT - Delegation (ROLE_REASSIGN)

0 votes
Yes by Delegation I meant ROLE_REASSIGN (signer passing the signing to someone else). I have decided to update JSON package to store this information. Can you help me with the Update Role Information API. I used the below API. It does not give any error but returns the same JSON back without updating the information. Here I am trying to update company attribute just as an example. PUT https://sandbox.esignlive.com/api/packages/bEsPSogrZfo2_hrGpPpTZu9zOnA=/roles/f3b6e6ce-809c-455d-b739-f3a3e0f76ab5 { "id": "f3b6e6ce-809c-455d-b739-f3a3e0f76ab5", "data": { "eslColorIndex": null }, "emailMessage": { "content": "1-1-1-1-1" }, "attachmentRequirements": [ ], "locked": false, "reassign": true, "specialTypes": [ ], "type": "SIGNER", "index": 1, "signers": [ { "group": null, "language": "en", "signature": null, "id": "2a7ee394-7dbe-4bd5-80e6-36203dcdec9d", "title": "", "data": null, "auth": { "scheme": "NONE", "challenges": [ ] }, "delivery": { "provider": true, "email": false, "download": true }, "knowledgeBasedAuthentication": null, "external": null, "updated": "2017-04-18T12:15:16Z", "company": "UPDATED-UPDATED-UPDATED", "email": "[email protected]", "firstName": "dimple", "lastName": "davray", "phone": "", "professionalIdentityFields": [ ], "userCustomFields": [ ], "address": null, "created": "2017-04-18T12:15:16Z", "name": "", "specialTypes": [ ] } ], "name": "Signer1" }

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