You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need an expiration period also for catalogue items after which they will be deleted. Deleting catalogue items also needs to be possible even if they haven't expired yet, but the user is requesting us to do so.
Expiration logic:
REMS users, catalogue items, and applications have separate processes for expiration, but the processes work together.
For example, if a catalogue item is expiring check if there are applications related to it that haven't expired yet and only expire the catalogue item after the application has expired.
Open questions:
What about other rems items that are related to the catalogue item, e.g. forms, resources, workflows? They could be in use in other catalogue items so deleting them might not be possible. -- They don't expire if they are in use in newer catalogue items?
If a catalogue item needs to be removed, but there are still active applications connected to it, what should we do?
We need an expiration period also for catalogue items after which they will be deleted. Deleting catalogue items also needs to be possible even if they haven't expired yet, but the user is requesting us to do so.
Expiration logic:
Open questions:
Related #3015 and #2682
The text was updated successfully, but these errors were encountered: