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

Submit Button Question

Avatar

Level 2

I added a submit button to a form in LiveCycle Designer and even though I choose"Save As static pdf", when I hit the submit button, the form that attaches to the e-mail is an XML document rather than pdf. Isn't that going to cause problems if our goal is simply for our  recipeints to download the form off the Internet, fill it out, then  e-mail it back to us? Aren't xml docs for more sophisticated, online  submissions, rather than e-mailing?

Untitled-1 copy.jpg

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

There is no relationship between the format of the saved PDF form and the submit function. Additionally, there are two form objects that can be used for submission, Email Submit Button and Button. Button can be configured to submit a PDF, XDP, XML and URL-encoded data. You selected the Email Submit Button and the default behaviour for the submit button is to attach the form XML to an email.

Steve

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

There is no relationship between the format of the saved PDF form and the submit function. Additionally, there are two form objects that can be used for submission, Email Submit Button and Button. Button can be configured to submit a PDF, XDP, XML and URL-encoded data. You selected the Email Submit Button and the default behaviour for the submit button is to attach the form XML to an email.

Steve

Avatar

Level 1

Also to submit the PDF rather than XML from Reader the form will need to be Reader Extended.

PL

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