Documentation

Changes to filter not reflecting in AEM UI

Last update: Tue Nov 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

Changes to group predicates or newly added predicates in AEM don’t appear in the UI, even after successful pipeline deployments. It happens due to reused cached artifacts or misconfigured deployment settings. To fix this, update pipeline variables, adjust configuration files, and redeploy the code.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptoms

  • Changes made to a group predicate, such as adding new predicates or creating new group predicates, don’t appear in the AEM UI.
  • Updates to existing search predicates within a group predicate are reflected, but newly added predicates are not visible.
  • This behavior persists despite deploying pipelines successfully.

Steps to replicate:

  1. Verify that the CM_DISABLE_BUILD_REUSE variable is set to true for the development pipeline to prevent reuse of old artifacts.
  2. Make dummy changes under the ui.content module and deploy them on the development environment using Cloud Manager.
  3. Check if changes are reflected in the AEM UI after deployment.

Resolution resolution

  1. When the changes made to the ui.content module don’t reflect:

    1. In the ui.content module module’s pom.xml file, remove <cloudManagerTarget>none</cloudManagerTarget> element. This tag excludes the module from Cloud Manager builds, which prevents your changes from being deployed. Removing it ensures the ui.content module is included in the pipeline deployment.
    2. Redeploy the code using Cloud Manager.

  2. If removing <cloudManagerTarget> doesn’t resolve the issue:

    1. Manually increment submodule versions in development and QA branches by setting 1.0.0-SNAPSHOT in all relevant pom.xml files, including the main pom.xml.
    2. Build the project locally and ensure it builds successfully.
    3. Deploy this updated code on both development and QA environments via their respective pipelines.

  3. Test by making additional changes to confirm that subsequent deployments reflect updates correctly in both environments.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f