Hi sushmakanugu,
If it's possible for you to monitor the "DOCUMENT_SIGNED" event, the "documentId" attribute contains the document id of which is signed by current signer. Following is a payload example.
If you couldn't monitor this event, since you can retrieve packageId anyway, you can make a traversal of all the documents and find out what documents are assigned signatures to this signer.
You can also have a check of Event Notifier Document to find out other notifiers. And hope you find this reply helpful!
We monitor documnet_signed event too.As the both events notify almost at the same time,would like to know if there is any other way to get on which document package_complete or signer_complete trigerred?
Thanks,
Sushma
Hi Sushma,
From package_complete and signer_complete event, you won't be able to find out which document triggers this event, as they are package level callbacks. (If a signer signed several documents to finish signing ceremony, it's hard to say which document triggers the event) But since you have already monitored the document_signed event, you can store all these history records in your system and finds out who signed what document in which package at when easily.
Reply to: Event Notification
Friday, October 13, 2017 at 12:47pmHi there, This question has been answered here: https://community.onespan.com/forum/how-identify-sessionuser-json-response-payload-rest-api
Reply to: Event Notification
Tuesday, July 3, 2018 at 07:34amReply to: Event Notification
Tuesday, July 3, 2018 at 08:04amReply to: Event Notification
Tuesday, July 3, 2018 at 11:44am