Metadata allows for easier categorization and organization of assets and helps users who are looking for a specific asset.
AEM forms, by default, provides a defined set of metadata for each asset type. Beyond the default metadata, you can add custom metadata to each of the asset types. AEM forms also provides you with the right means of creating, managing, and exchanging all this metadata efficiently for your forms.
If you're a developer or a site owner, you can customize Forms Portal, the end-user interface for AEM forms to reflect the metadata you're using in your organization. For more information abouts Forms Portal, see Introduction to publishing forms on a portal.
In AEM forms, the list of metadata properties associated with an asset depends on its type. Also, if you add any custom metadata property, it is added across all the assets of the type on which the custom metadata was added.
The following asset types are supported in AEM forms:
- Form templates (XFA forms)
- PDF forms
- Document (flat PDFs)
- Adaptive forms
|Property name||Asset type||Description
|Title||All but resource||Display name of the form.
|Description||All but resource||Description of the form. The user can specify this value.
A read-only value specifying the type of asset. It can have one of the following values:
|Created||All||A read-only value specifying the time of asset creation.|
|Last modification date||All||A read-only value specifying the time when the asset was last modified.|
|Author||All but resource||
A read-only value that is automatically computed based on the form type.
|Status||All but resource||
A read-only value that defines one of the following states of a form:
|Last publish date||All but resource||A read-only value specifying the time when form was last published.|
|Publish on/off time||All but resource||
Time at which the form is scheduled to be automatically published/unpublished. The user sets this value on editing metadata.
To configure a user-specified URL for submitting form data to a servlet.
Submit URL can be configured using any of the following methods, listed in order of precedence:
|HTML render profile||Form template||The HTML render profile used while rendering a Form Template in HTML format.|
This option allows the user to specify the rendering format of the form when the forms are published:
This option is used for restricting the rendering format of the forms only on forms portal where they are visible to the end user.
|Tags||All but resource||Labels associated to the form to facilitate quick and easy search.|
List of assets (other forms or resources) that this form is related to. These assets can fall in following two categories:
These assets are displayed as links and their metadata can be accessed directly by clicking them.
|Form model (XDP/XSD) selection||Adaptive form||
Specifies which form model is used while authoring the adaptive form. This property can have following values:
A form model once selected can be updated but not removed.
Assets have existing property values, which can be viewed in read-only mode. This metadata is originated at the time of form upload or form creation.
The property page that opens displays a schema containing only those metadata properties that hold some value.
The properties page has a toolbar containing two action icons:
- Edit: Edit the metadata property values
- View: Navigate to the form details page, which opens the form in the preview mode.
The content portion is divided in two parts:
- Left panel contains thumbnail of the form
- Right panel contains metadata properties in the read-only mode, distributed across various tabs.
You can edit the value of existing metadata properties or add new values to an existing metadata property field (for example, when a metadata field is blank).
This page has a toolbar containing two action icons different from those in view mode:
- Cancel: Cancel any changes made to metadata property values so far
- Done: Save all the changes made to metadata property values so far
Both these actions direct the user back to read-only mode of the properties page containing the updated values.
The left panel in the properties page displays the thumbnail of the form. By default, the thumbnail displayed is the one generated at the time of form creation (adaptive form) or at the time of form upload.
For all form types, you have the option to upload an image by clicking Upload Image and browsing for an image file from the local directory. The selected image is used as a thumbnail instead of the default one.
For adaptive forms, additional functionality is provided, which allows the user to generate a thumbnail as a snapshot of the current adaptive form preview. Since AEM forms also supports authoring of adaptive forms, the preview of the adaptive form may change every time you change the adaptive form. This functionality to generate a thumbnail helps you obtain a fresh thumbnail for the adaptive form based on the current preview status. Click Generate Preview to carry out this action.
Once a new image is uploaded or generated, the thumbnail is replaced by this image and cannot be reset to the previous image.
Apart from the metadata provided out of the box, AEM forms supports new custom metadata.
A tool (Metadata Schema Editor) is provided to define the schema for the metadata layout; that is, the layout of what appears in the Properties page of a form. The Metadata Schema Editor lets you add or modify a custom schema for your assets.
AEM forms exposes the metadata schemas of the supported forms types in this tool. This way, you can access these schemas and use the functionality provided in metadata schema editor to add custom properties.
Click a component that you just dragged. In the Settings tab that opens in the right panel, fill in information for the following fields:
Under Map to property field, you can see a prefilled value './jcr:content/metadata/default'. Change the ‘default’ to a desired property name, which is used to store the property in crx repository (For example: './jcr:content/metadata/department')
Do not change the prefix ‘./jcr:content/metadata/’ as it defines the path where the property is stored.
Also, the property name must be unique to avoid writing values for two or more properties at the same location in repository. So, it is recommended that you change the value 'default'.