This is a preview version of the Web Content component. It is not yet supported on mobile devices, or in the following browsers: Internet Explorer 11, Edge, and Safari. On those browsers, this component will display a link to the content instead of the content itself. See Usage Guidance for more information.
Displays content from an external source.
|Label||label||Text||Optional text to display as the field label.|
|Label Position||labelPosition||Text|| Optional text to determine where the label appears. Valid values include
|Instructions||instructions||Text|| Optional text displayed below the
|Help Tooltip||helpTooltip||Text|| Displays a help icon with the specified text as a tooltip. The tooltip displays a maximum of 500 characters. The help icon does not show when the label position is
|Source||source||SafeURI||Location of the external content.|
|Show Border||showBorder||Boolean||Determines whether the field has an outer border. Default: true.|
|Height||height||Text|| Determines the field height. Valid values include
|Alternative Text||altText||Text||Equivalent alternate text provided to assistive technology.|
|Visibility||showWhen||Boolean||Determines whether the component is displayed on the interface. When set to false, the component is hidden and is not evaluated. Default: false.|
altTextis used for the link label.
<title>attribute). When no title is provided, the
altTextvalue is used.
1 2 3 4 5 6 =a!webContentField( source: "https://www.appian.com/", height: "MEDIUM", showBorder: true, altText: "Appian Corporation" )
For the best user experience, use the web content field in Chrome or Firefox. In those browsers, content is embedded per the behavior described on this page. In Edge, Internet Explorer 11, and Safari, the web content field appears as a link to the source. The value provided in
altText is used for the link label.
It's important to consider which browsers are used by your end users and designers. For example, if an interface is designed and tested in Chrome, but deployed to an Internet Explorer 11 user population, the end user experience is different from what was tested. The opposite scenario must also be considered. If an interface is designed in Internet Explorer 11 and deployed to Chrome users, it won't be fully tested the way users will experience it.