Capable Diagrams for Confluence

Capable recognises 3 macros from Diagrams for Confluence (Capable). 3 of them convert, and none are left behind.


#At a glance

Macro

Becomes

Support

Diagrams (Standalone → Suite)

Capable Diagram (suite)

Converted

Diagram reference (Standalone → Suite)

Capable Diagram Reference (suite)

Converted

Diagram templates (Standalone → Suite)

Capable Diagram templates (suite)

Converted


#What each one does

#Diagrams (Standalone → Suite)

Migrates to

Capable Diagram (suite)

Support

Converted

For customers moving from the standalone Capable Diagrams app into the Capable Suite. Each diagram, its thumbnail and its history are copied into the suite and the macro is repointed at the copy. Re-running is safe: a diagram already migrated is recognised and the existing copy is reused rather than duplicated.

  • Only visible inside the suite app. Standalone-to-suite rows are hidden everywhere else, with no on-screen explanation.

  • Only actually copies content at migration behaviour version 1.2.0.

#Diagram reference (Standalone → Suite)

Migrates to

Capable Diagram Reference (suite)

Support

Converted

  • A second pass, it runs after everything else and needs the diagrams and templates migrated earlier in the same run. Ticking it automatically ticks the templates migrator it depends on.

#Diagram templates (Standalone → Suite)

Migrates to

Capable Diagram templates (suite)

Support

Converted

Copies diagram templates and their folders into the suite. These live in a library rather than on any page, so this row is counted in items rather than pages, does not widen the set of pages the run visits, and executes once at the very end of the run.



Find the drawing first. Everything else follows.