AEM as a Cloud Service: Composite field edit restriction in Content Fragment Touch-UI editor
This article explains when the enhancement that prevents editing of composite fields in the Adobe Experience Manager as a Cloud Service (AEMaaCS) Content Fragment Touch-UI editor becomes active. Until the environment is upgraded to the release that includes the enhancement, composite fields remain editable and continue to exhibit the existing behavior. To resolve the issue, verify your current release version and confirm that the enhancement is available in your environment.
Description description
Environment
- Adobe Experience Manager as a Cloud Service (AEMaaCS)
- Content Fragment Touch-UI editor
Issue/Symptoms
- Composite fields in Content Fragments remain editable in the Touch-UI editor.
- The expected edit restriction is not enforced.
- The behavior persists until the environment is upgraded to the release that includes the enhancement.
Root cause
The enhancement that restricts editing of composite fields in the Content Fragment Touch-UI editor is scheduled for activation in a future release. Until the environment is upgraded to that release, the existing behavior remains unchanged.
Resolution resolution
Follow the steps below to resolve the issue:
- Review the AEM as a Cloud Service release notes for the rollout of the composite field edit restriction enhancement in the Content Fragment Touch-UI editor.
- Confirm the release version currently running in your environment. The enhancement is scheduled to become active with the 2026.9.0 release.
- If your environment is running an earlier release, such as 2026.8.0, the composite field edit restriction will not yet be available.
- After the environment is upgraded to 2026.9.0, open a Content Fragment that contains composite fields in the Touch-UI editor.
- Verify that composite fields display a placeholder message such as: This field can’t be edited. This indicates that the enhancement is active.
- If unexpected behavior continues after the upgrade, collect specific examples and contact Adobe Support for further investigation.