Updates to Package and Sender data
Monday, August 24, 2020 at 07:24pmRegarding Updates to Package data, there appears to be a date/time data field called "update". The Package also seems to have a similar date/time data field called "update" for Sender info contained inside a Package. Do these "update" fields get changed for any/all changes, or only for specific events/changes?
There is a specific "create date/time" for DRAFT txn status, and for COMPLETE txn status, but not for "IN PROGRESS" (SENT) txn status status. If a txn status is "IN PROGRESS" (SENT), can I rely on the "update" date/time field to tell me when status changed to "IN PROGRESS" (SENT)? This question also applies to the other 4 txn status's e.g. TRASHED, OPTED_OUT, DECLINED and ARCHIVED.
Reply to: Updates to Package and Sender data
Tuesday, August 25, 2020 at 03:28pmHi Mike,
For package level "updated", it's the latest update date for this package. Not all events update this date, for example: signer simply accessing and viewing the signing ceremony won't update the package (but this event is recorded by the audit trail), but signer signing a signature updates the packages. Other events like package status change also updates the package.
For "sender" > "updated", sender update date seems never changed at my accounts, and I am not aware the use of it. I will let you know if I figured it out.
If you are interested in recording the package status change, a suggested way is to set up a callback listener and listen to the events relate to the status change.
My blog "Callback Event Notification – Part 1" sorts out all callback events regarding to status change (7 statuses) and package manipulation actions(trash, restore and delete)
We also have a series of guides with working examples showcasing you how to set up the callback listener.
Duo