---
title: "K15t Scroll Versions app"
canonical: "https://support.appfire.com/space/CDML/650153358/K15t%20Scroll%20Versions%20app"
format: markdown
---
> Macro (aura-html)


## Overview

This page describes how to install **Scroll Versions app** with Comala Document Management.

![image](media://f606a686-0f6a-4bc4-b27d-c54487f6d16a)

You need the following apps:

- [Comala Document Management](https://marketplace.atlassian.com/apps/142/comala-document-management?hosting=datacenter&tab=overview) (min v7.0.2)
- [Scroll Versions for Confluence](https://marketplace.atlassian.com/apps/1210818/scroll-versions-for-confluence?hosting=datacenter&tab=overview) (min v4.7.7)
- [Comala Document Management for Scroll Versions](https://marketplace.atlassian.com/apps/1216055/comala-document-mgmt-for-scroll-versions?hosting=server&tab=overview) (latest free version)

In particular, the **K15t Scroll Versions** and **Comala Document Management for Scroll Versions** apps must be compatible versions. Each version release notes of **Comala Document Management for Scroll Versions **in the Atlassian Marketplace lists the compatible versions of K15t Scroll Versions.

> ℹ️ The integration with K15t Scroll Versions only works if the Comala Document Management workflow is applied in [space mode](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649531846). This integration does not work when the workflow is added and applied to an individual page in [page mode](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649628831).

## Benefits

Integrate Scroll Versions with Comala Document Management to let you create the workflows you need, even in spaces with multiple versions and variants.

Scroll Versions and Comala Document Management are both class-leading flagship products. Now, you can combine them in your spaces for ultimate control over version and workflow management.

- Comala Document Management lets you define customized workflows to create, review, approve, and publish your content.
- Scroll Versions is the engine that powers great documentation. It takes management, authoring, and publishing in Confluence to new levels of ease and flexibility. Scroll Versions adds functionality for version and variant management, permalinks (including duplicate page titles), enhanced content reuse, support for context-sensitive help, and much more.

> ⚠️ The following Comala Document Management [trigger](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649563178) action macros are not compatible with the Scroll Versions app. 
> ⚠️ 
> ⚠️ - [approve-children](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649531735)
> ⚠️ - [set-state](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649727251)
> ⚠️ 
> ⚠️ These macros do not work for content that uses the Scroll Versions app and has an applied workflow that uses the macro in a workflow trigger:

## Step 1: Activate Scroll Versions

Scroll Versions must be [activated in your space](https://help.k15t.com/scroll-versions/latest/get-started-114105147.html).

## Step 2: Ensure pages are versioned

Make sure all pages you want to be managed by Scroll Versions and Comala Document Management are set as versioned – this is necessary because unversioned pages don’t have a workflow state.

Convert pages to versioned by opening them and clicking **Versions > Convert to versioned page**:

![image](media://9e8dd009-068b-42a5-bcb8-343ccf8131d7)

If you have just activated Scroll Versions, all pages in the space are **unversioned** until you convert them yourself or edit them for the first time

## Step 3: Implement the Workflow

If you don't have a workflow, you need to [create one](https://appfire.atlassian.net/wiki/spaces/CDML/pages/648611901) or edit one of the workflows bundled with the Comala Document Management app.

> ℹ️ The integration requires that the workflow used in your space is a **space scope** workflow (a workflow editable in the space document management dashboard). The K15t Scroll Versions integration will not work if you use a **global scope** workflow (a workflow only editable in the global workflows dashboard) applied in your space.

## Step 4: Update the final state in your workflow

Create or customize your workflow – at space level:

- [Document Management - Space Tools](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649827041)

Update the [state macro](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649531575) in your workflow, which has the `final=true` parameter, and **rename that parameter** to `versioncompleted=true`. This parameter is specific to the Scroll Versions integration.

An example is shown below:

![image](media://ab515e17-dfe9-4c86-8f2d-93fc5100736a)

It is crucial to remove the `final=true` parameter when using the `versioncompleted=true` parameter.

In workflow builder, checking the **Version completed** option automatically unchecks the **Final** state attribute.

![workflowbuilder_editstate_versioncompleted_checked.png](media://46c88aa2-e294-43dd-942b-3cbe0e41e587)

## Step 5: Enable the workflow

Your workflow must be used in [space mode](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649531846) and, additionally, **must be the only workflow active in that space**. If you have any other workflows listed on the [Document Management Dashboard](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649827041), remove them before activating the new workflow.

## Step 6: Update Scroll Versions settings

Once the workflow is activated, you can complete the integration by going to **Space tools > Scroll Add-ons > Additional Settings**, and selecting **Advanced Workflow**.

The Comala Document Management and Scroll Versions apps are now integrated in your space.

## What happens to my pages after the integration?

If you **integrated Scroll Versions into an existing Workflows space**, all versioned pages in your space will be merged with their already existing Workflows state. Depending on the size of your space this can take a while.

> 📝 Unversioned pages cannot have a workflow in spaces managed with Scroll Versions

If you **integrated Comala Document Management into an existing Scroll Versions space**, each versioned page in your space is assigned the Workflow's initial state. Alternatively, you can use [Initialize States](https://appfire.atlassian.net/wiki/spaces/CDML/pages/649827807) to force all content to a different state.

If you **integrated Comala Document Management into an existing Scroll Versions space where the built-in workflow engine is activated**, the pages' states are converted from the Simple Workflow state into the Workflows state as follows:

| Scroll Versions Simple Workflow | Comala Document Management |
| --- | --- |
| Draft, Review | Initial state |
| Complete | State marked as `versioncompleted=true` |

## See also

External link

![image](media://f9fb137f-74c9-4c9c-9839-97598821aae6)

- [K15t Scroll Versions - Atlassian Marketplace](https://marketplace.atlassian.com/apps/1210818/scroll-versions-for-confluence?hosting=datacenter&tab=overview)
- [Compatibility with Comala workflows - K15t product documentation](https://help.k15t.com/scroll-versions/4.7/compatibility-with-comala-document-management)