1. Responsiveness / iframe height (main priority)I have a custom component plugin that loads in an Appian interface. The plugin’s UI is responsive (e.g. adapts to mobile and different breakpoints), but the iframe and field layout do not adapt to the content height.
The JavaScript API reference (e.g. 25.3) only documents how to receive the height parameter via Appian.Component.onNewValue(); I don’t see any documented way for the component to report its content height so the host can resize the iframe (e.g. a setHeight or similar).Questions:
I’m currently using Tall (840px) as a workaround so the iframe has enough space, but I’d like to know if dynamic height is supported or planned.
2. Images: external URLs vs Appian document storageThe same plugin can render images from external URLs (e.g. https://...) without issues, but I cannot display images stored in Appian (e.g. from a Document or related storage).Question:Is there a supported way for a component plugin to show images that come from Appian document storage (e.g. a document ID or a URL that requires Appian auth)? For example, should the interface pass a different kind of URL or token that the plugin can use in an <img src="..."> or similar?
Summary: I’m looking for solutions for both: (1) iframe responsive to content height when Height = Auto, and (2) displaying Appian-stored images in the plugin. My current priority is (1) responsiveness.Thanks in advance for any guidance or documentation links.
Discussion posts and replies are publicly visible
Is this page helpful on how to manage the 'height' input? https://docs.appian.com/suite/help/26.1/how-to-adjust-height.html - I've always adjusted my internal container manually based on what is provided at runtime
Thank you so much for the help! This is exactly what I needed for my project.
I have a follow-up question regarding Image Storage and Component Plugins. I've noticed that while my plugin can render images from external URLs (e.g., https://...) without issues, it fails to display images stored within Appian (using Document IDs or internal paths). I need to be able to publish it on a portal.
https://...