AEMaaCS: DAM Asset Change Notifications to 3rd party via AEM Eventing + Runtime Action | Community
Skip to main content
S
samr99530769
Level 3
May 7, 2026
Question

AEMaaCS: DAM Asset Change Notifications to 3rd party via AEM Eventing + Runtime Action

  • May 7, 2026
  • 1 reply
  • 25 views

We are building a solution in AEMaaCS to notify 3rd party system whenever a DAM asset is created, updated, or deleted — covering all asset types including images, documents, Content Fragments, and videos.

Our approach uses AEM Eventing (Adobe I/O Events) with an Adobe I/O Runtime Action as the processor, which then forwards the event payload to 3rd party log monitoring system.

One key question before we finalize the design:

Will DAM asset events fire consistently from both the new Assets View console and the Classic Admin View (/assets.html)? Since both UIs share the same underlying DAM repository, we expect events to trigger regardless of which console is used — but would appreciate a confirmation.

Any inputs from the community are welcome!

https://experienceleague.adobe.com/en/docs/experience-manager-learn/cloud-service/aem-eventing/examples/event-processing-using-runtime-action
https://developer.adobe.com/experience-cloud/experience-manager-apis/api/stable/assets/author/#operation/asset_processing_completed

1 reply

S
Adobe Employee
SubbaraoGa1Adobe Employee
Adobe Employee
May 7, 2026

Hello ​@samr99530769 

Although both Assets View and Admin View access the same DAM content, Adobe documentation does not provide a formal statement that Adobe I/O asset events will fire identically from both UIs for all operations.

For that reason, we would not recommend finalizing the design on that assumption alone. The recommended approach is to validate the required asset lifecycle events from each UI and, where possible, standardize on a single authoring path for predictable event behavior.

Content Fragments should be treated as a separate validation area because you are stored as assets but are documented as a Sites feature.
Reference:

  1. Switch views in AEM Assets
  2. Content Fragments
  3. Working with Content Fragments

We recommend validating at minimum: upload/create, metadata edit, binary replace, move/rename, delete, and restore, across each UI your authors will use.

 

 

Terms & ConditionsAccessibility statement

Loading footer...