...
The MultiExcerpt function is a two-step process involving two macros, both of which come with purchasing the MultiExcerpt app from the Marketplace:
Create the MultiExcerpt key containing the content you want to leverage by reusing/displaying it in other locations. To know more on how to create MultiExcerptcontent, click here.
The following are the available MultiExcerpt macros:MultiExcerpt Macro
MultiExcerpt Fast Excerpt (Inline)
MultiExcerpt Fast Excerpt (Block)
Inserting the MultiExcerpt Include to reuse/display the excerpted content. To know more on how to reuse MultiExcerpt content, click here.
The following are the available MultiExcerpt Include macros:MultiExcerpt Include
MultiExcerpt Fast Include (Inline)
MultiExcerpt Fast Include (Block)
Difference between MultiExcerpt and MultiExcerptFast
...
Fast forward to today and Atlassian has introduced a new page editor (a.k.a. the fabric page editor). Pages created with the new page editor do NOT block rendering for "static" macro processing. It is not necessary to use the "Fast" (dynamic) versions of the MultiExcerpt macro for new/fabric pages. In fact, it It may be preferable to stick with the "static" MultiExcerpt and MultiExcerpt Include macros for new/fabric pages because the Fast macros have some limitations due to the nature of dynamic macros (rendered in an iFrame).
As an added complexity: there are many behaviours of new/fabric pages that are undesirable and inconsistent with the behaviours of legacy pages. In some cases, you may be forced to use a legacy page in order to get a feature or behaviour that has not been implemented or does not work in the new/fabric pages. When you are forced to use a legacy page you should prefer the "Fast" versions of the macros but beware that they come with some limitations: for example, if you nest a Confluence Table macro inside of a MultiExcerpt then table sorting will not work in the "Fast" version because the iframe containing the content does not have access to the CSS styling of the containing page and Confluence's Table macro depends on the CSS styling of the containing page. In a case like that, you must choose the simpler, but not as performant, "static" macros.
...
Inline | Block |
|---|---|
Inline allows the excerpt to be inserted in line with the content around it. | Block allows the insertion of content into separate blocks. |
Edit mode  View Mode After Saving Page  | Edit mode  View Mode After Saving Page  |
Fallback Permission Handling
The "Fallback permission handling" parameter in the MultiExcerpt macros is used to provide a fallback permission check in some scenarios such as exposing Confluence content in Jira Service Desk (JSD).
...
A system user, a.k.a. "app user", exists for 3rd party apps like the MultiExcerpt app.
When "Fallback permission handling" is enabled for a MultiExcerpt then, ONLY for situations where the user cannot be found, the app user will be used to access the excerpted content when a MultiExcerpt Include macro requests it.
Most of the time you will NOT need to enable this parameter.
An example of a scenario where it could be necessary to enable it is when using a MultiExcerpt Include on a page that is exposed on Jira Service Desk (JSD). Due to Atlassian bugs, users who are not in your basic profile in JSD will be unable to see content that is included via a MultiExcerpt Include.
Limitations
Performance
There is a limit on the number of MultiExcerpt Includes that you can use on a single page with satisfactory rendering times. This is due to a combination of the capabilities of web browsers, Confluence, and the MultiExcerpt Include macro.
...