Web Page Widget

< appboard | 2.6 | builder | widgets

Page Contents

1. Overview

The AppBoard Web Page Widget provides a way to include HTML content into an AppBoard dashboard. The URL for the widget can be configured with the widget and/or set via action which allows for user interaction to drive the content shown.

With the Web Page Widget you are able to:

  • Include content from an external source by specifying an external URL. Please note that not all websites behave well in this context hence the functionality provided by enPortal.
  • Include enPortal proxied content, providing the full capabilities of enPortal such as single sign-on (SSO), and the Content Retrieval System (CRS).
  • Include web pages or content served up by the AppBoard server itself. These could be static pages or CGI scripts.

This page covers using and configuring the Web Page Widget. For more information on updating the content via action refer to the Launch URL Action page.

Other than managing the URL, interaction between the Web Page Widget and AppBoard is limited. To develop a more integrated experience allowing AppBoard and the Widget to communicate then refer to the HTML Widget.

When using the Web Page Widget be aware that accessing some websites or web applications may not work. This is due to the way these sites are expecting to interact with the browser, as the top-level window, and not in a frame. The typical symptoms are either a blank widget, or the site will take over the top-level window replacing AppBoard.

If content from sites incompatible with frames is required then enPortal can be used to handle this by proxying the site along with custom rules to deal with the issues when running in a frame.

2. Creating Web Widgets

For instructions on creating a Widget, see the general instructions in Adding Widgets. The Web Page Widget type is located under the Web category on the Widget selection screen.

3. Widget Home Control

Web Widget Home control

In both the Builder and Viewer any Web Widgets feature a Home icon in the widget title bar. This forces the content displayed to revert to either:

  1. the last configured URL via action
  2. (if above doesn't apply) the widget configured URL

When interacting with a Web Widget the user may navigate away from the original content and this feature just provides an easy way to get back.

4. Examples

4.1. Simple External Source

This example configures a simple external URL:

  1. Follow the instructions above to create the basic "Web Page" Widget.
  2. Enter the following information on the Visualization tab:
  3. Click Close or Next -> Finish to save the changes.

4.2. Including enPortal Proxied Content

enPortal can provide from simple proxying of web content, so that a client retrieves the proxied data from the AppBoard server rather than directly, or more complex integrations using Product Integration Modules (PIMs).

The pre-requisites for including enPortal proxied content are:

  1. The Channel must exist, refer to the enPortal documentation on Content Creation
  2. The Channel should be provisioned to the roles of the end-users that will end up having access to the AppBoard Board where the Web Widget will be placed. Refer to the enPortal documentation on Content Provisioning.
  3. Obtain the enPortal URL needed for the Web Widget. The best way to get this is to:
    1. in enPortal go to: Provisioning -> Content Management
    2. find the desired Channel and select it
    3. use the View button to launch a pop-up browser window.
    4. copy the URL from this pop-up (excluding the http://server:port part)

Putting it together:

  1. Configure enPortal content as outlined above. In this example we created a folder called "Example" with a channel "Edge" that's a simple proxy channel of the Edge website.
  2. Follow the instructions above to create the basic "Web Page" Widget.
  3. Enter the following information on the Visualization tab (obtained from Viewing the channel):
    • URL: /enportal/servlet/pd/vdir/deployment/Menu/Example/Edge
  4. Click Close or Next -> Finish to save the changes.
  5. Using the mouse, hovering over any links in the proxied content (depending on your browser) will show these links referencing the AppBoard server rather than the Edge website directly.
Web Widget with enPortal proxied content.

In the portalAdministrator role this content will always be visible. However, if logged in as a regular user and the enPortal content has not been provisioned to the user's role then they will see a Portal Exception error message.

Some enPortal Channels can take URL parameters. These can be explicitly set in the URL, or using tokens if using the Launch URL action.

4.3. Embedding a Twitter Timeline

This example is a case of including a HTML page served up by the AppBoard server. The content of the HTML page is just a bare bones HTML document with the embedded code provided by Twitter using the User timeline widget (see https://twitter.com/settings/widgets - requires a Twitter account).

This approach would be similar for many other services that offer embeddable content.

Web Widget using local HTML page with embedded Twitter content.
  1. Use Twitter Widgets (link above) to create the widget
  2. Create a basic HTML page on the AppBoard server and include the code provided by Twitter. For example this could be stored: [INSTALL_HOME]/server/webapps/enportal/custom/edge_twitter.html
  3. Now in the AppBoard Builder create a new Web Page widget and use the following URL: /enportal/custom/edge_twitter.html
  4. Click Close or Next -> Finish to save the changes.