...
Server Concept | Cloud Concept | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
Metadata Set | Fields are no longer declared separately from sets. They can only be defined together. This is now called a Content Category. Content Categories can be assigned only to pages, not blog posts, and only one Content Category can be assigned to a page. | |||||||||
Metadata Field | ||||||||||
Space / Global Metadata Sets | In cloud there are only global Content Categories.
|
...
Functionality in Server | Cloud | Notes | ||||||||
---|---|---|---|---|---|---|---|---|---|---|
Connect a Confluence template to a Metadata set | Unlike the server/dc version of the app, where a Metadata set can be linked to multiple templates, in cloud a Content Category can currently be linked to only one Confluence template. We are currently evaluating if and how we can bring this feature also to cloud! | |||||||||
Display Metadata macro | The cloud app will soon support configuring the Display Macro to show Metadata values of other pages.
| |||||||||
Metadata Overview macro | In cloud it is renamed to : Metadata Report macro. Not all features from server are carried over. More options related to filtering and live filtering for sure are in our roadmap. For more info see:
We are open for your feedback! Please reach out to us if you miss an important feature. | |||||||||
Content by Metadata macro | ||||||||||
History of Metadata values | No history feature, including the History macro, is offered in cloud | |||||||||
Text field | ||||||||||
Multi select field | Due to cloud infrastructure limitations, a limit of 30 options is set for both fields. They also have the same look. No more field types. In cloud there is no differentiation between “Dropdown” and “Radio buttons”. Just There is just the “Single select” which works like the “Dropdown” on server. | |||||||||
Single select field (Dropdown and Radio buttons) | ||||||||||
Link field | Called Page link in cloud. It only supports adding Confluence pages as values. At the moment it is not possible to define a filter for the auto-completion in cloud. | |||||||||
User field | ||||||||||
Date field | ||||||||||
Group field | ||||||||||
Required fields | Currently not available. Will be refined in the future according to our customer requests. | |||||||||
Default values | Currently not available. Will be refined in the future according to our customer requests. | |||||||||
Bulk change |
| In server/DC it is only available for space Metadata. As in cloud there is no such feature, this is not available. | ||||||||
Metadata based CQL filters for Confluence built-in macros | ||||||||||
Comala publishing integration |
...