You can use dashboard cardsto create configurations of information. Dashboard cards can display information from an application, in a different format. There are many types of dashboard cards, including:

• Date Countdown
• Mini Application
• Notifications

You add dashboard cards to dashboard pages, which a user can open and flip through. You can configure the layout and appearance of cards on the page. This means that you can organize areas of information into pages. For example, a company could have one financial dashboard page that contains payables information such as invoices, contact history, contact notes, and payment details. The company could have another financials dashboard page that contains receivables information such as cash receipt details, invoices, and accounts receivable aging. 

Information displayed on dashboard cards is generated when the dashboard is opened, which means it is always up-to-date. 

Resource scheduling configuration overview

Resource scheduling is built and shipped as one package. There are multiple configurations that must occur to make it work, such as: 

• Calendars—Configure a calendar for events to be scheduled on. Learn more in the Calendar configuration topic. 
• Applications—Configure an application to hold the resources and calendars, and one to hold the events. Set up common context so that when events are scheduled on calendars, their information is copied over.
• Dashboards—Configure a dashboard card over the resource application to show the calendar options. Configure another dashboard card that holds the list form of the events. 
• Logic Blocks—Configure event actions on the application so that user interactions prompt changes to occur. Learn more about event actions in the Logic blocks and event actions topic.

To learn about how to use all of these configurations to create a resource scheduling dashboard, visit the Configure a resource scheduling dashboard topic.

Configure a resource scheduling dashboard

Calendar Definitions

Create a calendar in the Calendar Definitions application, and a Calendar data item in the Data Item Definitions application. Learn more in the Calendar configuration topic.

Table Definitions

In the Table Definitions application:

• Build your events table. This table holds the event types you want to schedule. 
• Build your resource table. This table holds the resources for your calendar. 

Application Builder

In the Application Builder application, build your events application and resource applications over your tables. To enable drag-and-drop functionality, configure Common Context so that the events application is the Publisher, and the resource calendar is the Subscriber. This allows users to drag records from the events dashboard card and copy them to a calendar on the resource dashboard card. Learn more in the Common Context configuration topic.

There are several requirements for the events application, including:

• Application Type must be Standard or Advanced List. 
• Application Style must be Mini App. 
• Configure your Common Context on the Field Dependencies page, in the Publishers field.

The events application, also known as the publisher application, must have List Drag-and-Drop source forms configured in Common Context for each field you want available for subscribed applications.

There are several requirements for the resource application, including:

• Application Type must be Standard or Advanced List.
• Application Style must be Card.
• Add the calendar on the Field Dependencies page, in the Field Dependencies field. Refer to the Calendar configuration topic. 
• Configure your Common Context on the Field Dependencies page, in the Subscribers field.

The resource application, also known as the subscriber application, must use Set Value destination types. 

Dashboard Card Builder

In the Dashboard Card Builder application, create a dashboard card for the events application, and one for the resource application you built. There are several requirements, including:

• Type must be Mini App. 
• Form to Display must be List. 

Dashboard Page Builder

In the Dashboard Page Builder application:

• Create a new page. 
• In the Page Cards field, enter the names of the dashboard cards you created. 
• Select the location and layout of your cards. 

Resource scheduling advanced configurations

Event Icons

In the List Lookup Definitions application, you can configure several list lookups which are shipped empty, such as: 

• CalendarEventIcon1—Populates the Event Icon 1 dropdown menu in the Event dialog box. For example, Plumbing or Electrical icons.
• CalendarEventIcon2—Populates the Event Icon 2 dropdown menu in the Event dialog box. For example, High Priority or Low Priority icons. 
• CalendarEventIcon3—Populates the Event Icon 1 dropdown menu in the Event dialog box. For example, Local or Commute icons. 
• CalendarEventColor—Populates the event color and value. For example, red and blue event colors to indicate if the event is Billed, or Not Billed. 

In the Logic Block Builder applications, configure the logic you want associated with the event actions. 

In Application Builder, use the Calendar Event Created and Calendar Event Updated event actions to configure logic between the application and the list lookups. There are additional event actions you can select from, such as Calendar Event Deleted. Learn more about event actions in the Logic blocks and event actions topic. 

When an event is moved from the events dashboard card to the calendar dashboard card (calendar event creation), or when an event is changed in the source table (calendar event update), the event details are copied onto the calendar. This includes the event icons which have been configured in the list lookups. The event icons cannot be changed when the event was scheduled from a source table. 

If the event was manually added to the calendar by an end user, they can select which icons they want on the Styling page of the Event dialog box. 

Resource Records

The resource application is built over the table that holds all of the details about the resources, like their skills, languages, or locations. 

For example, the Employees application has a Labor Resource Scheduling section on the Employment page.

In the List Lookup Definitionss application, there are several list lookups which you can configure to hold options for the resource records, such as: 

• Resource Scheduling Type—Populates scheduling options such as Plumber, Electrician, or Contractor. These values create a dropdown menu in the SchedulingTypes field, on the Employment page.
• Assigned Locations—Populates available locations for the resources in the company, such as Denver, Boulder, or Fort Collins. They values create a dropdown menu in the AssignedLocations field.

Dashboard cards

You can create different types of dashboard cards, including:

• Date Countdown—Display the time remaining until a specific date and time.
• HTML Content—Display custom information such as text, links, and more.
• Iframe Container—Display content from the web.
• Application—View and edit records from a dashboard page via a mini app. You can have multiple mini app dashboard cards that can share records and interact with one another. Learn more in Common Context.
• Mini Menu—Quickly access applications without opening the Navigation Menu. 
• Notifications—View system notifications. The notifications that display in this card are the same that display in the notifications menu.
• Picture Content—Display a custom image.
• RSS Feed Content—Display a feed of information from the web.
• Stack—Display multiple dashboards cards within a single card. Buttons for each dashboard card are included at the top of the card for navigation. 
• Weather—Display the weather for a given location. You can display the current weather only, or a 5-day forecast.
• Documentation Content—Display a content topic written in the Content Builder application within a dashboard card. Content topics of type concept and application listing, as well as guided tour and release notes, are all supported. 

Dashboard cards only display if they are added to dashboard pages. The layout of dashboard cards is determined by the configuration of the dashboard page. Learn more in Dashboard pages.

The UI elements visible on the card can be configured in the Dashboard Card Builder application, or in the Dashboard Page Builder application.

To configure a visualization on a dashboard card, it must be of type Mini-App in List View with the configuration completed on the underlying application. Learn more in the Visualization data mapper configuration topic. 

Configure announcement dashboards

Dashboard Card Builder

In the Dashboard Card Builder application, you must:

• Create dashboard cards of type Announcements. 
• Under the Announcements section, select the topic types, such as General Announcements and Company Meeting, that you want this card to include. You could create individual cards for each announcement type, or have multiple within the same card. 

Dashboard Page Builder

In the Dashboard Page Builder application, add your announcement dashboard cards to your dashboard pages.

Configure dashboard card stacks

Prerequisites

Before you configure a dashboard card of type Stack, you must already have the cards you want included in the stack created. 

Dashboard Card Builder

In the Dashboard Card Builder, you must:

• Create a new dashboard card of type Stack.
• In the Card Stack subtable, enter the names of the dashboard cards you want included in the stack. 

The order you enter dashboard cards in the subtable dictates what the default order is on the dashboard card stack. Once the dashboard stack is added to a dashboard page, users can drag and drop the cards to rearrange them. 

Dashboard Page Builder

In the Dashboard Page Builder, add your dashboard card stack to any dashboard pages you want it included on. 

Dashboard Card Builder application

Dashboard cards are added to dashboard pages so that users can access features and applications. The type of dashboard card you create determines what configuration options are available. 

For example, a dashboard card of type Application has fields for the application and application setting you are building the card over. You can also select whether the records should be shown in a list or detail form. 

Alternately, a dashboard card of type Stack has a subtable where you can select previously configured cards to include as a single card within a dashboard page. You can select UI elements such as the background color or card height, but the rest of the configuration options come from the dashboard card records referenced in the subtable. 

Dashboard cards can also be built to hold other content such as images, weather updates, content topics, or clickable links. See the Dashboard cards topic for more information.

Dashboard pages

Dashboards can have multiple dashboard pages. Dashboard pages can also be grouped together in a dashboard site. Pages provide a way to organize dashboard cards in different layouts and orders based on user requirements. 

When you sign in to the platform, the first favorite on your favorites bar opens up automatically on your dashboard. 

Layout and configuration

When you configure the layout of a dashboard page, you can choose from a variety of options. This layout determines the size and display of dashboard cards on a page. 

To edit a dashboard page, you can navigate back to the Dashboard Page Builder application, or use the Show Dashboard Edit Options toggle on the dashboard favorites bar. Select the toggle to populate the Edit Page, Add Page, and Edit Card buttons that allow you to make changes.

Select the Edit Page button to open up the Dashboard Page Builder application on the side of your dashboard. This allows you to modify multiple things, such as the name of your page, the layout of your page, position of the cards, what cards are on the page, and if the page is on your favorites bar. You can also select from preconfigured options that control what UI elements are visible, such as filter modifiers, column headers, or borders on the page, or cards.

Select the Edit Card button to open up the Dashboard Card Builder application on the side of your dashboard. This allows you to change the card Type, Product Family, Name, and Description. When you select Save and Exit, or exit the menu, the edit options close automatically. 

Dashboard Page Builder application

There are multiple configuration options for dashboard pages, using the following fields:

• Page Layout—Select different layout options for the dashboard cards, such as columns or full screen, depending on user requirements. You can also select from preset options which control the style of a mini app dashboard card and which user interface controls are visible
• DashboardPageCards.DashboardCardLoadOption—Select the order in which dashboard cards should be loaded. 
• Background Image Content Item—Select a background image to display on your dashboard.
• Hide Page from Dashboard Override—Hide your page if you aren't currently using it or it isn't ready for release yet. This does not secure the data. 
• Add to Favorites Bar—Add your dashboard page to the favorites bar of all users who are granted access.
• Auto Refresh—Enable auto-refresh options on the dashboard page. When selected, the refresh button includes an action menu of refresh options for users. 

When you add a page to a dashboard that is not hidden, it is available to all users.

Dashboard sites

To build a new site, navigate to the Dashboard Site Builder application and create a new record. Add the dashboard pages you want included in the Dashboard Pages subtable. If a site is built as a global favorite, all users with permissions to access the site see it automatically on their favorites bar. 

Configured dashboard sites appear in the dashboard picker menu found on your favorites bar. When you select a dashboard site, a list of the dashboard pages within the site become available for selection. 

You can favorite a dashboard site by press and holding the Shift key on PC, or the Option key on Mac, and then selecting it. The dashboard pages within the site are then included on the favorites bar as a group of tabs which are indicated by the same color. To collapse the tabs, select the site button on the left side of the site tabs. When the tabs are collapsed, you can select the site button to expand them.

 You can use the drag and drop functionality to reorder your favorite pages, sites, and applications. 

Dashboard Site Builder application

Add the dashboard pages you want included in the dashboard site in the Dashboard Pages subtable. 

If you configure the site to be a global favorite, all users with permissions to access the site see it automatically on their favorites bar.

The sequence field determines the order in which your site appears in the favorite bar, but only if it is set to be a global favorite. If you have a combination of sites and dashboard pages as global favorites, the Sequence field determines what order they appear in. 

The selected Site Group is used to enable permissions for the dashboard site. If a user is given security permissions for the dashboard site, they still need individual permissions for the dashboard pages inside of it.

Dashboard site permissions configuration topic. 

Content Item Definitions application

Dashboard cards

Some dashboard cards, such as HTML, Picture, iFrame, and RSS, require an association with a content item to display content. For example, you can create a Source URL content item in the Content Item Definitions application, and then associate it with an iFrame or RSS feed dashboard card by selecting it in the Content Item Key field. This displays the web content in the dashboard card. 

Other application uses

Application developers can create templates in the Content Item Definitions application and link them to data items in the Text Template Setup application. This creates a field action button on the field which has the predefined content available for users to select from.

The type of data item determines what information can be stored in the field, such as numbers or text. For example, Text Editor data items creates a text box with full formatting, such as the number of text lines allowed and default text for the field which a user can replace. 

Link multiple templates with the same field to create a dropdown menu which users can select from. The original reference text self updates from the template in the Text Template Setup application. Learn more in the Configure a field with content templates topic.

Dashboard best practices

Cards

For better performance, limit the number of cards. The more cards that are placed on a dashboard, increases the time to load the dashboard page. Best practice is to limit to five cards. The browser has a limit of the number of six requests at a time. Additional requests are queued and processed as a request is completed. The number of requests should be considered when creating a dashboard page. We will not limit the number of cards or requests, but the developer should understand the implications of performance. 

Each aggregation and visualization is a request to the server. Our best practice is to limit to aggregations and/or visualizations to more than two.

Other considerations that increase the time it takes to render a dashboard page. 

1.  Aggregations - consider if your mini app in a card needs totals in the footer. Every aggregation is an individual request to the server.
2. Visualizations - consider the number of visualizations on your page. Each visualization is an individual request to the server.
3. External callouts to 3rd party system (iFrame) 

Common context filter field placement

When configuring a publishing filter card in a dashboard using common context, the card should be positioned in the top left corner of the dashboard page as users typically read a page starting at the top left.

RSS and iFrame Security

Consider the security implications of iFrames from third party systems.