Uday's account

Sure, Thanks Haris.

Hey Haris, here is the requested json. https://jsoncompare.com/#!/simple/id=68c66de002a7954ce9da19941ff50408&reformat=beautify_2/ Please take a look.

Hi Haris, Thank you We have a situation where we need to move a document in one package to another, and i was directly adding document object from previous package to new one saying .WithDocument(..) during new package build. The api is not happy if i directly add a document like that from another package. I had to regenerate the document again like how i did for the existing package that document resides in. And it worked. Do you have any idea why this happens ?

This situation comes as part of a scenario where a transaction with 5 documents and 2 signers, the Sender himself and Signer A. Signer A is supposed to visit the package sender to electronically sign, in front of him and will not receive a notification to sign at a remote place (this is a business requirement). A signs documents and leaves place after which Sender had a couple more documents to sign (these are usually ancillary, could be signed and accessed from any remote location). In this scenario we had to 'move' documents from the existing package to a new package and send the signer a notification to sign at his location. Note: 1. The place of origination of document for any signer is not completely in our control. It ends up adding document to existing package already created. 2. The documents already signed contains documents that should 'not' be shown to the signer as per the requirement. Hope it helps. Let me know if you have way to make this process easier.

Hi Duo Liang We tried replicating same steps provided through email.

Package is moved to DRAFT mode Using GET, role for which signature must be cleared, is retrieved One particular tag signature is removed from payload Using a PUT call, modified payload is successfully sent to server Package is moved to SENT mode

The only problem here is, while response from PUT call shows the signature tag to be null, re-fetching the role using a GET call shows the signature value. Images showing same are attached for your reference. Also, in the information shared through mail, it is observed that documents are immediately being uploaded to package after signer's signature is cleared. But as per our business need, this is not feasible. Documents will be added to this package in future using a different procedure altogether. Business Need: In a scenario where customer leaves after signing but had to revisit & sign few more documents the next day. In this case:

New package creation, maintenance is proving to be costly for us Enforcing hand drawn signatures at package level is proving to be tiresome for user Applying the same signature, captured previous day is bewildering user

Customers are little hesitant about persisting their signature even after they completed signing & left the place. Hope our challenge & business need is clearer to you now.