Edge Documentation

The AppBoard developer should not be expected to build multiple copies of each component (e.g. one for desktop, one for iOS, one for Android, and so on). So one of the core goals of AppBoard is to support the same suite of components across all devices.

However, certain types of Widgets provide displays that are too complex for consumption on a mobile device. In fact, if the user accesses certain standard AppBoard Widgets on a mobile device the device will display the message: "This widget is not supported on this device. Please contact your administrator to configure an alternative compatible widget". To address the specialized requirements of the mobile platform, many AppBoard Widgets provide a special configuration option called "Configure Alternate Widget".

For example, the standard Basic Table Widget is not supported in AppBoard Mobile. To present data from a Basic Table Widget on a mobile device, you can select a single column of the table and display that as a single-column list in AppBoard Mobile.

Although this Option is used primarily for presentation on mobile devices, it can also be used to configure an alternative display to be presented on the desktop.

A green check box on the Data tab in the "Edit Widget" Wizard indicates that the alternate Widget settings have been configured for the current Widget. Once an alternate Widget is configured, there is no way to "un-configure" the alternate Widget

Configuring an Alternate Widget for Mobile

Perform the following steps to configure alternate display settings for a Widget:

1. Log in to the AppBoard Builder as an administrator.
2. In the Builder Modes panel, click Widgets. The Widgets panel is displayed.
3. Select a Widget and click Edit. The Widget Wizard is displayed.
4. Click the Configure button under Alternate Widget. The alternate widget configuration screen is displayed, with a preview pane on the right and configuration settings panel on the left.
5. Select the appropriate items for the following fields:
   • Layout - Select how the Widget should flow on the mobile device:
     • Flow - Information is displayed in multiple vertical columns in the Widget.
     • Vertical - Information runs from top to bottom in the Widget. This is the default option.
     • Horizontal - Information runs from left to right in the Widget.
     • Coverflow - Information is selected by visually flipping through animated snapshots.
   • Label Orientation - Select where to display the label(s) with regard to the icon in each cell.
     • Bottom - Label(s) will be displayed below their associated icon.
     • Right - Label(s) will be displayed to the right of their associated icon.
   • Label Field - Select the field whose value will be displayed as the label in each cell.
   • Second Label Field - Check the box to select an optional second field whose value will be displayed as a second label in each cell.
   • Default Shape - Select the shape of the icon to display in each cell (unless overridden by a Colored Shape Filter).
   • Icon Size - Select the size of the icon to display in each cell.
   • Default Color - Select the color of the icon to display in each cell (unless overridden by a Colored Shape Filter).
   • Colored Shape Filter - [optional] Create rules to apply for controlling the color and shape of the icons for individual items. See Colored Shape Filter for more information.
6. Confirm that the preview pane displays the appropriate presentation for the alternate widget.
7. Click Finish to save the changes.
8. Load the Widget on the mobile device and confirm that it is displayed properly.

When naming Widgets, you should consider that the same name will be used across the various delivery platforms. For example, you may have a Widget called "Available Services Table" which displays a table of services on the desktop but only shows the status of a single service on the mobile device (using the "Configure Alternate Widget" approach). In this case, a more generic name such as "Available Services" may be preferable.

For more information on configuring AppBoard for mobile devices, see Appboard Mobile.