We use the certify method of the SignatureServiceClient as described in
Because we simply want to sign the form, we create an invisible signature field and pass that to the certify method.
This seems to be a long way around and is in fact causing us problems with the layout.
Question: Is it possible to sign the form not using a signature field?
Using the Workbench tool, you can create a process to "certify" a PDF using the CertifyPDF operation without needing to specifiy a signature field. The same should be possible when using the APIs. Have you tried to certify the PDF without creating a signature field first?
The SignatureServiceClient certify method takes as parameter a reference to a signature field.
"Have you tried to certify the PDF without creating a signature field first?"
Are you referring to another way of certifying the PDF or to the SignatureServiceClient certify method?
That's odd, as it is possible to certify a PDF (without a signature field) when using a process created in Workbench. You would think that the APIs would function the same, unless the CertifyPDF operation in Workbench creates an invisible signature field as part of the certify operation.
You could check with Adobe Technical support to confirm.