Feature differences between Scaffolding Data Center and Scaffolding Cloud
Overview
In Confluence Data Center, there were not many restrictions on how macros could be used together. In Confluence Cloud, a macro with a body can’t be nested inside another macro.
This limitation affects the Scaffolding macros, so some work differently, and some are not available in the new Cloud editor.
Before migrating your Confluence Data Center spaces with Scaffolding data to the cloud, it is important to understand the feature differences and anticipate what is not migratable.
On this page: |
---|
Feature Differences
Migration Focus Area | Feature | Platform |
|
---|---|---|---|
Data Center | Cloud | ||
Versioning/License | Version support | Migration of Scaffolding data is supported for Scaffolding 8.25.0 and later. In Scaffolding 8.30.0 and 9.1.0, we introduce partial support for Repeating Data macro migration. | Migrate to the Scaffolding cloud using the steps at Migration Path. |
License | Available through Atlassian Marketplace | Available through Atlassian Marketplace. Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team. | |
Access/Security | Authentication type | Authentication is based on your current setup. | This describes how Atlassian helps with security and encryption in Confluence Cloud. |
Confluence Differences
| Structure editing
| Input field macros are called directly on a page. Some macros interact with each other and have to be nested inside other macros. | Input fields are drag-and-dropped after adding a Field Group macro on a page. You build the structure of the page inside this macro by choosing the input fields from the left-hand panel and drag-and-dropping them into the editing area. |
Content editing
| Clicking Edit Content opens a separate Scaffolding content editor. Depending on the Scaffolding field macro type, editing values can be done directly in this area or in a separate popup editor area. | Clicking Edit Content changes the Page View to become an editable area.
| |
Scaffolding settings | Scaffolding includes an administrator setting, which allows Confluence administrators to set the default setting for the Edit Contents mode. For details, see Accessing Scaffolding's Administrator Settings | All limit settings are preconfigured. No further configuration is needed in the cloud. | |
Previous Scaffolding XML versions | Scaffolding allows users with the proper permissions to view Scaffolding data history on a page that contains Scaffolding metadata. | All changes to pages with Scaffolding macros are recorded in the Page History, including Scaffolding structure changes and data changes. Users are able to restore page data to an earlier version through the Confluence Page History. | |
Integration with other macros | Since Field macros are called directly on a page as macros, this means that users can add any other Confluence macros inside this page along Scaffolding macros. Confluence server supports nested macros as well which means Scaffolding macros can easily be nested and integrated with other Confluence macros.
Scaffolding supports integration with most reporting macros/apps, including
| Field Group macro is a standalone macro that reveals a separate editor where you can build your page structure. While this editor supports most Confluence page functions, it does not support other complex macros and third-party macros Confluence Cloud currently does not support nested macros (See CONFCLOUD-68323), which means integration with other apps via nesting is limited. Currently, Scaffolding Cloud does not support integration with reporting apps such as page property report macro. | |
Macro Differences Overview | Data Center Macros | Cloud Macros | |
We have simplified our cloud Scaffolding application to focus on some key macros. This means that data migrated will be handled totally differently in Cloud. Review and understand the following:
|
| ||
Macro Differences Breakdown | |||
Data Center Macro | Cloud Macro (or closest equivalent) | Key Differences | |
Data Center | Cloud | ||
Allows users to specify an attachment to upload or select a previously uploaded attachment. |
|
| |
Creates a list of options linked to the attachments on the specified content. Must be contained inside a List Data macro.
|
|
| |
Generates a set of options linking to Confluence content (e.g. pages, blog posts, etc). May be filtered in several ways. Must be contained inside a List Data macro. |
|
| |
Allows editing of dates with a date picker pop-up menu, or via keying in directly into the fixed format field. |
|
|
|
Allows data to be grouped within a named data set. |
|
| |
Repeating Data |
|
|
|
Creates a list of labels to attach to the current page. Must be contained inside a List Data macro. |
|
You can add labels which are currently being used in the Confluence instance by selecting them from the dropdown list. You can also add new labels to the list by typing or pasting them in. | |
Allows selection of one or more options from a specific list. Must contain option-generating sub-macros, for example List Option, Content Options, User Options, Attachment Options or Label Options. | Available as a combination of |
|
|
Generates a single, simple, list option. Must be contained inside a List Data macro. |
|
| |
Live Templates use either Confluence Global templates, Space templates or even other regular Confluence pages as templates. |
|
Find Limitations at Limitation for Live Template in Confluence Cloud | |
Allows editing of numbers in either a text box or a list item. |
|
| |
Allows the dynamic addition and deletion of repeating sections. |
|
| |
Allows dynamic addition or deletion of rows in a table. |
|
| |
Allows editing of free text data. |
|
| |
Creates a set of list options linking to users matching the filter options. Must be contained inside a List Data macro. |
|
|