JSON files trigger unwanted DAM Update Asset workflow in AEM

In AEM, uploading JSON files to Assets triggers the DAM Update Asset workflow, resulting in unwanted processing and rendition creation. To fix this issue, update the workflow launcher configuration to exclude JSON files from DAM Update Asset workflow execution.

Description description

Environment

  • Product: Adobe Experience Manager (AEM) Managed Services Support, v6.5
  • Module: Assets
  • Instance: Staging

Issue/Symptoms

Uploading or modifying a JSON file in AEM Assets triggers the DAM Update Asset workflow, causing unnecessary processing such as rendition creation for these assets.

Resolution resolution

To fix this issue, follow these steps:

  1. Navigate to Tools > Workflow > Launchers in AEM.

  2. Locate all launchers associated with the DAM Update Asset workflow, typically configured for node creation or modification under /content/dam.

  3. Open the properties of each relevant launcher configuration.

  4. Add exclusion conditions to prevent triggering on JSON files:

    • Set a condition to exclude assets where jcr:content/metadata/dc:format is equal to application/json.
    • Set an additional condition to exclude assets where jcr:content/jcr:mimeType is equal to application/json.

Note: Apply both conditions separately across all relevant launcher configurations (“globbing patterns”) related to the DAM Update Asset workflow.
5. Save and synchronize your changes.
6. Test by uploading a JSON file and verify that the DAM Update Asset workflow does not trigger for this asset.
7. Confirm that other asset types (such as images) continue to process normally through the workflow.

Notes

  • If renditions exist for JSON files created before this configuration change, remove them manually.

  • Add both exclusion conditions separately:

    • jcr:content/metadata/dc:format!=application/json
    • jcr:content/jcr:mimeType!=application/json
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f