How Site Collection Inactivity is Calculated by Governance Automation
Search and filter
KB Article ID: 12113
| Product: | Governance Automation,Governance Automation Online |
| Product Version: | All |
| SharePoint Version: | 2013,Office 365 |
Details:
With AvePoint Governance Automation, you can manage site collection lifecycles by enabling a site collection inactivity threshold in the site collection policy. If activity in the site collection has ceased for the configured time threshold, Governance Automation will start an approval process. The purpose of the approval task is to alert the assignee to the inactivity, and to optionally provide them with tools to manage the site collection lifecycle. This leads to a fundamental question: how do we calculate site collection inactivity?
For Governance Automation Server, an on-premises solution, site collection inactivity is calculated based on two conditions: 1. the configured inactivity threshold in the site collection policy, and 2. the value of the LastContentModifiedDate property in the SharePoint Server API. This property is updated when a change is made to the database for that site collection, including the addition of view audit records. This can be interpreted as a Last Accessed Time for that site collection, and thus inactivity is based on site collection access of any kind.
However, the LastContentModifiedDate property used for on-premises calculation is not available in the SharePoint Online API. So for Governance Automation Online, a hosted solution in the AvePoint Online Services platform, and for SharePoint Online site collections managed by Governance Automation Server, site collection inactivity is calculated based on: 1. the configured inactivity threshold in the site collection policy, and 2. the value of the LastItemModifiedDate property in the SharePoint Online API. This property is updated when content is modified in the site collection, not including the addition of audit records to the database. This calculation can be interpreted as a Last Modified Time for the site collection, and thus the distinction between on-premises and Online site collection inactivity is that for Online, inactivity is based on actions taken on content in the site collection rather than access to the site collection.