Issue in passing URI to Web Content Field

RE: Issue in passing URI to Web Content Field

rachelg9844 — Tue, 28 Feb 2023 05:19:23 GMT

URL parameters (known also as “query strings” or “URL query parameters”) are elements inserted in your URLs to help you filter and organize content or track information on your website.

To identify a URL parameter, refer to the portion of the URL that comes after a question mark (?). URL parameters are made of a key and a value, separated by an equal sign (=). Multiple parameters are each then separated by an ampersand (&).

Regards,

Rachel Gomez

RE: Issue in passing URI to Web Content Field

jefferyo7735 — Sun, 26 Feb 2023 14:07:16 GMT

You need to pass a Safe URI to the source parameter of the webContentField component, and that URI is generated using a web API. The problem here is that when I use the URI generated from the web API, it throws an error. I found a detailed explanation and solution for this issue on XtraSaaS, a platform that covers technical topics like this in depth

RE: Issue in passing URI to Web Content Field

harryc5316 — Wed, 20 Jul 2022 08:25:12 GMT

This is not supported by the evidence. Appian takes waffle game proactive measures to prevent usage cases like this one due to security concerns. Because of a change that occurred a few years ago, we had no choice but to discover this the hard way.

RE: Issue in passing URI to Web Content Field

Stefan Helzle — Mon, 04 Jul 2022 12:46:13 GMT

That would require a component plugin.

docs.appian.com/.../component-plugins.html

RE: Issue in passing URI to Web Content Field

TJ — Mon, 04 Jul 2022 12:39:54 GMT

Hi Peter,

I am trying to execute certain piece of html code that is part of script tag inside body. Through that I am trying to embed chat functionality developed by other system on Appian screen.

RE: Issue in passing URI to Web Content Field

Peter Lewis — Fri, 01 Jul 2022 16:37:09 GMT

Like Stefan said, this is not supported. Can you provide more context on what you're trying to do though? There might be other possible solutions that don't involve pointing to a Web API.

RE: Issue in passing URI to Web Content Field

Stefan Helzle — Fri, 01 Jul 2022 12:49:31 GMT

This is not supported. Appian actively prevents this use case because of security reasons. We had to learn this the hard way as this has changed a few years ago.