This article outlines the differences between the Confluence Server/Data Center version and the Confluence Cloud version of Scroll HTML Exporter.
If a specific feature is not listed on this page, you can expect it’s working as expected for the app on any Confluence deployment type (ie. Server, Data Center, or Cloud).
Feature Comparison
The reasons that drive the differences between the Server and Cloud versions of Scroll HTML Exporter can be grouped into three categories:
-
Differences between the cloud and the on-premise Confluence architectures
-
Compatibility with 3rd party marketplace apps
-
Deprecation of Confluence features between Data Center and Cloud versions
Ensure that you are familiar with the differences before you plan your Migration Path.
Scroll Macros
The Data Center variant of Scroll HTML Exporter comes with Scroll macros included so the macros are available immediately after you install the app.
In the Confluence Cloud version of HTML Exporter, the Scroll macros are available through the free Scroll Exporter Extensions app that you can install from the Atlassian Marketplace. After installing, the macros will become functional within a few minutes.
Confluence Cloud offers only a limited support for nesting of macros. As a result, if your Scroll macro content is nested inside another macro (Confluence native or 3rd party), the nested content will not be properly editable in the Cloud environment. To mitigate the impact of this limitation on your content, you have two options:
-
Post-migration - manually add or alter the content in the Cloud pages.
-
Pre-migration - re-factor the content in the familiar Data Center editor as a part of your pre-migration cleanup.
For more details, see Atlassian’s open issue for reintroducing the nesting macros functionality - https://jira.atlassian.com/browse/CONFCLOUD-68323.
Legend: – Available |
– Unavailable |
– Partially available
|
Macro |
Description |
Server / Data Center |
Cloud |
Details |
|---|---|---|---|---|
|
Scroll Pagetitle |
Makes Scroll overwrite the page title on export. |
|
|
On Cloud, this macro is not available. Instead, use the Scroll Page Title dialog by going to the Page tools menu (•••) > Set Scroll Page Title.
|
|
Scroll app specific macros |
For users of Scroll HTML Exporter 3.5.1 and older, you may have used Scroll app specific macros on your Confluence pages (eg. Scroll-HTML-Ignore). Since EXP-32 we have made changes to these macros so they are not app-specific. |
|
|
On Cloud, these macros will not be made available. You can read more about how to manually change these legacy macros to a cloud compatible format here.
|
Template Customization
|
Feature |
Description |
Server / Data Center |
Cloud |
Details |
|---|---|---|---|---|
|
Template Theme Customization |
Create custom export templates that allow modifications to the export look and feel. |
|
|
Due to the differences in templating between Scroll HTML Exporter for Confluence Server/DC and Cloud, we provide a hard-coded template theme on cloud.
However, on Cloud, templating is far less sophisticated and the possibilities for customization are reduced and specific template settings and export properties can be defined (learn more). Furthermore, we provide a custom template customization option on app and you can read more about how to make post-export customization changes here. |
|
Template Placeholders |
Possibility to add template placeholders in custom export templates to reference metadata in the generated export. |
|
|
Due to Scroll HTML Exporter for Cloud providing a hard-coded template, we do not yet support the addition of template placeholders which are available on Server/DC. |
Administrative features
|
Feature |
Description |
Server / Data Center |
Cloud |
Details |
|---|---|---|---|---|
|
Choose which spaces and/or user groups have the option to export content with Scroll HTML Exporter. |
|
|
Not currently available for the cloud version of the app. Related feature request: Restrict the export functionality for Confluence Cloud Exporters |
|
|
Restrict the number of pages that can be exported in a single export |
Limit the number of pages that can be exported by Scroll HTML Exporter |
|
N/A |
Not Applicable → This feature is not available on Confluence Cloud as it is only applicable for on-premise Confluence (self-hosted) deployments to influence memory consumption and export generation. |
|
Use the Audit log section to view specific logged events with the exporter app. |
|
N/A |
Not Available → This feature is not yet available on Confluence Cloud Related feature request: Introduce export statistics / report for performed exports |
Export Method
|
Feature |
|
Server / Data Center |
Cloud |
Details |
|---|---|---|---|---|
|
Perform exports in your custom Java app using our public Scroll Exporter Java API |
|
|
Due to the technical setup of apps on Confluence Cloud a Java API is not available (since Cloud apps are not running on the same Confluence instance any more). Users should use the REST API instead. |
Integrations
Export options
|
Feature |
|
Server / Data Center |
Cloud |
Details |
|---|---|---|---|---|
|
Integrate with Comala Document Management to only export content that has been approved through every step of a Comala Workflow, and has been published to the final workflow state. |
|
|
Not currently available for the cloud version of the app. Related feature request: Comala Document Management for Scroll Exporter on Cloud |