Expand my Community achievements bar.

Don’t miss the AEM Skill Exchange in SF on Nov 14—hear from industry leaders, learn best practices, and enhance your AEM strategy with practical tips.
SOLVED

Retrieve attributes from a signature?

Avatar

Level 2

I would like to get the end-user's name out of a digital signature (i.e., subject's name on the signature) while executing the postSign script, so that I can transcribe into a text field elsewhere in the document. I've spent hours surfing to find a solution for this. Is there a way to do it? Thanks for reading.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Look in the Acrobat scripting reference at the signature objct. I am quite certain that it is exposed through that object.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

Look in the Acrobat scripting reference at the signature objct. I am quite certain that it is exposed through that object.

Paul

Avatar

Level 2

Thanks, that source of information worked out for me. For the benefit of others, here is the Adobe Javascript Scripting Reference document he identifed:

http://partners.adobe.com/public/developer/en/acrobat/sdk/AcroJS.pdf

... and then the help I was looking for is the desciption of SignatureInfo object. In the Livecycle javascript in my form, I can now go to the desired username attribute as follows

var digSig = event.target.getField ("MyForm[0]...MyPathstuff [0]...Signature [0]");

digSig.signatureValidate ();

If successful...

var sigInfo= digSig.signatureInfo (); // Gets SignatureInfo object

var sSigner = sigInfo.name;

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