Investigating
Better options for the Expiry search filters.
| 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:
|
| 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): | 2023.8.13323.20230831T134651Z |
| Name des Kunden/der Organisation: | medi GmbH & Co. KG |
| Screenshot (sofern zutreffend): | |
| Code-Paket (sofern zutreffend): |