Adobe Experience Manager (AEM) Assets users perform many actions like creating, uploading and deleting Assets. These actions can be recorded so you are able to provide an history of what has been done by a user. This section describes the recording capabilities of AEM and how to configure AEM in order to record specific events.
This integration could be CPU and disk space consuming for example when doing bulk import. For these reasons the AEM Assets integration with the Activity Stream is disabled by default.
The following events can be configured to be recorded:
- License accepted (ACCEPTED)
- Asset created (ASSET_CREATED)
- Asset moved (ASSET_MOVED)
- Asset removed (ASSET_REMOVED)
- License rejected (REJECTED)
- Asset downloaded (DOWNLOADED)
- Asset versioned (VERSIONED)
- Asset version restored (RESTORED)
- Asset Metadata updated (METADATA_UPDATED)
- Asset published to external system (PUBLISHED_EXTERNAL)
- Asset's original updated (ORIGINAL_UPDATED)
- Asset Rendition updated (RENDITION_UPDATED)
- Asset Rendition removed (RENDITION_REMOVED)
- Sub-asset updated (SUBASSET_UPDATED)
- Sub-asset removed (SUBASSET_REMOVED)
The Web console provides access to the AEM Assets Event Recorder tuning. To configure the AEM Assets Event Recorder, proceed as follows:
The recorded events are stored as activities. You can read them programmatically by using the ActivityManager API.