Issue Summary

When migrating Confluence Connect marketplace apps to Forge, defining an adfExport function for dynamic macros enables Word export but overrides the high-fidelity PDF export, resulting in degraded PDF output. There is currently no way to specify different exporters for Word and PDF in Forge macros, unlike Connect macros.

Steps to Reproduce

1. Create a Forge Confluence macro with rich content (graphics, icons, specialized fonts).
2. Deploy the macro without adfExport defined in the manifest.
   1. Result: Macro renders correctly online and in PDF export, but Word export fails with “We don’t have a way to export this macro.”
3. Add an adfExport function to the manifest to enable Word export.
   1. Result: Word export now works, but PDF export uses the limited output of adfExport instead of the high-fidelity

Expected Results

• PDF export should continue to use the high-fidelity online rendering (as it does when adfExport is not defined).
• Word export should use the output from adfExport.
• It should be possible to specify different exporters for different output types, as is possible in Connect macros.

Actual Results

• When adfExport is not defined:
  • PDF export works as expected (matches online view).
  • Word export fails.
• When adfExport is defined:
  • Word export works.
  • PDF export is degraded and uses the limited output from adfExport instead of the online view.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available