The Core Component Form Container Component allows for the creation of simple submission forms.
The form Container Component enables the building of simple information submission forms and features by supporting simple WCM forms and by using a nested structure to allow additional form components.
By using the configure dialog the content editor can define the action triggered by form submission, the URl that should handle the submission, and whether a workflow should be triggered. The template author can use the design dialog to define the allowed components and their mappings similar to the design dialog for the standard layout container in the template editor.
The core components Form Container Component only supports the use of core components form components (button, text, hidden, etc.). Using foundation components form components within the core components form container (and vice versa) is not supported.
The current version of the Form Container Component is v2, which was introduced with release 2.0.0 of the Core Components in January 2018, and is described in this document.
The following table details all supported versions of the component, the AEM versions with which the versions of the component is compatible, and links to documentation for previous versions.
|Component Version||AEM 6.4||AEM 6.5||AEM as a Cloud Service|
release 2.17.4 and prior
For more information about Core Component versions and releases, see the document Core Components Versions.
To experience the Form Container Component as well as see examples of its configuration options as well as HTML and JSON output, visit the Component Library.
The latest technical documentation about the Form Container Component can be found on GitHub.
Further details about developing Core Components can be found in the Core Components developer documentation.
The configure dialog allows the content author to define what actions are taken when the component is submitted.
Depending on the selected Action Type, the available options within the container will change. The available action types are:
Regardless of the type, there are general settings that apply to each action.
When the form is submitted, the post form data action type will pass the submitted data on to a third party as JSON for processing.
There are additional timeout options which a system administrator can adjust to handle the processing of forwarded form data. See the technical documentation on GitHub for more information.
When the form is submitted, the mail action type will send an email to designated recipients.
When the form is submitted, the content of the form will be stored in a designated repository location.
In order to make the management of user-data simpler and to enforce separation of concerns, it is generally not recommended to store user-generated content within the repository.
Instead use the Post Form Data action type to pass user content on to a dedicated service provider.
Regardless of the action type selected, a thank you page can always be defined.
The design dialog allows the template author to define the allowed components and their mappings for the container similar to the design dialog for the standard layout container in the template editor.
The Form Container Component supports the AEM Style System.