We propose the implementation of a new features in Adobe Experience Manager (AEM) that allows users to create custom report templates for asset management. These templates can be saved and scheduled to run at user-defined intervals, such as monthly. The primary purpose of this feature is to facilitate the generation of reports that scan for assets scheduled to expire within a specified timeframe and defined meta data parameters.
Key Features:
Custom Report Template Creation:
Users can create and save custom report templates and use again.
Templates can include custom metadata fields configured by the user.
Scheduling:
Users can define a schedule for the report to run automatically, such as daily, weekly, or monthly.
Email Delivery:
Users can register one or more email addresses to receive the generated report.
The report can be sent as a PDF attachment or as a link to a dashboard in AEM.
Interactive Reports:
The report includes thumbnails of the assets.
Users can interact with the report by clicking on links that direct them to the respective assets in AEM.
This can be implemented as an interactive dashboard within AEM or as clickable links in a PDF report.
Use Case Example:
A marketing team schedules a monthly report that identifies assets due to expire within the next specific parameters. The report includes thumbnails and key metadata fields such as asset name, expiration date, and usage rights. The report is sent via email to the team, and they can quickly review the assets and click on links to access them directly in AEM for further action.
Current/Experienced Behavior:
Not able to save templated reports and can only schedule once or execute now. Report need to be reconfigured each time used. Report not interactive. If exported from system thumbnails of images are lost.
Improved/Expected Behavior:
Create recurring report that has thumbnails of images and has live links to the assets in AEM.
Environment Details (AEM version/service pack, any other specifics if applicable):
This has been reported to the engineering under the internal reference ASSETS-41887. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira status.
