Scaffolding Forms and Templates Feature Differences
Overview
This document explains the feature differences between scaffolding forms and templates.
On this page: |
---|
Migration Path
Original Platform | Target Platform | Available App Migration Path | License Migration | Notes/Consideration |
---|---|---|---|---|
Server/DC | Cloud | Needed |
This guide assumes you have successfully migrated your Confluence Server data into Confluence Cloud, per Atlassian's instructions (CCMA) More Atlassian resources are available here. |
Feature Differences
Migration Focus Area | Feature | Platform | |
---|---|---|---|
Server | Cloud | ||
Versioning/License | Version Support | Min version 8.25.0 for migration | Migrate to Scaffolding cloud using steps at Migration Path |
License | Available through Atlassian 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 | This describes how Atlassian helps with security and encryption in Confluence Cloud. |
Confluence Differences | Structure editing
| Field macros are called directly on a page. | Field macros 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 Field macros from the left-hand panel and drag-and-dropping them into the Editing area. |
Content editing
| 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 settings | 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 is 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. | 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. | |
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.
| 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 macro (See CONFCLOUD-68323) which means integration with other apps by way of nesting will be limited. Currently, Scaffolding Cloud does not support integration with reporting apps such as page property report macro. | |
Macro Differences Overview | Server 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 | |||
Supported Server Macro | Cloud Macro (or closest equivalent) | Key Differences | |
Server | Cloud | ||
Allows users to specify an attachment to upload, or to select a previously-uploaded attachment. |
|
| |
Creates a set of list options linking 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. |
|
| |
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 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. |
|
|