Hi @VincentDumas1 , I’m an engineer on Confluence. Thanks for pointing out this limitation, I do indeed see that for exporting via pdf specifically, the macro configuration is not passed into apps’ specified adfExport functions. I’ve gone ahead and made a quick change to include these configuration values, as well as the contentId as part of the function payload–it should be merged and deployed by early next week.
Unfortunately the pending code change does not include the other fields that you’re after (macroId and content version); their exclusion is a limitation of the platform right now. Would you know of any other places where Forge surfaces such data to apps? It could help us to evaluate the effort required to potentially add those fields in the future.