---
title: "Why are Comala Document Management 7+ releases different?"
canonical: "https://support.appfire.com/space/CDML/650314954/Why%20are%20Comala%20Document%20Management%207%2B%20releases%20different%3F"
format: markdown
---
> Macro (aura-html)


## Comala Document Management 7.0+ for Data Center

> Macro (excerpt)
> 
> Comala Document Management and **Page Activity** are key capabilities for many of our customers, especially those that rely on page activity for regulatory or compliance needs.
> 
> **Comala Document Management v7.0** **Data** **Center **introduces a new capability - **Document Activity**.
> 
> Document activity provides
> 
> - **enhanced performance and stability** when loading document activity with large numbers of states and approvals, mitigating the risk of data loss due to size limits
> - a new **[Document Activity Report](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649891440)** with improved layout, sorting, and filtering, including the flexibility to add advanced filters
> - [Document Activity APIs](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649791485) to drive your own business insight from the document lifecycle by connecting to your organization's business tools for tailored reporting

> ℹ️ **Document Activity **is a step change in the way the app stores workflow events, such as state changes and approvals, and provides a powerful new API to enable your teams to get business insights from their document lifecycle.

> 📝 This is a significant change from the key capability of **Page Activity** and requires an upgrade of existing data.

## Get ready

After installing Comala Document Management 7

- **New spaces** automatically utilize document activity to record and report workflow events and actions
- **Existing spaces without an applied workflow** (no previous workflow events or actions) will automatically utilize document activity on the application of a workflow

However, to take advantage of the new capabilities of Comala Document Management 7 in the data center, you need to **upgrade your existing workflow activity data** to a new data format. 

> ℹ️ The data upgrade requires your Confluence Administrator to enable Confluence **Read Only Mode** in the data center while it runs.

## Pre-upgrade data check

> ℹ️ A [pre-upgrade data checks capability](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649760247) is available in Comala Document Management [6.17](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649825498)+ releases and in Comala Document Management 7.

 The pre-upgrade data check enables you to:

- Validate that existing page activity data can be upgraded
- Estimate the upgrade process duration for each space
- Identify any upgrade errors for specific pages in each space

> 📝 Pre-upgrade data checks can be run separately without the need to enable **Read-Only Mode**. This means that pre-upgrade data checks can be undertaken in a server instance prior to moving to data center.

[Comala Document Management 6.17](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649825498)+ for server and data center provides the ability to run

- **pre-upgrade data checks** on a space-by-space basis so that you can validate your existing activity and get upgrade duration estimates (this ***does not*** require Read Only Mode)

**Comala Document Management 7.0** for data center provides the ability to run

- **pre-upgrade checks and upgrades** on a space-by-space basis, allowing you to prioritize and schedule each space upgrade

> ✅ Both the pre-upgrade checks and the upgrade can be executed on a space-by-space basis to minimize the impact on your end-users

## Related pages

> Macro (contentbylabel)