Expand my Community achievements bar.

AEM Forms Header and Footer

Avatar

Level 10

Hi,

All my forms have the same Header and Footer and don't want form authors to author these on all forms.

I, Just like in AEM,  want to create a template with iParsys (for Header), Parsys (for Body) and iParsys (for Footer).

In the JCR /Content/Project-Name folder, at the root level, I will configure Header and Footer once and want all child pages inherit the Header and Footer.

Want to create such a Forms template.

Kindly show me a tutorial in this direction.

Appreciate your help.

Thanks,

Rama.

6 Replies

Avatar

Level 3

HI Rama,

AEM Forms follow similar notion of creating templates as done in AEM Sites. 

In 6.2, a new feature of template editor was added in AEM. With this, you could actually create editable templates(template created using template editor) as detailed here [1]. You could also refer to a video tutorial at [2]

If you are using 6.1, you could follow steps mentioned here [3]. Please Note, these templates are static template meaning, they don't have any editor for authoring them.

Template editor is very powerful and there are many new features added. More details can be found at [4].

Hope the links mentioned below help you easily create AEM Forms Template. Let me know if you have any further questions.

Thanks,

Rishi

 

[1] https://helpx.adobe.com/aem-forms/6-2/template-editor.html

[2] https://www.youtube.com/watch?v=EhhjGwGgGfQ

[3]https://helpx.adobe.com/aem-forms/6-1/create-custom-templates-adaptive-forms-documents.html

[4] https://docs.adobe.com/docs/en/aem/6-2/develop/templates/page-templates-editable.html

Avatar

Level 8

If the header and footer are the same why not create a template with the header and footer or create form fragment header/footer elements.  Using fragments allows you to modify them as needed and have the changes replicated automatically across forms.

Avatar

Level 10

Hi Steve,Rishi,

Thanks for responding quickly.

If I create a template with the header and footer, how to make sure that they are required to be authored only once?

With form fragment header/footer elements, this feature looks to be possible correct?

Thanks,

Rama.

Avatar

Level 10

Hi Rishi,

You mentioned "AEM Forms follow similar notion of creating templates as done in AEM Sites.".

In AEM, if the template has iParsys, if I author header & footer to a page at a folder level, all the child pages underneath that page inherit those header and footer.

But in Forms, where is the concept of parent page, iParsys, child page and all child forms inheriting all iParsys elements from parent?

Thanks,

Rama.

Avatar

Level 3

RNYSHADH SHADH wrote...

Hi Rishi,

You mentioned "AEM Forms follow similar notion of creating templates as done in AEM Sites.".

In AEM, if the template has iParsys, if I author header & footer to a page at a folder level, all the child pages underneath that page inherit those header and footer.

But in Forms, where is the concept of parent page, iParsys, child page and all child forms inheriting all iParsys elements from parent?

Thanks,

Rama.

 

By similar notion, I meant the way templates are created. Components used in the template would be different in both Sites and Forms. 

Just like "parsys" in sites, we have "panel with grid fluid layout" in forms. In fact, grid fluid layout of panel behaves very similar to parsys. If you start using the template editor in forms, you would get answers to your question.

Forms does not have the notion of parent and child. If you wish to re-use content across forms, you could make use of Adaptive Form Fragments.

Avatar

Level 10

Hi Rishi,

There are two types of form fragments requirements in my project:

1. Header and Footer: Content authored once, but used in all forms

2. Common parts of a form: Here it has a set of form elements common in many forms, but content should not replicate. Every form should be presented only those fields with blanks (no values). Ex: Address.

But a Form Fragment once authored, will bear that content correct?

How to achieve #2 above using a Form Fragment.

Appreciate your reply.

Thanks,

Rama.