Issues calling local server content with a!webContentField()

RE: Issues calling local server content with a!webContentField()

adithyay — Thu, 20 Feb 2020 17:25:35 GMT

Hello Kumara53,

a webcontentfield will only allow https URL's.

RE: Issues calling local server content with a!webContentField()

kumara0002 — Thu, 20 Feb 2020 15:00:00 GMT

Hi All,

I have a similar issue, trying to embed http://xx.xx.xxx.xx into appian's iframe using a!webcontentfield() but it is not loading, though the url is accessible over internet.

Appreciate suggestions and workarounds!

Thanks in advance!

RE: Issues calling local server content with a!webContentField()

brettr — Fri, 20 Apr 2018 17:03:53 GMT

Wonderful, thank you Rob!

I am utilizing the billboardLayout for some of my dashboards where I do want that "top banner". I am actually trying to embed a widget from another service that shows up to date, external data to show off some of the new Appian functionality.

RE: Issues calling local server content with a!webContentField()

Robert Shankin — Fri, 20 Apr 2018 16:54:35 GMT

Hi Brett -

I passed the feedback along.
When you're feeling strongly about unexpected behavior, a support ticket is your best avenue for communicating that to the product team.
Also, I know this isn't exactly the same thing, but have you considered the use of a billboard layout for your banners?

Thanks,
Rob

RE: Issues calling local server content with a!webContentField()

brettr — Fri, 20 Apr 2018 16:16:40 GMT

Rob,

Thank you for the clarification. Preview Mode is a new concept to me, so I will definitely keep that in mind moving forward. Is there a more appropriate avenue to offer feedback for these components? I would love to offer any more thoughts/concerns I come across while using this component. I actually have one in mind already, specifically around size control. I am trying to implement a small widget to act almost as a banner above a section, and there is a lot of white space below it, even when setting the height to "SHORT".

And for anyone stumbling on this post in the future, I have an idea on how to get around only allowing external content. I have not implemented this, but was going to if time permitted or I had issues using Amazon's public name. Create a new subdomain and add a corresponding virtual host to Apache. Configure the local directory in that host, and link to that from the Appian installation. I am not 100% sure this would work, but if it does I believe it could be a good workaround.

RE: Issues calling local server content with a!webContentField()

Robert Shankin — Fri, 20 Apr 2018 16:09:23 GMT

Hi brettr

Advance apologies, this isn't a great answer -
the docs do specify that the Web Content Field displays content from "an external source".
So, your speculation about Appian thinking that it's pulling it's own content might be close to what's going on.
When a feature (like this one) is offered in preview mode, we can expect that it's only going to get better in future releases.

Keep this feedback coming, and this product team should take notice.
Thanks,

Rob