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

Eliminate the requirement of saving form when signing

Avatar

Level 2

Is it possible for me to code the signature field on my form to not prompt the user to save when signing? 

After I distribute my form, each user must sign it with digital ID and then they click a button on the form that attaches the signed form to an email in Outlook. I have many of the users requesting that they not have to save it when signing it.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

When applying a digital signature to a PDF, it has to be re-saved.  There is no way to avoid this when an end user manually signs the document.

Here is another thread related to your question...  http://forums.adobe.com/message/2257437#2257437http://

Regards

Steve

View solution in original post

5 Replies

Avatar

Correct answer by
Former Community Member

When applying a digital signature to a PDF, it has to be re-saved.  There is no way to avoid this when an end user manually signs the document.

Here is another thread related to your question...  http://forums.adobe.com/message/2257437#2257437http://

Regards

Steve

Avatar

Level 2

Ok, this answered a question that I had, I understand it, even though it will complicate things for me.  If there is no way around saving the file after signing, is there a way to automate the location of the saved file? I have a bit of a phobia of 600 people saving these temporarily signed pdfs all over their HDDs just so they can send them back, and then someone else being able to see the completed form who shouldn't. I would love to completely automate the process of saving the file after signing.

Avatar

Former Community Member

Hi 2425pike,

Did you get answer...pls share me. I have same requirement.

Srujan

Avatar

Level 2

Yes, answer was on the same post. You cannot eliminate that requirement of saving.

Rich Gwynn

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