Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AEM Forms vs AEM out-of-box Form Component | Which should be preferred and what are the pros and cons?

Avatar

Level 3

Hi,

I have pressing need to automate the online form data capture , submission, notify recipient and storage of the form data from an existing AEM based portal.

However I need to evaluate between using the AEM's out-of-box form component and calling OSGI Services from it's actions (the actions I am aware would need to be custom actions) or do I make use of AEM forms to provide for these form submissions, storage of user input data and notify the specific users?

Please suggest some pros and cons of not using out-of-box Form component vs using AEM Forms.

Thanks,

Hemant

1 Accepted Solution

Avatar

Correct answer by
Level 8

It depends on your use case, if you have one or two simple forms where you want to capture 5 fields of information then the OOTB forms would suffice.  However if you have this requirement, moderately complex, and/or complex forms then AEM Forms would be a better solution.  Here are some of the details as to why I make this statement:

1)  Form model capabilities - being able to bind a form to a schema or XDP form for ease of back end integration

2) Rule builder as an example of being able to add logic to a form without the requirement of scripting including access to web services

3) Document of record - in many cases upon submission of data there is a desire to create an archive of the submission, AEM Forms can create PDF and PDF/A documents by utilizing OOTB services and either no or little coding

4) If you have a need for adding attachments to the form and using them as part of archive or welcome kit - AEM Forms OOTB can convert other document types to PDF and then combine these documents together along with page numbering, table of contents, bookmarks ect....

5) Batch capabilities - perhaps you have a requirement to merge data onto a template and produce print output that's directed to printer or bulk PDF creation

6) OOTB correspondence management capabilities to manage documents such as contracts

7) A much richer set of components that come OOTB to ensure the best possible user experience

😎 One click Marketing Cloud integration - easily add in Analytics, Adobe Sign, Target using the built in Forms Manager

9) Sophisticate form capabilities such as form fragments, form sets, lazy loading - these all ensure ease of form authoring and ensure a high performing user experience

10) Forms Manager to manage all your forms - dictionary translation, initiate review and comment, find relationships between forms and form fragments ect....

The above is a limited list of all the reason to select one implementation versus another but I wanted to at least give you some food for thought.  If you need more detail let me know.

View solution in original post

0 Replies

Avatar

Administrator

Hi Hemant

Please find below the answer i got from the team:

"The simple answer is if you can get things done by with functionality of the out-of-box Form Component then that would be the way to go.  AEM Forms is really designed for advanced forms, security, print related use cases.  Also it requires licensing costs for AEM Forms.

The origination of AEM Forms was from an entirely different product (LiveCycle) that has since been re-branded as AEM Forms."

Thanks and Regards

Kautuk Sahni

Avatar

Level 10

Hi Kautuk,

These are really useful pointers, as this is the question we are often faced with.

Could we also say that AEM Forms (PDF) are adaptive by default, as one of the advantages?

Is there a comprehensive list of enhancements of AEM Forms over out of box Form Component?

Appreciate your responses.

Thanks,

Rama.

Avatar

Administrator

Let me see, if i can pullout some information on this.

~kautuk

Avatar

Level 3

Hello Kautuk,

Did you by any chance get any further information on this topic?

Thanks,

Hemant

Avatar

Administrator

Thanks for reminding me. 

I have again asked them. I will share it with you sooner.

~kautuk

Avatar

Correct answer by
Level 8

It depends on your use case, if you have one or two simple forms where you want to capture 5 fields of information then the OOTB forms would suffice.  However if you have this requirement, moderately complex, and/or complex forms then AEM Forms would be a better solution.  Here are some of the details as to why I make this statement:

1)  Form model capabilities - being able to bind a form to a schema or XDP form for ease of back end integration

2) Rule builder as an example of being able to add logic to a form without the requirement of scripting including access to web services

3) Document of record - in many cases upon submission of data there is a desire to create an archive of the submission, AEM Forms can create PDF and PDF/A documents by utilizing OOTB services and either no or little coding

4) If you have a need for adding attachments to the form and using them as part of archive or welcome kit - AEM Forms OOTB can convert other document types to PDF and then combine these documents together along with page numbering, table of contents, bookmarks ect....

5) Batch capabilities - perhaps you have a requirement to merge data onto a template and produce print output that's directed to printer or bulk PDF creation

6) OOTB correspondence management capabilities to manage documents such as contracts

7) A much richer set of components that come OOTB to ensure the best possible user experience

😎 One click Marketing Cloud integration - easily add in Analytics, Adobe Sign, Target using the built in Forms Manager

9) Sophisticate form capabilities such as form fragments, form sets, lazy loading - these all ensure ease of form authoring and ensure a high performing user experience

10) Forms Manager to manage all your forms - dictionary translation, initiate review and comment, find relationships between forms and form fragments ect....

The above is a limited list of all the reason to select one implementation versus another but I wanted to at least give you some food for thought.  If you need more detail let me know.

Avatar

Level 3

Thanks TundraSteve ! At onset that's quite a handy explanation of comparative data points on the topic.

May i get a little greedy for any more details you may feel comfortable sharing ? 

Example: If you possibly can share any case study on an AEM forms based implementation without disclosing the end business' details like brand / commercials, that will be like icing on the cake smiley

Thanks much again !

- Hemant

Avatar

Level 5

In addition to these any point of views on TouchUI support for "OOTB AEM Site Forms component" vs "AEM Adaptive form component"

Is touchUI support for  "OOTB AEM Site forms component "  available via any service pack we are planning to use AEM 6.2 ?

Avatar

Level 1

Hi,

I'm new to AEM, just wondering if the OOTB form supports asynchronous submission (AJAX) as what AEM Forms does?

Thanks!