-
Type: User story
-
Status: Resolved
-
Priority: Minor
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: BlobManager, Retention
-
Epic Link:
-
Tags:
User story
As a record manager, I want to configure a retention policy with a retention period to start based on a metadata, so that I can use an external and past event to define the expiration date.
Description
The goal is to add another option in the retention starting point part to define the retention period trigger as an external date (example: date of publication of the document, date of approval in a external system, ...)
- Name of the option: "Based on a metadata"
- Behavior:
- The retention period is calculated based on the retention duration and a metadata (date or datetime only)
- Expiration date = date filled in the predefined metadata + retention duration
- The retention period is calculated based on the retention duration and a metadata (date or datetime only)
- Configuration: the metadata is defined based on an expression language
- Limitations:
- The selected metadata must be a date format (or convert in the expression language)
- It can be a past or a future date
User experience
- Retention starting point section
- Retention starting point section when I select "Based on a metadata"
Acceptance criteria
- For a retention policy with 2 years of retention and configured as "Based on a metadata", the expiration date value is the predefined metadata date + 2 years
- For a retention policy with 2 years of retention and configured as "Based on a metadata", when the metadata is not filled or is not correct, the document becomes a record without expiration date (eligible to deletion)
- For a retention policy with 2 years of retention and configure as "Based on a metadata", when the metadata is older that the retention policy period, the document is declared as a record without expiration date
- depends on
-
NXP-28135 Record management - Empty or past date value for metadata based retention
- Resolved