Issue Summary

Currently the exported view (the result of `adfExport`) is rendered for Forge macros and migrated Forge macros when they're nested inside a bodied dynamic content Connect macro.

This ticket is to cover the support of shallow (one level) nesting of a Forge inside a Connect macro so it's rendered as if it was placed on page's top level.

Supported parents:

• Dynamic content bodied Connect macro.

Supported children:

• Non-bodied pure Forge UI Kit macro.
• Non-bodied pure Forge Custom UI macro.
• Non-bodied migrated (stored as <ac:structured-macro>) Forge UI Kit macro.
• Non-bodied migrated (stored as <ac:structured-macro>) Forge Custom UI macro.

Static content Connect macros will still render adfExport result for nested Forge macros.

Steps to Reproduce

1. Create a page.
2. Add a bodied dynamic content Connect macro to the page.
3. Add a Forge macro into the Connect macro body.
4. Publish the page.

Expected Results

Forge macro is rendered inside a Connect macro as if it was placed on the page

Actual Results

Depending on the Forge macro type and configuration, various outcomes are possible:

• If `adfExport` is present in the app manifest – the rendered adfExport result is displayed.
• If `adfExport` is not present in the app manifest:
  • If it's a pure Forge macro – display "We don't have a way to export this macro".
  • If it's a migrated Forge macro – display the macro title placeholder.

Workaround

Currently there is no known workaround for this behavior.