Linking macros in cloud have the following limitations:

• Does not support nested macros, which means Linking macros cannot be placed in a nested container (such as inside an expand macro, etc)
• Due to the above, other macro integration is difficult.
• Currently, Linking macro cannot be used with Scaffolding macro
  • Tracked as a feature request at https://ideas.atlassian.servicerocket.com/ideas/LINK-I-120
  • Current status as at May 2021: Likely To Implement

Supported macro parameters

• Name
• Link Text
• Source
• Source Type
• Prefix
• Postfix
• Parent
• Labels

Supported macro parameters

• Link Text
• Button Text
• Field hint
• Source
• Source Type
• Prefix
• Postfix
• Parent
• Labels

Supported macro parameters

• Spaces
• Bullet Style
• Display Excerpts

Supported macro parameters

Supported macro parameters

Supported macro parameters

• Match Using
• Users
• User Groups

Deck of Cards and Cards

• In Server, Tabbed content is available by calling the Cards macro nested inside Deck of Cards. 
• Content of each tab will be added inside each Card macro

Tabs, Tab Group and Tab

• Confluence Cloud has two different editors (see Legacy editor vs New editor for more information)
• Composition Tabs have a different set of macros for each type of editors:

  • Macros available for Legacy Editor: Tab and Tab Group

    • Tab & Tab Group macros can be added into the legacy editor by calling the Tab macros nested inside Tab Group. 

    • Content of each tab will be added inside each Tabs macro

        Take note of the incompatible macros when nested within Composition Cloud's Tab and Tab Group macros..

      Summary

      Many Confluence macros do not work properly when nested within a Tab or Tab Group macro.

      

       This KB is for the Tab Group / Tab macors. If you're looking for compatible macros within the newer Tabs Macro, refer to the Tabs documentation (with an 's').

      Environment

      • Confluence Cloud

      Cause

      Due to limitations with Confluence Cloud's live editor, nested macros no longer work as before. What this means for Composition is that many macros do not function as intended when nested within either a Tab or Tab Group macro.

      Resolution

      A solution is forthcoming.

      In the meantime, the following is a list of compatible and incompatible macros:

      	Macro	Compatible?	Notes
      	Macro	Compatible?	Notes
      1	Activity Stream Macro
      2	Anchor Macro
      3	Attachments Macro		Drag and drop does not work Unable to expand the attachment info
      4	Blog Posts Macro		No UI error, but unable to create blog post
      5	Change-History Macro
      6	Chart Macro
      7	Cheese Macro
      8	Children Display Macro
      9	Code Block Macro		The text inside code-block macro is not displayed
      10	Column Macro
      11	Content by Label Macro
      12	Content by User Macro
      13	Content Report Table Macro
      14	Contributors Macro
      15	Contributors Summary Macro
      16	Create from Template Macro		Infinite spin on the button
      17	Create Space Button Macro		The link will lead to 404
      18	Excerpt Include Macro
      19	Excerpt Macro
      20	Expand Macro
      21	Favorite Pages Macro
      22	Gallery Macro
      23	Global Reports Macro
      24	iFrame Macro		Will lead to 404
      25	IM Presence Macro		Unconfirmed
      26	Include Page Macro
      27	Info, Tip, Note, and Warning Macros
      28	Jira Chart Macro
      29	Jira Issues Macro		Single issue will display accordingly JIRA Filter will not resulted in an error
      30	JUnit Report Macro
      31	Labels List Macro
      32	Livesearch Macro
      33	Loremipsum Macro
      34	Multimedia Macro
      35	Navigation Map Macro
      36	Network Macro
      37	Noformat Macro		The text is not displayed
      38	Office Excel Macro
      39	Office PowerPoint Macro
      40	Office Word Macro
      41	Page Index Macro
      42	Page Properties Macro
      43	Page Properties Report Macro
      44	Page Tree Macro
      45	Page Tree Search Macro
      46	Panel Macro
      47	PDF Macro
      48	Popular Labels Macro
      49	Profile Picture Macro
      50	Recently Updated Dashboard Macro
      51	Recently Updated Macro
      52	Recently Used Labels Macro
      53	Related Labels Macro
      54	Roadmap Planner Macro
      55	Search Results Macro
      56	Section Macro
      57	Space Attachments Macro
      58	Space Details Macro		The Space Icon is missing Edit link does not work
      59	Spaces List Macro		Tabs lead to 404
      60	Status Macro
      61	Table of Contents Macro
      62	Table of Content Zone Macro
      63	Task Report Macro		Cannot click to complete task
      64	User List Macro
      65	User Profile Macro
      66	Widget Connector Macro

      
      

      
      

      
      

  • Macros available for New Editor: Tabs

    • Tabs macro can be added into New Editor by calling the Tabs macro, which will call a Tabs editor. Content is added inside this editor

      

  • New editing experience in Confluence Cloud does not support Nested Bodied macros (CONFCLOUD-68323)
  • Tab Group and Tab macros that utilize nested macros mechanism will not work properly in New Editor.

Field macros are called directly on a page.
Some macros interact with each other and have to be nested inside other macros

Field macros are called 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 down to the Editing area

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. 

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 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 currently 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 contain 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 simplifying the page structure and removing any complex third 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. 

• Define output to be a dropdown list. Requires other Field macros to work
• Dropdown settings are defined here such as Required, Allow multiple, Separator, etc.

• All dropdown macros are called individually depending on their function
• Allow Multiple and Required setting are set in each individual macros

 Unsupported server scenarios upon migrations.

• List data that contains multiple types of options.
  

• In Cloud, the type of options is its own separate macros and therefore cannot be combined. 

• If this scenario happens, only the topmost option will be migrated. In this example, only User Options will be migrated to Cloud.

Live Template 

Live Templates use either Confluence Global templates, Space templates or even other regular Confluence pages as templates.

• Accepts Page, Space or Global Templates, and any Confluence Blueprint as templates

• Location of Page/Template/Blueprint is chosen from a dropdown field. Space name and Page name field are separated

   Unsupported server scenarios upon migrations.

Find Limitations at Limitation for Live Template in Confluence Cloud

  Click here to expand for more details...

Summary

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.

Environment

• Confluence Cloud

• Scaffolding Forms and Templates for Confluence Cloud

Cause

Due 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.

Resolution

Template Type	Server	Cloud	Notes about Server - Cloud migration
Page			Can be migrated automatically
Space Template			Can be migrated automatically
Global Template			Due to CCMA limitations, Server Global template can't be automatically migrated to Cloud. All Global Template have to be copied to Space template manually before the migration. Read more about the steps here.
Confluence Blueprint
Scaffolding Blueprint			Scaffolding Blueprint is not supported in Cloud and will not be migrated to Cloud

Accepts initialRows and order as parameters for the Table data.

Does not take any further parameters

 Unsupported server scenarios upon migrations.

• Nesting Table data does not work in Cloud. 
  • In server the following table appears as a nested table 
    
    

  • Confluence Cloud does not support nested macro related functions.

  • If this scenario happens, the data inside the table will not be migrated. I.e Agenda, Notes, Status, and Actions column will not be migrated.

• Accepts area, line, or password as Type, and richtext, text, etc as the content type
• Accepts language, minLength, maxLength, etc as parameters for the Text data

Text input is divided into Short Text and Paragraph. Paragraph macro accepts rich text while Short Text accepts the shorter length of texts

• Text data: Accepts Placeholder to help users input their data
• Paragraph: Does not take any further parameter
• Migrating Text data with type Area will be migrated as Paragraph while type Line and Password will be migrated as Text Data

 Unsupported server scenarios upon migrations.

• Text data with type Password will be migrated as Short Text macro and will not have masked view on page view

• Rich Text content is only partially accepted

  • Find limitations at Limitations of Rich Text content of Text Data Macro (Server) migration to Paragraph Macro (Cloud)

      Please click to find more complete details

    Summary

    Confluence server supports the Text Data macro which converts to Confluence cloud Short Text, Paragraph. However the Paragraph macro in cloud's support of rich text migrating from server is limited. This document highlights the limitations.

    Environment

    All Confluence versions that can support CCMA(Confluence Cloud Migration Assistant)

    Cause

    Due to differences of the macros and limitation in Cloud, Paragraph macro (Text data equivalent in the Cloud) can only accept some of the rich text content features.

    Resolution

    Paragraph

    • Look out for icons highlighting limitation of the rich text data migration if any at table below.
      
      •  - Available

      •  – Unavailable

      •  – Partially available

    Feature	Available
    Fonts Normal text Heading 1, 2, 3, 4, 5, 6 Bold, italic, underline Strikethrough Code Superscript, subscript
    Text alignment
    Text colour
    Lists Bullet Numbered
    Action item
    Link
    Files & images	SCAF-I-126 GATHERING INTEREST
    Mention
    Emoji	Partially Available: Bit emoji  Confluence specific emoji
    Expand
    Table
    Layouts
    Quote
    Code snippet
    Panel Info Note Success Warning Error
    Decision
    Divider
    Date
    Status

    
    

    
    

    
    

You will need to set up the connection to the Salesforce site on the Confluence side. You will need to provide Salesforce URL, login, and password directly in this menu.

• Only allow one connection to a single Salesforce site.
• This app supports SSO.

You will set up the connection on Confluence, but Confluence will redirect you to the Salesforce login page for authorization.

• Allows more than one connection to multiple Salesforce sites.
• SSO will be managed by Confluence Cloud. Read more about this here.

Confluence Cloud does not support nested macros, which means integration with other apps by way of nesting will be limited.

Currently, Salesforce Connector Cloud does not support integration with reporting apps such as Page Property Report macros. 

• Salesforce Account 
• Salesforce Contact 

Depending on the Salesforce object, Confluence users will choose between Salesforce Account or Salesforce Contact macro to add to the page. 

• Object macro

Confluence users can add any type of Salesforce Object (e.g. Salesforce Account, Contact, Opportunities, etc.) into a page, as long as they know the Object URL using the Object macro.

• Salesforce Entity 

Use Salesforce Entity to displays a list of Salesforce entities in a table format

• Table macro

Use Table macro to display a list of Salesforce entities in a table format

• A Salesforce Search function is available to help you craft a SOQL to be added in this Table macro.

Macros are created by calling the Secure macro on a confluence page

Macros are created by calling the Secret macro on a confluence page

Approved access users need to re-enter their Confluence password to decrypt

Approved access users can click "decrypt" button to immediately access the secured content

An access log of each macro

After decrypting the macro, approved access users can also view the access log

Centralized view of all secrets on a space

As a space administrator, you can see what secrets are stored in the space, the last time they were updated and which pages do they belong to.

Centralized audit log of all macros on a space

As a space administrator, you can use the audit logs to run audit reports, review access to secrets, find out any unintended access, detect suspicious activities and provide supporting evidence of your organization's security compliance.

This table signifies the difference between Server/Data Center app and the Cloud version. While the function of server macros is available in Cloud, they are not directly migratable.