Initiate retention time period on content Based on Metadata / Attributes Upon Upload (Migration) to Box
For example, when content is uploaded to Box, applying a 7 year retention policy to content, but basing it off the last modified or created date. In this scenario, the 7 year policy would apply to the content, but it would not live for 7 years in Box - it would like for 7 years from the last modified/created date.
AdminChristopher Drubka
(Admin, Box)
shared this idea
-
AdminPauline C.
(Product Manager, Box)
commented
There is now the ability to leverage custom metadata date field as the start date for retention. The date can be in the future or in the past.
-
AdminModerator
(@ Box, Box)
commented
Event-based retention is important for my company.
-
AdminJacques van der Merwe
(Admin, Box)
commented
There is a variation of this theme which in other system governance system is called a base date. It means that the retention policy is calculate from a base date + retention. This base date can creation date, modified date, last accessed date or metadata date. This play a very important role when migrating system that has current retention in place to Box, because it allows for the transfer from one system to another e.g. the retention date needs to start from a date that the ERP system sets. Once set the retention policy will be activated for 3 years. If we now migrate a document into Box and apply the same 3 year policy, but there is only 18 months left, then it will continue as usual. At the moment to achieve the same effect, I have to create multiple policies with various lengths to accommodate the same behaviour.