We want to automatically place stamps in a PDF document. This can be done by the Aspose.PDF API. We also want to identify our stamps, so we can update or delete those stamps. We have found the getStampId and setStampID methods (setStampId | Aspose.PDF for .NET API Reference), but these are of type integer. This could lead to potential problems if we open a PDF document that already has identifiers on stamps. I.e., if a document has stamps with IDs 1 and 5, then we don’t know if these IDs are set by our system or someone else.
Another problem is that these IDs are not visible in Adobe Reader.
Is there a way where we can set our custom stamp properties and identifies, such as a GUID and an Environment GUID of the customer? Then we can see which stamps are set by our system or somebody else.
Another option could be to use the Author and Subject properties of a stamp because they are visible in Adobe Reader. Unfortunately, these properties seem not to be available in de Aspose PDF API.
Do you have suggestions to cope with this problem?
2 Likes
@digiofficerobin
For now, we only have integer Stamp IDs regretfully. However, we could improve this feature by introducing the stamp IDs of type String. An enhancement ticket as PDFNET-51984 has been logged in our issue management system to implement it. We will look into its details and let you know as soon as the ticket is resolved. Please be patient and spare us some time.
We are sorry for the inconvenience.
OK, thanks for creating the enhancement ticket. We will look forward to this new feature. For now we are realizing our feature with the use of the StampID, but this is not ideal.
Is it possible to use the alternative, thus using the Author and Subject field of a stamp?
image.png (27.1 KB)
These values are also visible to users in Adobe Reader.
Notice that there is also a ‘Locked’ checkbox. Maybe we can look also our stamps.
@digiofficerobin
We are afraid that we cannot share any feedback without further diving into the logged ticket. We have however recorded your all concerns and will investigate the ticket from this perspective as well. We will let you know as soon as we make some progress towards ticket resolution. Please spare us some time.
We are sorry for the inconvenience.