adobe / adobe/aem-modernize-tools

[Enhancement] Support to convert AEM foundation forms to core component based AF

Open
#209 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
62
Forks
45
PR merge metrics
No merged PRs in 30d

Description

### Expected Behaviour

Currently, AEM Forms customers both on-premises and cloud services face challenges in migrating their foundation forms to core component-based Adaptive Forms. To address this, we aim to utilize aem-modernize-tools to streamline the migration process.

To ensure clarity and efficiency, we intend to introduce a dedicated tile for forms. A separate tile for forms is required since:

1. The All-in-One conversion job mandates configuration paths and other parameters for policy conversion, which are unnecessary for forms.
2. The Component conversion job lacks Page Handling options essential for forms.
3. Adaptive Forms (AF) are accessible both as a Site page located at /content/forms/af and as a Digital Asset Management (DAM) asset at /content/dam/formsanddocument. Therefore, to utilize the "Copy to Target" page policy, we must copy the source form (asset) to the target, a functionality not available in any of the existing conversion jobs.
4. Furthermore, this separation ensures that any future additions of form-specific code to the tool won't impact other conversion jobs.
5. To prevent user confusion regarding the appropriate job to execute for specific purposes.

### Actual Behaviour

### Reproduce Scenario (including but not limited to)

#### Steps to Reproduce

#### Platform and Version

#### Sample Code that illustrates the problem
https://github.com/adobe/aem-modernize-tools/pull/210
Forms-modernizer PR: https://git.corp.adobe.com/livecycle/forms-modernizer/pull/2 [in progress]

#### Logs taken while reproducing problem

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the requirements in this issue and the referenced aem-modernize-tools PR #210. The forms-modernizer PR is marked in progress, so check its current state before beginning. Done means a dedicated forms conversion tile supports the stated policy, page-handling, and source-asset copying needs without affecting other conversion jobs.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.