"Expire on date" and then "auto-archive in N days"

Avatar
Aron Gombas
Follow

This use case is doable the following way: you can apply the "expire-18/1/1" and "archive-18/4/1" labels to have a page expire on 1 January and get archived on 1 April.

This will work, but this requires more attention to use:

  1. Once, the user needs to add two labels manually, making sure that he is using the correct dates.
  2. And, if after 1 January, someone decides that the page is not actually expired, he needs to drop both labels (and maybe add two new labels with the new expiration and the new archiving date).

The process could be made in a smoother way.

Have more questions? Submit a request

2 Comments

Date Votes
  • 0
    Avatar
    Aron Gombas

    UPDATE: We have released the Better Content Archiving app's cloud version just a few weeks ago. It addresses many points criticized in the Data Center version, including also this one.

    (Our plan is that, if there is interest, we will back-port the most valuable changes from the Cloud version to the Data Center one.)

    In the cloud version, each status has a customizable CQL query. If a content matches the CQL filter of status X, then the content is in status X.

    Following that thought, your requirement can be implemented with the "Expired" status using a CQL query like this:

    arch.expirationDate < now() 
    or 
    (arch.expirationDate is empty and arch.event.lastUpdatedOn < now("-365d"))

    It means that either the content has passed its expiration date or it has no expiration date set and hasn't been updated for a year.

    🔥 Try this in action now!

    Edited by Aron Gombas
  • 0
    Avatar
    Patrick Richert

    I'd think the rule would be simple for page expiration, and is really what we need:

    IF page has a Label

    THEN expire on that date

    ELSE expire after x days of no update

     

    Right now it seems to want to apply both the expire date and the expire after x days, which causes problems if someone has a page that needs to stay for 5 years due to contractual agreements, but that page is simply not going to change (as much of our documentation that's customer facing CAN'T change), and there are also pages on there that can be expired on a normal cycle (say 2 years).

    Right now, if the page that needs to stay the same gets older than 2 years, even though it's never going to need updates, and is flagged to expire for 5 years, it will still expire in 2 years when the rule runs.

    If the change above were made, the rule would recognize that the page is labelled, so it would ignore the "expire if the page hasn't been updated in <x> days"

     

Please sign in to leave a comment.