Having the code block below in your manifest enables your macro to be included in the pdf or word file when your confluence page is exported.
modules: macro: - key: xxx-xxxx-xxx resource: main resolver: function: resolver title: Macro description: xxxxxxx export: function: xxxxx-export function: - key: xxxxx-export handler: export.run app: id: ari:cloud:ecosystem::app/xxxxxx-xxxx-xxxx-xxxx-xxxx
The main limitation here is that the export function provided can only be UI kit.
Now, this works okay for macros built using the UI kit. But, it becomes difficult for the export function to support sophisticated macros built using Custom UI, simply because UI kit components are limited and cannot be extended (please correct me if I am wrong here).
Luckily, UI kit provides an image component. So, an image representation of your macro can be generated and stored “somewhere” passing the image URL in the image component
Also, you can create a base64 image representation of your macro and then pass the string in the image component
However, the first approach is complex and can leave some security risks as images with sensitive data are stored externally. With the second approach, you run into the risk of " request entity too large" error when the image base64 string representation is too large.
So, I would like to ask the following questions to the Forge team:
- Are there currently other ways to export macros with complex UIs built using Custom UI?
- How do you plan to support macros with complex UI that are built with Custom UI?
- Is there any timeline for this?
All comments are welcomed.