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

Making two parts to a form

Avatar

Level 3

I will try to explain this the best way I can.  I created a form which has quite a few if then functions.  The start of the form has three radio button choices and base on one of those three selections the form changes.  My issue is or is there a way to have everything in one form but in sections so if the first radio button is selected, part I shows up or if radio button 2 is selected then part 2 shows up.  My problem is the objects in the form all run together at the moment but I want to be able to create page breaks I guess and create sections of the form.  Any help on this is much appreciated.  If you need more clarification just let me know. Thanks.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

It is certainly possible.

I woudl wrap each section into its own subform and simply set the subform to hidden. Then when you click the appropriate radio button you can make the subform visible. This causes all of its child objects to inherit the parent setting.

Hope that helps

Paul

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

It is certainly possible.

I woudl wrap each section into its own subform and simply set the subform to hidden. Then when you click the appropriate radio button you can make the subform visible. This causes all of its child objects to inherit the parent setting.

Hope that helps

Paul

Avatar

Level 3

Thank you! That's exactly what I needed.

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