Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.
SOLVED

multiple digital signatures from one person

Avatar

Former Community Member

I have a PDF form that has 10 pages, each page has a Signature field.

I want to put this form in the WorkSpace, and route it in a workflow process, eventually route it to the user who is supposed to sign it.

But I don't want him to sign 10 times (one for each page).

Is it possible to let him only sign the first page, and all the other 9 pages get applied with his signature automatically?

How to do that?

thanks

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

You could have a process that leverages the "Digital Signatures" functionality of LiveCycle.  You could apply the signatures on the server side.  You would need to make sure that the signer's digital certificate was imported into the "Credentials" section of the trust store.  LiveCycle needs access to the P12 or PFX file to create the signature.

I am not aware of any way to automate the signature process on the client side.

Regards

Steve

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

You could have a process that leverages the "Digital Signatures" functionality of LiveCycle.  You could apply the signatures on the server side.  You would need to make sure that the signer's digital certificate was imported into the "Credentials" section of the trust store.  LiveCycle needs access to the P12 or PFX file to create the signature.

I am not aware of any way to automate the signature process on the client side.

Regards

Steve

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] ----