This article only outlines the differences between the Confluence Server/Data Center version of the app and the Confluence Cloud version of the app. Therefore, anything else not listed on this page can be considered as working as expected for the app on any Confluence deployment type (ie. Server, Data Center, or Cloud).
Overview
Learn about the differences between the Server/Data Center and Cloud versions of Scroll Word Exporter.
Features
Scroll Macros
When installing Scroll Word Exporter on Confluence Server/Data Center, the Scroll macros come bundled automatically and will be available after the installation. This differs to Confluence Cloud, where, to gain access to the Scroll Macros you would need to separately install the free Scroll Exporter Extensions app (after installing the macros will become available after a few minutes).
Please note, if you have content nested within Scroll macros, that is also then nested within other macros (ie. Confluence’s own or 3rd-party), this content will not be properly editable in your Cloud instance after the migration, and Confluence will display a notification on the migrated page. This is because Confluence cloud does not support the nesting of macros within other macros, whereas Confluence Data Center does. This means you would either need to re-add/ alter this content on your affected cloud page(s) post migration, or you’d need to make changes on your Data Center content before migrating. Atlassian has an open issue for reintroducing the functionality for nesting macros within macros which you can track here - https://jira.atlassian.com/browse/CONFCLOUD-68323
Legend: 
|
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 Word Exporter 4.0.0 and older, you may have used Scroll app specific macros on your Confluence pages (eg. Scroll-Office-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. However, since the release of Scroll Word Exporter 5.1 (and later) we have implemented a migration tool that users can run on their server/DC Confluence instance to turn the Scroll App specific macros into a cloud compatible version. Learn more about how to use this tool here. |
Template Placeholders
|
Placeholder |
Description |
Server / Data Center |
Cloud |
Details |
|---|---|---|---|---|
|
$scroll.globallogo |
The global logo of the Confluence system. |
|
|
Not available on Confluence Cloud |
|
$scroll.globallogo.(<height>,<width>) |
The global logo of the Confluence system. |
|
|
Not available on Confluence Cloud |
|
$scroll.space.group |
The group of the current space. |
|
|
Not available on Confluence Cloud |
|
$scroll.metadata.(<key>) |
This placeholder can be used to access metadata defined on the root page of your export. This placeholder depends on the Confluence Metadata App as a prerequisite. |
|
N/A |
Not Available → Comala Metadata is not available on Confluence Cloud |
|
$adhocState |
The state of the export root page taken from Comala Document Management. Possible values: 'DRAFT', 'PUBLISHED' or |
|
|
Related feature request: Comala Document Management for Scroll Exporter on Cloud |
|
$scroll.versions.* |
Refers to any of our Scroll content management placeholders. These are available with Scroll Versions or Scroll Translations apps. |
|
|
Scroll Versions and Scroll Translations are not available for Confluence Cloud. However, we have alternatives for these apps on Confluence cloud, please see here for more information. |
|
$scroll.custom.* |
Refers to any of our custom placeholders - for instance for Comala Document Management or Communardo Metadata |
|
|
If you are interested in implementing custom placeholders on Confluence Cloud please let us know via help@k15t.com. |
Administrative Features
|
Feature |
Description |
Server / Data Center |
Cloud |
Details |
|---|---|---|---|---|
|
Option to restrict the export option |
Choose which spaces and/or user groups have the option to export content with Scroll Word Exporter. |
|
|
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 Word 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. |
|
Show/hide the native Confluence Word export option |
Show or hide Confluence's built-in Word exporter in the page tools (•••) |
|
N/A |
Not Available → This is not possible on Cloud due to technical limitations of the Cloud platform. |
|
Audit Logging |
Use the Audit log section to view specific logged events with the exporter app. |
|
N/A |
Not Available → Confluence Cloud does not offer an audit log section |
Export Method
|
Feature |
|
Server / Data Center |
Cloud |
Details |
|---|---|---|---|---|
|
Export to Word via Java API |
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 |
|---|---|---|---|---|
|
Export using Comala Document Management integration |
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. |
|
|
Related feature request: Comala Document Management for Scroll Exporter on Cloud |