Who is this article for?

Administrators using the search feature.

Administrator access is required.

To help you better manage your documentation, you have access to flexible document management features, including the ability to set expiration dates and automatically reset them upon revision.

When a document has a fixed expiration date (e.g., 15 November) and the Reset Expiration with Every Revision is enabled, the document would prioritize the last published date or expiration verification date depending on the type of edit. This ensures that document expiration aligns with the most recent revision, maintaining compliance and accuracy.

This article explains how the system handles this in different editing scenarios.

1. Understanding behaviour

The behaviour depends on the document's status and the type of edit made (manual or expiration triggered). Below are the key scenarios to illustrate the behaviour.

1.1. Document - Published

Manual edit

Expiration date is updated to last published date + expiration interval.

If the document was manually edited and published on 1 June, and the expiration interval is 1 year, the new expiration date becomes 1 June of the following year.

Expiration edit

Expiration date is updated to expiration verification date + expiration interval.

If the document was verified for expiration on 15 July, and the interval is 1 year, the new expiration date becomes 15 July of the following year.

1.2. Document - In Edit

Manual edit

Expiration date is not updated until the next publish. On publish, it's updated to the last published date and expiration interval.

If the document is manually put into edit and published on 10 August, the expiration date becomes 10 August + interval.

Expiration edit

Similar to manual edit in edit mode, expiration date is not updated until publish. On publish, it's updated to the last published date and expiration interval.