Detecting original asset updates in Adobe Experience Manager Assets
Learn how to detect updates to the original asset file in Adobe Experience Manager (AEM) Assets for auditing purposes when the DamEvent.Type.ORIGINAL_UPDATED event is not emitted by the default event handler. In AEM Assets, you might need to audit when the original asset file (primary resource) is updated, such as when someone uploads a new version. Although the DamEvent.Type.ORIGINAL_UPDATED value exists in the legacy DAM Java API, the default AEM Assets event producer does not emit this specific event. Instead, updates to the original asset appear as standard asset update events. If you filter for DamEvent.Type.ORIGINAL_UPDATED, you will not get results, so you need to inspect the payload to distinguish primary resource changes from other asset updates.
Description description
Environment
Adobe Experience Manager (AEM) as a Cloud Service (all versions)
Issue/Symptoms
- You filter for
DamEvent.Type.ORIGINAL_UPDATEDin your event handler, but you don’t receive any events when you update the original asset file. - Your auditing solution relies on this event type and doesn’t capture original file updates.
Cause
The DamEvent.Type.ORIGINAL_UPDATED value is present in the legacy DAM Java API, but the default AEM Assets event producer doesn’t emit it. Original asset updates appear as standard asset update events instead.
Resolution resolution
Follow these steps to resolve the issue.
-
Configure your event listener to subscribe to AEM Assets update events using AEM Eventing or Adobe I/O Events.
-
In a non-production environment, run a controlled test:
a. Upload a new version of an existing asset using your standard authoring process (such as Assets view, Touch UI, or OpenAPI).
b. Capture the complete event payload generated by the update event.
-
Inspect the event payload to:
- Identify the affected asset (such as the asset path or ID).
- Confirm that the update applies to the primary resource (original file).
- Check for version information, binary identifiers, or other details relevant to your audit requirements.
-
If the event payload contains sufficient information, implement your audit logic based on these details.
-
If you don’t receive the event, or the payload doesn’t provide enough information to distinguish a primary resource update, review your event listener configuration and confirm you’re subscribing to the correct event types.
-
Repeat the test as needed to validate that your auditing requirements are met.