Skip to main content
Skip table of contents

Conditional Content Macros after Migration

Conditional content macros in Scroll Versions enable you to control the visibility of content based on specific conditions. This article explains how Conditional Content macros are migrated to Scroll Documents and Variants for Scroll Documents. We will also discuss the important differences between the two macros.

Scroll Documents and its extension apps

Translations for Scroll Documents and Variants for Scroll Documents, are extension apps to Scroll Documents. The extensions offer enhanced language and variant management features. It is recommended to use both apps together with Scroll Documents for a complete experience. To learn more see: How Do Extension Apps Work?

Transformation and Limitations

When you migrate to Scroll Documents, your Conditional Content macros are transformed into Scroll Conditional Content macros.

It's important to note that Scroll Documents and Variants for Scroll Documents do not support inline macros. This means that any inline conditional content macro you migrate, as well as any new Scroll Conditional Content macros you create, will be transformed/created as blocks. As a result, the content within each Scroll Conditional Content macro will be displayed on a new line.

We have plans to enhance the display of conditional content by adding highlights to the macros. For more information, refer to: DOCS-170

To learn more about managing variants and conditional content with Scroll Documents on Confluence Cloud see:

If You Migrate with Inline Conditional Content

During the migration process, Scroll Versions provides you with the option “Preserve inline Conditional content macros.”

You only need to select this option if you have inline conditional content macros on the same line as other text content.

If checked, the conversion tool will detect the paragraph around one or multiple inline conditional content macros and make the whole paragraph conditional, with different inline content in each of them. This results in equivalent output when publishing or exporting the content, the page view of the content might look less clear. Below are some examples of conditional content macros migrated with and without the option to preserve inline conditional content.

Conditional content before migration:

The following sentence contains two inline condition content macros

Conditional content after migration:

Editor view after migration without preserving inline conditional content (left) and with preserving conditional content (right)

If you have multiple variants, you'll see the migrated macros stacked on top of each other in Confluence page view. However, when using Scroll Viewport, the Document Reader, or exporting with Scroll Exporters, only the content from the selected variant will be visible.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.