Zusammenfassung der Funktionsverbesserungsanfrage (RFE):
The expired assets predicate in the search filter currently only has one feature. Asset is already expired. Yet there are much more interesting things related to the expiry, that could be shown. Here are some examples for more interesting search filter regarding the expiry:
Expired: The asset itself is expired (Ignore Dependencies)
Has expired dependencies: The asset contains expired assets (Don't show expired assets, but instead those assets that contain an expired asset)
Will expire: The asset will expire till (dateselect) + usefull quickoptions: within the next 1 week, 1 month, 1year etc.) Be careful using those on sites / print projects that will be used for a longer period of time, since the printed media can't be "unpublished" but have to be destroyed, removed etc.)
Will not expire: Show only assets that are free of an expiry restriction I call it the "care free" option. Assetts can be used without having any fear that they will depublish themself / printed items do not have to be destroyed because one asset is no longer licensed
Anwendungsfall:
A user that wants to produce a print medium has to check if the assets that went into the print medium are not restricted with an expiry date. A cataloge might contain up to 800 assets. The cataloge will be printed with a circulation of 10k pieces. Currently, a user would have to check each individual asset to see whether it expires before the estimated time at which the print copies will be replaced by a newer one. Or a user builds an asset into a site, just to see that the asset depublished itself one week after the site launched because the expiry was overlooked.
Aktuelles/erlebtes Verhalten:
The expiry search predicate is built to make only visible what is already expired (what can not be used). In addition it makes it not easily distinguishable if the expiry flag is set because an asset itself is expired or if it contains a expired asset.
Verbessertes/erwartetes Verhalten:
Add additional functions as written in the RFE. Two checkboxes for expired, one for assets and another for dependencies Checkboxes that look into the future and give the user a option to check if the asset will expire within a range or has an expiry at all.
Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben):
This has been reported to the engineering under the internal reference ASSETS-29252. The product team will triage this request to verify feasibility based on the prioritization model. This post will be updated according to the Jira request status.
Hi @kautuk_sahni , Thank you for the reply! Is there a way the process of this ticket? In case any more questions arise out of my description, i would like to offer the invitation to contact me.
@Adilos-Cantuerk, If there are additional questions from the PM team, they Or I will share them with you at the top of this Thread. Also, this thread will keep you updated with any progress. Otherwise, you can share "ASSETS-29252" with support Or your CSM/TAM to validate the status of this same.
