The ImageMaster Stamping Service can be used to retrieve a modified document rendition where a watermark is visible as an overlay. This can be configured in the AdminClient [UM AdminClient]:
-
Stamps configuration (for Stamping Service): Create a stamp and specify how it looks.
-
Stamping (for Stamping Service): Assign an existing stamp to a document type and specify conditions when to apply it.
Rules specify, when a stamp is applied.
-
Stamping can be related to specific use cases like:
-
Display
-
Export
-
Download
-
Print
-
Send Mail
-
-
A header can be set in the web services to apply stamps in document retrieval operations.
For details see Stamping Service header (REST)/Header for the Stamping Service (SOAP).
Supported formats
The following MIME types are supported by the Stamping Service. Note that text files will be changed to PDF to enable an overlay:
|
MIME type |
File extensions |
|---|---|
|
application/pdf |
|
|
text/plain |
txt (retrieved document will be a PDF) |
|
image/tiff image/tif |
tiff/tif |
|
image/jpg image/jpeg image/jpe |
jpeg/jpg |
|
Table 356: Stamping Service MIME types and file extensions |
|
Font-dependent performance during PDF stamping
A performance issue may occur during PDF stamping depending on the font used in the document. Processing time can vary significantly because font rendering and internal font handling are part of the PDF processing pipeline. In observed cases, documents using standard PDF base fonts such as Helvetica were processed faster than documents using embedded TrueType fonts such as Liberation Mono.
Standard PDF base fonts are typically processed more efficiently. In contrast, embedded TrueType fonts may require additional rendering, embedding, and layout calculations. As a result, stamping operations can take considerably longer for documents that use such fonts.
This behavior results from font-dependent processing in a third-party PDF component outside the direct control of the application and cannot be optimized further within the application code.