Macro Pack for Confluence (Warsaw Dynamics)

Capable recognises 2 macros from MacroSuite for Confluence (Warsaw Dynamics). 1 of them convert, and 1 are detected and reported without being changed.

A reported-only macro is left exactly as it is on the page. It is counted so you can see how much of it you have, and decide what to do about it, but nothing is rewritten.

#At a glance

#What each one does

#Macro Pack (from text)

The one MacroSuite macro that converts. Depending on what a given Macro Pack instance renders, it becomes the matching Capable macro. Diagram and Markdown content is written into a new asset on the page and the new macro is pointed at it. PlantUML content missing its start and end tags is wrapped automatically, and draw.io content is cleaned of the stray elements that otherwise render a blank canvas.

• Only migrates when the Macro Pack source is pasted text. Instances sourcing from a web address, an attachment or anywhere else are reported unsupported and left untouched.

• If the new asset cannot be created, the macro is reported failed and left unchanged.

#Detected but not converted

These are found and counted so the report is honest about what is on your pages. They stay exactly as they are.

#Other Macros

• Deliberately one row covering all 22 of the older single-purpose MacroSuite macros (Swagger, markdown, HTML, LaTeX, AsciiDoc, PlantUML, Mermaid, JSON, CSV, draw.io, and the inline Macro Pack), rather than 22 rows. Each separate row would have cost its own count query and buried the one Macro Pack row that does migrate.

• MacroSuite Swagger macros are reported here as unmigratable rather than converted.

#Related

Native beats a macro, where native will do.