Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

RADIO BUTTONS

Avatar

Level 4

I am creating another appliation form using 'Yes' and 'No' radio buttons whereby if the applicant chooses no I want additional information boxes to pop up.  I have been able to duplicate this by using the Purchase Order form in the list of samples.

I have a couple of additional requests:

1.     The two 'Yes' 'No' radio buttons are in a small box to begin with but when the applicant chooses 'No' the text box expand to include the additional information; and

2.     How do I have the additional information boxes not show on the screen until 'No' is selected but print out should the applicant choose to manually complete the form.

Hope these two requests make sense.  I have attached the part that I am referring to which might help.

Regards

Jen

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

here is a modified sample. Resizing objects is a little bit tricky so have a look at the code. The pre and post print events are used to make fields visible/invisible accordingly.

Paul

View solution in original post

3 Replies

Avatar

Level 4

For 1) you could bind the radio buttons to an identically pair of radio buttons that will only be shown if the user checks no and with the only difference that they include the additional text. The original will hidethemselves if no is checked.

For 2) making it visible on preprint should do the job.

Good Luck

Lisa

Avatar

Correct answer by
Former Community Member

here is a modified sample. Resizing objects is a little bit tricky so have a look at the code. The pre and post print events are used to make fields visible/invisible accordingly.

Paul

Avatar

Level 4

Thanks.

Paul I can't access the attachment can you e-mail to me.  bluey72@live.com

Jen

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