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

Separating a 4 page form with global field bindings

Avatar

Level 2

I have a 4 page form that uses global binding for the Name, Address, etc. fields that are common to each of the pages.  When the end-user fills out the form is it possible to break-out each of the 4 pages?  (each of the 4 pages on the form is routed to a different office)   If there is a solution, will the end user need to use Acrobat?

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

I am assuming that each page would have its own name (Page1, Page2, Page3 and Page4). W

hen you are ready you can use the presence property to hide the pages you want. So

if I wanted to send Page1 then you would use the commands:

Page2.presence = "hidden";

Page3.presence = "hidden";

Page4.presence = "hidden";

When you are ready to show the pages again then you woudl use the keyword visible for the presence so the commands would be:

Page2.presence = "visible";

etc.....

Paul

View solution in original post

7 Replies

Avatar

Former Community Member

When yo route the form all 4 pages will be included .....but you can hide and show different pages so that it looks

like only one is sent (and they woudl see only the info that was intended for them). Would this be an acceptable solution?

Paul

Avatar

Level 2

Yes, that would be an acceptable solution.

Could you please detail how I can hide 3 of the 4 pages?  Does the 1st and 4th page have a different "hiding schema" than pages 2 and 3?

Thanks!

Avatar

Correct answer by
Former Community Member

I am assuming that each page would have its own name (Page1, Page2, Page3 and Page4). W

hen you are ready you can use the presence property to hide the pages you want. So

if I wanted to send Page1 then you would use the commands:

Page2.presence = "hidden";

Page3.presence = "hidden";

Page4.presence = "hidden";

When you are ready to show the pages again then you woudl use the keyword visible for the presence so the commands would be:

Page2.presence = "visible";

etc.....

Paul

Avatar

Level 2

Perfect!  Thank you very much for your help Paul.

Avatar

Level 2

Paul,

Thinking this out a little further:  Would it be possible to place 4 buttons at the end of the 4 page form with button 1's action= "submit Page 1", button 2's action="submit Page 2". etc.?  Could button 1 hide pages 2,3 and 4 and submit via email?  Button 2 would hide pages 1,3 and 4, etc.

Thanks for your help!

Avatar

Former Community Member

A submit will send all fields that are bound. The binding is not dynamin - maening that I cannot change the binding on the fly. So if you are intending on sending all fields at one point or other then they must be bound at start up.....and the submitting of prts of a form is not possible. The hiding of the pages is possible but the submit will send all data or the entire form.

Paul

Avatar

Level 2

Paul, thanks for the clarification.

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