SubAssetExpiry blocks move operation for editors and librarians.
Hi dear community!
I am looking at something that just been brought to my attention.
We all know that an asset that is expired by prism:ExpirationDate will lose some of its functions (as it should).
The asset will no longer be downloadable, it gets depublished, AssetLink will not longer find the asset etc. pp.
All good stuff.
BUT now the same behavior comes up with InDesign Files that simply contain an expired asset.
isSubassetIsExpired seems to trigger the same behavior - at least regarding the "move" functionality.
*Edit: Even Download is blocked ;(
This behavior will make an librarian out of our administrators... they will move a lot of files.
Imagine a single picture that renders 500 InDesign files as SubAssetExpired.
Does anybody know what acls are responsible for this behavior / if it is possible to grant rights to "move"?
