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

Emailing Interactive PDF

Avatar

Level 2

I have completed an interactive order form and have included a submit Email button in the top left corner of the form. When people complete the form and email it by pushing the button, the form attaches as .xml format and not pdf.  How do I change it to submit as a pdf and not .xml?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Don't use the email submit button ...that is programmed to submit XML. Use a regular button and make it a type Submit. This will activate the Submit tab on the Object palette. You can set the URL as a mailto:emailAdress and in that screen you can also choose the Submit As option ...choose PDF.

You will also have to Reader Extend the form to allow a local save before you can mail a PDF. This can be done in Acrobat under the Advanced/Extend Features in Adobe Reader option.

Paul

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Don't use the email submit button ...that is programmed to submit XML. Use a regular button and make it a type Submit. This will activate the Submit tab on the Object palette. You can set the URL as a mailto:emailAdress and in that screen you can also choose the Submit As option ...choose PDF.

You will also have to Reader Extend the form to allow a local save before you can mail a PDF. This can be done in Acrobat under the Advanced/Extend Features in Adobe Reader option.

Paul

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