Image component image-adaptive-forms-core-component

An Image component in an Adaptive Form is a way to include images in a form. These images can be used to enhance the overall design of the form, provide additional information, or serve as a visual aid to help users understand the form’s purpose. The image component can be used to add a logo, a photo, or a graphic in the form.

For accessibility, it is important to specify Alternate text to the image to provide a short, descriptive text alternative for the image, that describes the image to users who cannot see it.



Usage reasons-to-use-image-in-a-form

There are several reasons why it is beneficial to include an Image component in an Adaptive Form, including:

  • Branding: An image can be used to display the logo or name of the organization that created the form, helping to establish brand recognition and credibility.

  • Visual Aids: An image can help to provide an extra level of information to users, by serving as a visual aid to help users understand the form’s purpose.

  • Decoration: An image can be used to enhance the overall design of the form and make it more visually appealing.

  • User Experience: An image can be used to make the form more user-friendly by providing a clear and intuitive way for users to access and fill in form fields.

Version and Compatibility version-and-compatibility

The Adaptive Forms Accordion Core Component was released in Feb 2023 as part of the Core Components 2.0.4 for Cloud Service and Core Components 1.1.12 for AEM Forms or later. Here’s a table showing all supported versions, AEM compatibility, and links to corresponding documentation:

Component Version
AEM as a Cloud Service
AEM Forms or later
Compatible with
release 2.0.4 and later
Compatible with
release 1.1.12 and later but less than 2.0.0.

For information on Core Component versions and releases, refer to the Core Components Versions document.

Technical Details technical-details

Get the latest information on the Adaptive Forms Image Core Component in the technical documentation on GitHub. For more on developing Core Components, check out the Core Components developer documentation.

Configure Dialog configure-dialog

You can easily customize your image experience for visitors with the Configure Dialog. You can also define image options with ease for a seamless user experience.

Properties tab

  • Name - You can identify a form component easily with its unique name both in the form and in the rule editor, but the name must not contain spaces or special characters.

  • Title - With its Title, you can easily identify a component in a form and by default, the title appears on top of the component. If you do not add a title, the name of the component is displayed instead of the title text.

  • Mark as Unbound Form Element: Select the option to configure a form field not linked to any schema. This option allows you to save data without updating the data source. It also enables you to handle data in a custom way, separate from standard database integration.

  • Description - A description is a brief text explanation that provides additional information or clarification about the purpose of a specific image.

  • Drop an asset here or browse for a file to upload - This option allows to drop an asset such as image with mouse drag and drop. You can also upload a file from a local file system using the Browse button. After adding an image, three buttons appear at the bottom of the image:

    • Edit - Tap or click Edit to manage the renditions of the asset in the Assets Editor.
    • Clear - Tap or click Clear to de-select the currently selected image.
    • Pick - Tap or click Pick option to select another image from Assets folder.
  • Alternate text - This option is used to enter the text that provides a short and descriptive text alternative for the image, that describes the image to visually impaired users.

  • Hide Component - Select the option to hide the component from the form. The component remains accessible for other purposes, such as using it for calculations in the Rule Editor. This is useful when you need to store information that doesn’t need to be seen or directly changed by the user.

Design Dialog design-dialog

Design Dialog is used to define and manage CSS styles for the Image component.

Styles Tab styles-tab

The tab is used to define and manage CSS styles for a component. The Adaptive Forms Image Core Component supports the AEM Style System.

Design Dialog

  • Default CSS Classes: You can provide a default CSS class for the Adaptive Forms Image Core Component.

  • Allowed Styles: You can define styles by providing a name and the CSS class that represents the style. For example, you can create a style named “bold text” and provide the CSS class “font-weight: bold”. You can use or apply these styles to an Adaptive Form in Adaptive Forms editor. To apply a style, in Adaptive Forms editor, select the component you want to apply the style to, navigate to the properties dialog, and select the desired style from the Styles drop-down list. If you need to update or modify the styles, simply return to the Design Dialog, update the styles in the styles tab, and save the changes.

Custom Properties

Custom Properties Dialog

Custom properties allows you to associate custom attributes (key-value pairs) to an Adaptive Form core component using the form template. The custom properties are reflected in the properties section of the headless rendition of the component. It allows creating dynamic form behavior that adapts based on the custom attributes values. For example, developers can design various renditions of a Headless Forms component for mobile, desktop, or web platforms, significantly enhancing the user experience across a wide array of devices.

  • Group Name: You can provide a name to identify the custom property group. You can add, delete, or rearrange multiple custom property groups. After adding the custom property group, you can see the following options:

    • Key-Value Pairs: You can add multiple custom property names and custom property values by clicking the Add button for each custom property group.

    • Delete: Tap or click to delete the custom property name and custom property value.

    • Rearrange: Tap or click and drag to rearrange the order of the custom property name and custom property value.

See Also see-also