Component Title | Form Button |
Description | The Form Button Component allows for the inclusion of a button to trigger an action on a page. |
Features |
|
Location | /apps/ehi-core/aem65/components/form/button/v1/button |
sling:resourceSuperType | core/wcm/components/form/button/v2/button |
Supported AEM Versions | 6.5 |
Editing Mode | inPlaceEdit |
Component Group | Cheerios Experience |
Use Object | The Button component uses the com.adobe.cq.wcm.core.components.models.Button Sling model as its Use-object. |
The Core Component Form Button component allows for the creation of button field, often to trigger the submission of the form and is intended to be used along with the Form Container component .
The component provides a core.wcm.components.form.button.v2.editor editor client library category that includes JavaScript handling for dialog interaction. It is already included by its edit and design dialogs.
BLOCK cmp-form-button
Extending the components can be done in multiple ways depending on the needs of the brand component.
Use this approach if you do not have any required html markup changes or backend java changes. This will only update the title of the component, componentGroup and point to the resourceSuperType. Optionally can extend the description.
Use this approach if you need to update css classes or add data attributes and do not need to change the backend model, or potentially want to use a different model by retain all of the markup in the component-tmpl.html (Component Template) markup.
The component template is usually named component-tmpl.html this file contains the html markup. Update this file if you need to change the html structure of the component.
Use this approach if you need to change the Sling Model to update the backend logic.
Files that will need to be added when extending:
It is possible to extend more than just the component.html file, if necessary any file that is resourceSupertyped can be extend for example if something needs added to the dialog.
This gives us the flexibility to change our classes or add attributes easily. Say I want to add new javascript I can easily target a different data attribute to trigger my javascript.
The following properties are written to JCR for this Form Button component and are expected to be available as Resource properties: