Capable Formatting for Confluence
Capable recognises 1 macro from Macros for Confluence (Capable). 1 of them convert, and none are left behind.
#At a glance
Macro | Becomes | Support |
|---|---|---|
Standalone → Suite: 20 macro rows | The same macro in the Capable Suite | Converted |
#What each one does
#Standalone → Suite: 20 macro rows
Migrates to | The same macro in the Capable Suite |
|---|---|
Support | Converted |
For customers moving from the standalone Capable Macros app into the Capable Suite. Each is its own row, all fully supported. Nothing about the macro changes except which app it belongs to, every setting is preserved exactly.
What survives the move
Every macro setting, verbatim
Worth knowing before you run it.
Only visible inside the suite app.
Standalone Tab and Tabs macros have no suite migration row, even though the code for one exists.
Detection relies on a fixed list of known app builds, so a macro deployed under an unrecognised build will not be found.
#Related
Native beats a macro, where native will do.
