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.
Read More & Register today!
SOLVED

header and footer

Avatar

Former Community Member
8/25/11 8:19:05 PM

Hi,

i am creating a form in livecycle with expandable text input boxes. when filled the text boxes can flow onto the next page. I'd like to set up the form so as that when the text expands onto a new page a header and footer appear on the new page. is this possible?

Views

854

Replies

1

Total Likes

Translate
Translate
1 Accepted Solution

Avatar

Correct answer by
Former Community Member
8/26/11 5:42:09 AM

Put your header and footer on a master page and they will appear on every page regardless if a field breaks across it or not.

paul

View solution in original post

Views

451

Replies

0

Total Likes

Translate
Translate
Jump to reply
1 Reply

Avatar

Correct answer by
Former Community Member
8/26/11 5:42:09 AM

Put your header and footer on a master page and they will appear on every page regardless if a field breaks across it or not.

paul

Views

452

Replies

0

Total Likes

Translate
Translate
Jump to reply
Related Conversations
Header at the end of row item issue Solved

Views

1.3K

Likes

0

Replies

1
Is Adobe live cycle ES2 9.0.5 version compatible with SQL server 2017 and above ? Solved

Views

814

Likes

0

Replies

2
A table row repeats when footer is set to be on the final page

Views

1.7K

Likes

0

Replies

6
FormCalc error messages after signing (and locking) form: cannot change properties (of locked fields)

Views

791

Likes

0

Replies

2
Loss of header in case of multiple pages

Views

443

Likes

0

Replies

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