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

Help with check box behavior

Avatar

Level 1

Hello everyone:

I am really new on this Live Cycle world and I am having issues to be able to create a form with check boxes that are optional.

This is what I mean:

Dress and Appearance

Looked neat and well-groomed?

Yes No

r r

Appeared confident?

Yes No

r r

Were first impressions good?

Yes No

r r

I only want to be able to click one of the boxes (yes or no) on each question. I have try for hours reading some scripts and I do not get it.

Any help please will be greatly aprecciated.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

You want Radio button behaviour but with a checkbox look and feel. Chnage your objects to radio buttons and make sure that the buttons for each question are under the same radiobuttonlist in the hierarchy (this is what sets up the exclusivity). Now on the Radiobutton objects themselves you can change the appearance to a sunken square and now they will look like checkboxes but act like radiobuttons.

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

You want Radio button behaviour but with a checkbox look and feel. Chnage your objects to radio buttons and make sure that the buttons for each question are under the same radiobuttonlist in the hierarchy (this is what sets up the exclusivity). Now on the Radiobutton objects themselves you can change the appearance to a sunken square and now they will look like checkboxes but act like radiobuttons.

Paul

Avatar

Level 1

Thank you very much. This work for me right away.

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