Suite or standalone
Calendar is sold on its own and as part of the Capable Suite. The features are the same in both; several behaviours around them are not. Here is what changes, so you know what to expect from the one you have.
#What differs
Standalone app | In the suite | |
|---|---|---|
Macro names | Usually adds the word macro, for example "Calendar macro (Capable)" | "Calendar (Capable)" |
The Calendar page | A space page and a global page, both titled "Capable Calendar" | One entry titled "Calendar" inside the shared "Capable" page |
Site settings | Confluence settings → Capable Calendar | Confluence settings → Capable |
Indexing tab | Not shown. Indexing still runs; there is just no tab for it. | Confluence settings → Capable → Indexing, where an administrator can run or check indexing |
Hiding Calendar site-wide | No Capabilities tab, although the byline still respects the setting | Confluence settings → Capable → Capabilities |
The Calendar byline | Does not wait for indexing | On Auto, shows only on pages Capable has already indexed as having dates, or in a space set to Always |
Saved calendar content | Stored as "Capable Custom Content (Calendar)" and "Capable Shared Storage (Calendar)" | The same names, ending in "(Suite)" |
Other Capable features | Most connections to other Capable features are not there | Available wherever the other feature is installed too |
#A few things worth knowing
Macro names usually differ: the standalone app tends to add the word macro.
Content is not shared between the standalone app and the suite, so moving across is a migration.
Anything described as working with another Capable feature needs that feature installed too.
#Related
Same features. Different neighbours.
