Available App Migration Path
Migration Focus Area
Min migratable Version : 8.25.0
|Migrate to Scaffolding cloud using steps at Migration Path|
|License||Available through both Atlassian Marketplace and ServiceRocket Marketplace.||Available through Atlassian Marketplace only. Monthly subscriptions are the default option, however, discounted annual subscriptions are available upon request to our Atlassian Sales team.|
|Access/Security||Authentication Type||Authentication will be based on your current setup||Confluence Cloud protects your data with encryption in transit and at rest and provides administrative controls to enforce organization-wide protection such as SAML SSO, enforced 2FA, and SCIM. (Click the link to understand how Atlassian helps with security and encryption angles in Confluence Cloud)|
Calling Field macros
Field macros are called directly on a page.
Field macros are called after calling Field Group macro on a page. You build the structure of the page inside this macro by choosing the Field macros from the left side panel and drop down to the Editing area
Filling up the forms
|Clicking "Edit Content" will pop-up a separate Scaffolding Edit Content editor. |
Depending on the Scaffolding field macro type, editing values can be done on this directly, or on a separate popup editor area.
Clicking "Edit Content" will change the Page View to become an editable area.
Scaffolding includes an administrator setting, which allows Confluence administrators to set the default setting for the Edit Contents mode.
All limit settings are handled by the app internally. No further configuration needed in Cloud.
Previous Scaffolding XML versions
Scaffolding allows users with the proper permissions to view Scaffolding data history on a page that contains Scaffolding metadata. Users may compare versions or restore older versions using this feature.
All changes made to pages with Scaffolding macros will be recorded in Page History, be it Scaffolding structure or data changes. Users are able to restore page data to an earlier version through the Confluence Page History.
Due to the feature difference between Server and Cloud, only the current version of Scaffolding data will be migrated to Cloud.
|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.
Example of how Scaffolding macros are nested with other macros...
Scaffolding supports integration with most reporting macros/apps like Page Property Report macros (Native Confluence macros) and Reporting (ServiceRocket app)
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 does not support nested macro (See CONFCLOUD-68323) which means integration with other apps by way of nesting will be limited
Due to this limitation, pages and templates that contains Scaffolding macros nested with other macros (such as the one highlighted in the Server column on the left side) will fail to be migrated to Cloud. We suggest cleaning up the page structure and removing any complex 3rd party macros in the page/template before performing the migration to Cloud. Feel free to contact our support team to get further advice about this.
Currently, Scaffolding Cloud does not support integration with reporting apps such as Page Property Report macros.
Availability of Reporting for Confluence Cloud....
We're rebuilding the app for Cloud with better experience and functionality. Sign up through survey if you wish to participate in Beta releases.
Macro Differences Overview
Cloud Macros ( Naming conventions have been changed to suit new macro behavior)
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
|Supported Server Macro|
Cloud Macro (Or closest equivalent )
Creates a set of list options linking to the attachments on the specified content. Must be contained inside a List Data macro.
Accepts content, include and exclude as filter criteria for the attachments
Accepts page location: The location of the page to search the attachment on
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.
Accepts space, parent ancestor, labels etc as filter criteria for the content to be displayed as option.
Accepts space as filter criteria for the content to be displayed as option.
Allows editing of dates with a date picker pop-up menu, or via keying in directly into the fixed format field.
Accepts minDate, maxDate & Display format as Date field criteria.
Accepts no parameter
Allows data to be grouped within a named data set.
Acts as a bucket of Field macros to be easily referred to later. Field name is required.
Acts as the main macro to do Structure editing. Field group name is required.
Allows selection of one or more options from a specific list.
Available as a combination of
Unsupported server scenarios upon migrations
Generates a single, simple, list option.
Must be contained inside a List Data macro.
Accepts custom Texts (that may contain emoji) or Statuses as value and output of the dropdown list.
Live Templates use either Confluence Global templates, Space templates or even other regular Confluence pages as templates.
Unsupported server scenarios upon migrations
Find Limitations at Limitation for Live Template in Confluence Cloud
Click here to expand for more details...
Confluence server supports the Live template macro with various Template types.
However, the Live template macro in Cloud supports different types of template types. Therefore migration of Live Template may be limited
This document highlights the limitations and differences.
CauseDue to differences of the macros and limitations in Cloud, Live Template macros in Cloud can only accept some of the template types used in Live Template macros in Server.
Allows editing of numbers in either a text box or a list item.
Accepts decimal, minValue, maxValue, format display, etc as filter criteria for the number value.
Does not have further criteria for the number value.
Allows dynamic addition or deletion of rows in a table.
Accepts initialRows and order as parameters for the Table data.
Does not take any further parameters
Unsupported server scenarios upon migrations Nesting Table Data
Allows editing of free text data.
|Short Text, Paragraph|
Text input is divided into Short Text and Paragraph. Paragraph macro accepts rich text while Short Text accepts the shorter length of texts
Unsupported server scenarios upon migrations Text Data
Creates a set of list options linking to users matching the filter options. Must be contained inside a List Data macro.
Accepts groups, spaces, users etc , to scope the list of users as options
Accepts user groups to scope the list of users as options