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

Digital Signatures

Avatar

Former Community Member

Hi,

I have created the attached timesheet and am wanting my staff to fill it out and sign it electronically to save on printing and paper costs. I have Adobe Acrobat 9 Pro and the signature field works for me in PDF format perfectly. Unfortunately, when I try it on another employee's computer using Adobe Reader 9.0 it will not work. My employees will always be using Reader 9.0 to complete the form.

I have tried troubleshooting and I can't seem to find the solution as Reader suggests that it should be working fine. Is there something that needs to be done in Livecycle designer in order to enable staff to digitally sign the document in Reader?

Thanks,

Kate

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

The form will need to be "Reader Extended" to enable the digital signature capability in Reader.  This can be done using LiveCycle Reader Extensions ES (server product) or Acrobat Proessional (from the Advanced menu, select 'Extend Features in Adobe Reader"

Regards

Steve

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

The form will need to be "Reader Extended" to enable the digital signature capability in Reader.  This can be done using LiveCycle Reader Extensions ES (server product) or Acrobat Proessional (from the Advanced menu, select 'Extend Features in Adobe Reader"

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