Zusammenfassung der Funktionsverbesserungsanfrage (RFE):
Better differenciation between Asset-Is-Expired and SubAsset-is-Expired Visual by not having a red flag for both - and for the filter.
Anwendungsfall:
The red flag icon on the thumbnail warns that an Asset is expired. This red flag indicates that a file can not be downloaded. BUT this warning is used by the system for two different occasions.
AssetExpired and SubAssetExpired. An InDesign file might contain an expired picture. Now that InDesign file will be displayed with a red flag. But the InDesign file itself is not expired and can be downloaded. Therefore i suggest that there needs to be a better differenciation. Visualy as well as for the expiry search filter.
Aktuelles/erlebtes Verhalten:
If a picture expires that is built into 1000 documents, the expiry filter now lists 1001 expired assets - even there is only a single expired asset and a 1000 assets in which this picture is a dependency. There is no visual differenciation between an expired InDesign and an InDesign that simply contains an expired asset. Users see the red flag and get the impression that the file can not even be downloaded.
Verbessertes/erwartetes Verhalten:
For the Thumbnails, this can easily be done by having a small change in /libs//dam/gui/coral/components/admin/contentrenderer/card/asset/propertyList.jsp
This already checks between the two states: if ((isContextCollection || properties.contains(VIEW_PN_IS_ASSETEXPIRED)) && (isAssetExpired || isSubAssetExpired)) { %> <coral-card-property class="expirystatus" icon="flag" data-is-asset-expired="<%= isAssetExpired %>" data-is-sub-asset-expired="<%= isSubAssetExpired %>" title="<%= xssAPI.encodeForHTMLAttr(i18n.get("Expired")) %>"></coral-card-property> <% } I changed this for my organisation, but i think it would be a great improvement for everybody OOTB.
Umgebungsdetails (AEM-Version/Service Pack, ggf. weitere Angaben):
This has been reported to the engineering under the internal reference ASSETS-33043. 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.