Expand my Community achievements bar.

Learn about Edge Delivery Services in upcoming GEM session
SOLVED

Signing a form without a signature field

Avatar

Former Community Member

We use the certify method of the SignatureServiceClient as described in

http://help.adobe.com/en_US/livecycle/9.0/programLC/help/index.htm?content=000898.html

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?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Steve

the answer is to pass "null" as the signature field parameter in the java certify method.

Thanks for the pointers.

Peter

View solution in original post

6 Replies

Avatar

Former Community Member

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?

Regards

Steve

Avatar

Former Community Member

The SignatureServiceClient certify method takes as parameter a reference to a signature field. 

You wrote:

"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?

Thanks

Peter

Avatar

Former Community Member

Peter

I was asking if you had tried to certify the PDF using the the SignatureServiceClient certify method without creating a signature field.

Steve

Avatar

Former Community Member

Steve

that's what I thought you were saying. But the certify method won't work without  a valid signature field. I haven't tried null.

Peter

Avatar

Former Community Member

Peter

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.

Regards

Steve

Avatar

Correct answer by
Former Community Member

Steve

the answer is to pass "null" as the signature field parameter in the java certify method.

Thanks for the pointers.

Peter

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----