Ignore the "not updated for N days" trigger (optionally) if the page is labeled with an explicit expiration or archiving date

Avatar
Aron Gombas
Follow

At the moment, the two triggers are combined with OR, but a user suggests that having a label should completely turn off the other trigger.

Have more questions? Submit a request

6 Comments

Date Votes
  • 1
    Avatar
    Carolin Felden

    It would be great if future archived pages will be excluded from the lifecycle job. To be exact, if there is a label „archive on date xxx“, the lifecycle job should ignore the „expire after N days“ trigger. 

  • 0
    Avatar
    Linda Dorn

    This feature is very important for us, as we regularly use the "archive on date xx" label e.g. for team meeting minutes as we want to keep some of them but not all of them.

  • 0
    Avatar
    Linda Dorn

    Hi guys,

    any news on this? This is really really disturbing our whole archiving process.

     

  • 0
    Avatar
    Aron Gombas

    Linda,

    Just to manage expectations, I wanted to tell that we are not working on this particular one right now, but there will be two other important app features (also requested by you) released in the few next months.

  • 0
    Avatar
    Linda Dorn

    Thank you Aron for this update :-) 

  • 1
    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 content status can be configured with a CQL query. The rule of the game is simple: if a content satisfies the CQL search of status X, it will be set to status X.

    To implement this feature request, just set up the "Expired" status with this CQL:
    (arch.expirationDate < now()) 
    or 
    (arch.event.lastUpdatedOn < now("-100d") 
      and 
     not arch.expirationDate > now("-2000y"))
    Using this logic, a content will become "Expired" either if it has an expiration date and the date is passed, or if it has no expiration date set and was not edited for 100 days. The CQL query may look a bit quirky for this reason: as the CQL language does not allow testing if the expiration date is not null, we are testing if it is later than now minus 2000 years. 😊

    🔥 Try this in action now!

    Edited by Aron Gombas
Please sign in to leave a comment.