Reporting if assets are deleted in AEM from the AEM linked folder. | Community
Skip to main content
S
ShannaBo
Level 2
January 29, 2026
Solved

Reporting if assets are deleted in AEM from the AEM linked folder.

  • January 29, 2026
  • 1 reply
  • 35 views

We currently have users uploading their assets to the linked AEM folder in Workfront, which then syncs to AEM/Content Hub. If an error is identified on an asset, it must be manually deleted in AEM and then again in Workfront.

Is there a report available that can identify whether users have deleted an asset from the linked AEM folder? Additionally, do teams typically have a governance process in place for when this occurs?

Best answer by Vishal_Anand

Hi ​@ShannaBo,

Short answer: There’s no single out‑of‑the‑box report that universally flags “user deleted an asset from the linked AEM folder,” but you can reliably detect and report deletions using Workfront audit data, AEM audit/events, or an automated reconciliation process.

Below are concise options:

Option 1: Workfront audit / reports

  • Use Workfront’s System Audit Trail or a Custom Report on the Document object to export events filtered by action = DELETE.
  • Or call Workfront API to list documents and query historical events for delete actions.

Option 2: AEM audit & event listener

  • Check AEM DAM audit logs and asset workflow history.
  • Implement a JCR/Sling EventListener or AssetEventHandler that logs deletion events (user, path, timestamp) to a table/log for reporting.

Option 3: Automated reconciliation (recommended)

  • Build a scheduled job (script/OSGi) that:
    • Queries Workfront folder contents via Workfront API.
    • Queries AEM via Assets API/QueryBuilder for assets mapped to that folder.
    • Compares lists and outputs missing items (deletes) into a report (CSV/DB/dashboard).
  • Run daily or on a cadence that matches sync frequency.

Option 4: Real‑time webhook sync

  • Configure Workfront Event Rules/webhooks for file deletes to call a middleware endpoint.
  • Middleware updates AEM record/state or writes an event to a reporting store. This prevents manual double‑cleanup.

Logging & configs to enable

  • Enable/collect Workfront audit exports or API event logs.
  • Add an AEM event handler + persist entries to a reporting DB or Kafka topic.
  • Ensure service users and API credentials are configured and secured for both systems.

Governance (technical controls commonly used)

  • Implement soft‑delete + lifecycle state in AEM/Content Hub.
  • Push delete actions through an approval workflow (technical gate).
  • Automate reconciliation and alerting for discrepancies.
  • Maintain an audit table and retention policy for deleted asset records.

Feel free to reach out if you have any further queries.

​@kautuk_sahni 

1 reply

Vishal_Anand
Vishal_AnandAccepted solution
Level 5
February 1, 2026

Hi ​@ShannaBo,

Short answer: There’s no single out‑of‑the‑box report that universally flags “user deleted an asset from the linked AEM folder,” but you can reliably detect and report deletions using Workfront audit data, AEM audit/events, or an automated reconciliation process.

Below are concise options:

Option 1: Workfront audit / reports

  • Use Workfront’s System Audit Trail or a Custom Report on the Document object to export events filtered by action = DELETE.
  • Or call Workfront API to list documents and query historical events for delete actions.

Option 2: AEM audit & event listener

  • Check AEM DAM audit logs and asset workflow history.
  • Implement a JCR/Sling EventListener or AssetEventHandler that logs deletion events (user, path, timestamp) to a table/log for reporting.

Option 3: Automated reconciliation (recommended)

  • Build a scheduled job (script/OSGi) that:
    • Queries Workfront folder contents via Workfront API.
    • Queries AEM via Assets API/QueryBuilder for assets mapped to that folder.
    • Compares lists and outputs missing items (deletes) into a report (CSV/DB/dashboard).
  • Run daily or on a cadence that matches sync frequency.

Option 4: Real‑time webhook sync

  • Configure Workfront Event Rules/webhooks for file deletes to call a middleware endpoint.
  • Middleware updates AEM record/state or writes an event to a reporting store. This prevents manual double‑cleanup.

Logging & configs to enable

  • Enable/collect Workfront audit exports or API event logs.
  • Add an AEM event handler + persist entries to a reporting DB or Kafka topic.
  • Ensure service users and API credentials are configured and secured for both systems.

Governance (technical controls commonly used)

  • Implement soft‑delete + lifecycle state in AEM/Content Hub.
  • Push delete actions through an approval workflow (technical gate).
  • Automate reconciliation and alerting for discrepancies.
  • Maintain an audit table and retention policy for deleted asset records.

Feel free to reach out if you have any further queries.

​@kautuk_sahni 

    Terms & ConditionsAccessibility statement

    Loading footer...