Adobe PDF has the functionality to set up forms that have multiple signature fields, with each of those signatures being associated with a specified set of data fields. We have a form like that.
The first user fills out the first set of fields and applies his digital signature. When the first signature is applied, all the fields that go with that signature are locked (i.e. made read-only).
The form is then routed to the next user, who repeats the procedure with the next group of fields, filling them out and then applying his digital signature in their associated digital signature field, which locks that group of fields.
Each digital signature sets up another 'revision' (what Adobe calls it) of the document. As long as no users change any of the fields that are associated with previous digital signatures, the signatures all remain valid.
We are trying to automate part of this process by having Aspose PDF fill out the each group of data fields (the digital signature is applied manually by the signee) before the form is routed to the next signee. It fills out the first group and the first person signs, which locks the first group. Then Aspose PDF fills out the second group, but when it does it invalidates the first signature.
I am attaching a simple demo app. Run fill1.bat to populate Field 1. It will output demoOut1.pdf. Then sign Signature 1. Notice that it locks Field 1. Then run fill2.bat. It will populate Field 2 and output demoOut2.pdf. You will see that now the first signature is invalid. However, you can manually open demoOut1.pdf and populate Field 2 and it does not invalidate the first signature.
I've also noticed that I don't even have to change the PDF. All I have to do is to open it and save it with Aspose and it will invalidate the signature.
All of this with Aspose PDF 9.8
How can I use Aspose PDF to populate fields in the form without invalidating previous signatures?
Thanks
Steve
The first user fills out the first set of fields and applies his digital signature. When the first signature is applied, all the fields that go with that signature are locked (i.e. made read-only).
The form is then routed to the next user, who repeats the procedure with the next group of fields, filling them out and then applying his digital signature in their associated digital signature field, which locks that group of fields.
Each digital signature sets up another 'revision' (what Adobe calls it) of the document. As long as no users change any of the fields that are associated with previous digital signatures, the signatures all remain valid.
We are trying to automate part of this process by having Aspose PDF fill out the each group of data fields (the digital signature is applied manually by the signee) before the form is routed to the next signee. It fills out the first group and the first person signs, which locks the first group. Then Aspose PDF fills out the second group, but when it does it invalidates the first signature.
I am attaching a simple demo app. Run fill1.bat to populate Field 1. It will output demoOut1.pdf. Then sign Signature 1. Notice that it locks Field 1. Then run fill2.bat. It will populate Field 2 and output demoOut2.pdf. You will see that now the first signature is invalid. However, you can manually open demoOut1.pdf and populate Field 2 and it does not invalidate the first signature.
I've also noticed that I don't even have to change the PDF. All I have to do is to open it and save it with Aspose and it will invalidate the signature.
All of this with Aspose PDF 9.8
How can I use Aspose PDF to populate fields in the form without invalidating previous signatures?
Thanks
Steve