Expand my Community achievements bar.

SOLVED

Email / HTTP submit buttons not using entered email

Avatar

Former Community Member

Hi there,

I am having a bit of trouble with my form and getting my email buttons to send to the address typed in the 'email addresss' box of the Object palette.  After having distributed the form and when the form is to be completed and submitted the form reverts to my email address and not the one allocated to the button.  I have also tried using the HTTP button "mailto:..." but this did not work either.

Can someone please help provide some guidance.  I know the answer will be straightforward and may have something to do with initial set-up details, but I cannot work out how to fix it.

I am using Livecycle Designer ES2 9.0

Thank you in advance.

Lyndle

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Hi folks,

The issue was with Acrobat Pro not Livecycle.  Acrobat Pro assumed that as I created the form I was also going to be receiving the completed forms submitted on the same email, which was not the case. I needed to change my Acrobat Pro 'identity' to the email i wanted to receive the forms with before distributing.  To do this:

Acrobat Pro --> Edit --> Preferences --> Identity

Hope this helps someone else in the future.

Cheers,

Lyndle

View solution in original post

1 Reply

Avatar

Correct answer by
Former Community Member

Hi folks,

The issue was with Acrobat Pro not Livecycle.  Acrobat Pro assumed that as I created the form I was also going to be receiving the completed forms submitted on the same email, which was not the case. I needed to change my Acrobat Pro 'identity' to the email i wanted to receive the forms with before distributing.  To do this:

Acrobat Pro --> Edit --> Preferences --> Identity

Hope this helps someone else in the future.

Cheers,

Lyndle

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