How to migrate existing assets from LiveCycle ES4 SP1 to AEM forms JEE?

After you upgrade from Livecycle ES4 SP1 to AEM forms on JEE, your existing asset are also migrated. After upgrade, a synchronization schedule is automatically initated. It runs at a configurable frequency, detects Livecycle applications existing in the repository at the last configured shadow node root path and migrates detected applications to AEM forms on JEE at /content/dam/formsanddocument.

In some senarios, you might be required to manualy initiate syncronization and migration operation. For detailed information, see 'Get existing forms workflow assets.

Additional functionalities available in AEM forms JEE

Folders to arrange assets

Apart from application folders that are kept in sync with the applications residing in Livecycle, AEM Forms now supports another category of folders that do not have a strict structure and allow some additional operations. These folders can hold all kinds of asset types supported in AEM Forms including Adaptive Forms which are not supported in Livecycle applications. For more details, see Using folders to arrange assets

XML Schema Definition

Apart from images, AEM forms now supports a new resource type, XSD (XML Schema Definition) in both the categories of folders described above. XSD could be used as a resource with a form template or be used as a form model for an adaptive form. As mentioned above, the XSDs within a Forms Workflow application would be synced with AEM forms on JEE repository while the ones in general folders would not be synced with AEM forms on JEE repository.

Adaptive Form

Apart from form templates, PDF Forms & Document, AEM forms now supports a new form type, adaptive form. Adaptive forms can dynamically adapt to user responses by adding or removing fields or sections as required. AEM lets you reuse Adobe XML form templates to create adaptive forms. For more details, see 'Introduction to AEM forms'

Publishing & unpublishing forms

The AEM forms server provides two instances: Author and Publish. Author instance is for creating and managing the forms and resources. Publish instance is for staging the forms and related resources that are available for end users. Publishing a form replicates the published form automatically on the configured publish instance. For more details, see Publishing & Unpublishing Assets

Creating and managing reviews for forms

A review is a mechanism that allows one or more reviewers to comment on a form. Steps to set up and manage a review can be found at 'Creating and managing reviews for assets in forms'

Changes in functionalities that existed in LiveCycle ES4 SP1

How does AEM forms JEE handle custom properties?

In AEM forms on JEE, custom properties are assigned based on an asset type. If a custom property has been added to a particular asset type say Form Templates, it would be visible on the metadata properties page of each Form Template present on the system. This behavior is different from the one that was available in Livecycle ES4 SP1 where each asset had to be assigned a custom property individually.

In Livecycle ES4 SP1, custom properties were all by default written into the form binary content in order to be accessed in Form template designer or PDF reader.

In AEM forms, apart from a custom property that is written into the form binary content, you can choose to create a custom property that only resides in AEM forms metadata.

For details on how to add a custom property to an asset in AEM forms, see Add custom metadata

How to support the existing custom properties present in migrated forms?

  1. Navigate to the metadata schema editor (Tools > Assets > Metadata Schemas)

  2. Edit the schema of the asset type depending on the type of the concerned form.

  3. Add a field for the custom property.

  4. Under the Settings tab that opens in the right panel, fill in value ‘./jcr:content/metadata/fmg:<property_name>’ for ‘Map to property’ field. (For example: './jcr:content/metadata/fmg:department')


    The namespace 'fmg' ensures that the custom property is written in the form binary content and is thus available in the form when it is downloaded and opened in the desinger or reader. If this namespace is not added, the property will function as a custom property but will not be available inside the downloaded form.

How to handle the Activate/Deactivate status that existed in Livecycle ES4 SP1?

The activate/deactivate functionality that was present in Livecycle ES4 SP1 is different from publish/unpublish that has been introduced in AEM Froms JEE. However, you may want to retain the functionality of marking a form as active/inactive because it was supported in Forms Portal, where you could search for forms based on this property too.

So, this functionality can be achieved in AEM forms as well by maintaining the active/inactive status as a metadata custom property. Perform the following steps to achieve active/inactive status of forms:

  1. Navigate to the metadata schema editor (Tools > Assets > Metadata Schemas)

  2. Edit the schema of the asset type for which you wish to maintain the status.

  3. Drag and drop a dropdown component from Build Form section in the right-side panel.

  4. Select the dragged component such that the 'Settings' section opens on the right-side panel.

  5. Enter the following values under Settings

    • Field Label - Activation Status
    • Map to property - ./jcr:content/metadata/status
  6. Click the + icon under Choices. Add Inactive for option text and false for option value. Similarly, add another choice with Active for option text and true for option value.

  7. Click Done after making all the changes. The property would now be visible to you on the properties page of the asset.  

    Any migrated assets containing this property would display correct values.  


AEM Forms recommends you to use Publish/Unpublish. This functionality of adding Active/Inactive as metadata properties is only for backward compatibility.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy