Expand my Community achievements bar.

Radically easy to access on brand approved content for distribution and omnichannel performant delivery. AEM Assets Content Hub and Dynamic Media with OpenAPI capabilities is now GA.
SOLVED

Email Addresses Attached to Check Boxes

Avatar

Level 1

I am new to LiveCycle.  I am creating a form that is being used by students to apply for leadership positions on campus.  Depending upon which positions they wish to apply for, the form needs to be submitted to a corresponding email address.  Currently, at the end of the form I have submit buttons which is confusing.

Is it possible to set up my form so that when a check box is selected the corresponding email address is added to the submit button?  So if I check box 1, 4, and 10, when I click the submit button the form is sent to email1, email4, and email10.

Thanks, for any help you might be able to provide.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

Here is a sample that I created with what I think you want.

Paul

View solution in original post

4 Replies

Avatar

Correct answer by
Former Community Member

Here is a sample that I created with what I think you want.

Paul

Avatar

Level 1

Thanks Paul.  I have no idea what I am doing with script but made lots of copies of the file and experimented.  I am not entirely sure how but I have everything working the way I needed it to though.  Thank you so much.  This will streamline our process immensely.

Avatar

Level 2

Does it matter what the flow direction is?

Avatar

Level 2

Figured it out. Thanks for the post:)

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