Problem with adaptive form fragment adding components

Hi ​@brackenk1997 

The No design at /etc/designs/fd/af/default. Using default message is generally a fallback warning. It is not, by itself, the reason why the Add Component control, drag-and-drop, or component configuration dialog is unavailable. Please validate the following in this order.

1. Make sure the editor is in Edit mode
In the first screenshot, the top-right mode selector shows Design. The Allowed Components, Default Components, and Layout Settings dialog belongs to Design mode. Switch the mode selector to: Edit

Then select guideRootPanel from the Content tree and try to add a component using the Insert Component (+) action or the Components browser.

Adobe documents the Adaptive Forms editor as supporting component insertion, drag-and-drop, and component-property editing from the authoring UI. https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/forms/getting-started/introduction-forms-authoring

2. Confirm that the form and fragment use the same component generation

Check the fragment in CRXDE Lite and inspect its effective cq:template and sling:resourceType values. If the fragment uses:  /libs/fd/af/templateForFragment/defaultFragmentTemplate

then it is a Foundation Components / AFv1 fragment.

That template must be used with a Foundation-based Adaptive Form. If the parent form is based on Adaptive Forms Core Components / AFv2, create a new fragment using a Core Components-based fragment template and a Core Components-based theme. Do not fix this by manually changing cq:template on an existing fragment because the underlying content structure and resource types are different.

Adobe specifically distinguishes between:

• Core Components-based fragment templates
• Foundation Components-based fragment templates
• The default /libs/fd/af/templateForFragment/defaultFragmentTemplate, which is the Foundation template https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/forms/adaptive-forms-core-components/adaptive-form-fragment-core-components

3. Install the matching AEM Forms add-on

For AEM 6.5 LTS SP2, install the AEM Forms add-on that corresponds to the exact AEM LTS SP2 build.

Do not combine:

• an older Forms add-on with the LTS SP2 runtime
• multiple versions of Core Components
• Core Forms Components from an unrelated release
• old custom overlays with the newer Forms authoring client libraries

After installation, verify in:  /system/console/bundles

that the Forms and Adaptive Forms Core Components bundles are active.

Adobe's release guidance requires installing the corresponding Forms add-on whenever an AEM Service Pack or upgrade is applied. https://experienceleague.adobe.com/en/docs/experience-manager-release-information/aem-release-updates/forms-updates/aem-forms-releases

The Adaptive Forms Fragment Core Component is supported on AEM 6.5 Forms from the supported Core Components release onward.

4. Check the feature toggles if the Core Components fragment template is missing

On affected AEM 6.5 Forms builds, the Core Components fragment creation/template flow may still be gated by feature toggles. Go to: /system/console/configMgr Open: Adobe Granite Dynamic Toggle Provider 
Add the required toggle IDs under Enabled Toggles, save the configuration, and refresh the authoring page. For affected 6.5 builds, verify at least:  FT_FORMS-14833 FT_FORMS-2494

Also check the enabled-toggle response:/etc.clientlibs/toggles.json 

The exact toggle set is release-dependent, so it should be validated against the installed Forms add-on/build. Adobe documents the supported method for enabling toggles through the Dynamic Toggle Provider. https://experienceleague.adobe.com/en/docs/experience-manager-65-lts/content/forms/adaptive-forms-core-components/enable-feature-toggle

A restart is normally not required for a toggle change, but refresh the editor and clear the browser cache before retesting.

5. Recreate and test a clean fragment

After correcting the template and package setup:

• Create a new Adaptive Form Fragment.
• Select None as the form model for the first test.
• Select the correct Foundation or Core Components fragment template.
• Open the fragment directly from the Forms console.
• Confirm that the editor is in Edit mode.
• Add one standard text component.
• Open the component properties using the wrench icon.
• Test drag-and-drop with an out-of-the-box component.

Do not test initially with a fragment containing custom components, custom client libraries, overlays, or a schema/FDM. First prove that the OOTB fragment editor works.

6. If the issue still occurs, check the browser Network tab

Look for failed requests such as:

guideRootPanel.treejson

pageinfo.json

/content/forms/af/<fragment>.html

Also verify that the author has the required Forms authoring permissions, including membership in the appropriate Forms groups.