Release notes 7.10.1

Open

Release date: Jun 10, 2025

Our team is thrilled to announce the latest release of Comala Document Management Data Center.

Confluence Data Center compatibility: v8.5.10 - 9.5.1

The “watchers” value now also includes users watching the space where the page is located. As a result, email notifications will be sent to both page watchers and space watchers.

Previously, migrating Document Activity data required manually running tasks on the server/DC side before running the migration. With this update, the migration of document activity data is now supported as part of CCMA, with no manual steps or scripting needed.

A new column, "Translated Workflow Size Over the Limit," has been added to the Workflow Usage Report to indicate whether the translated version of a workflow exceeds the size limit (32kb). Workflows that exceed this limit cause migration failures, and this enhancement will help identify and address potential migration issues in advance.

The following issues are fixed in this release:

• Fixed an issue where the Workflow Usage Report was incorrectly retrieving other content types as pages within a space. The report now accurately retrieves only valid pages.

• Fixed an issue where invalid workflows caused report generation to fail. Workflows that fail to render are now excluded from the report, and an error log is created.

• Resolved an issue where user links appeared to be broken when the page activity macro was used within email notifications.

• Fixed an issue where workflow details for system workflows could not be viewed for single-page workflows. The workflow details now correctly display information for page workflows.

• Resolved an issue where Document Activity timestamps did not account for the user’s summer schedule settings. Both Page History and Document Activity now display consistent times.

• Migration failure due to invalid state conditions in Triggers: Fixed a migration issue caused by the translation of triggers containing state conditions with values referencing states that do not exist in the workflow. These invalid values broke the workflow during migration, which is now resolved.

• Resolved an issue where usernames in space-level workflow parameters were not correctly translated during migration. The parameter now includes the mapped cloud user corresponding to the original DC (Data Center) username.

• Fixed an issue where lists of users defined in workflow parameters were not properly mapped during migration.