Appboard/2.4/overview: Difference between revisions
imported>Jason.nicholls No edit summary |
imported>Jason.nicholls No edit summary |
||
| Line 6: | Line 6: | ||
End-users of the system use the AppBoard '''Viewer''' which is also a Adobe Flash based client. This provides users with a restricted set of dashboards with the ability to interact but not modify the contents or behaviour. | End-users of the system use the AppBoard '''Viewer''' which is also a Adobe Flash based client. This provides users with a restricted set of dashboards with the ability to interact but not modify the contents or behaviour. | ||
== Basic Concepts == | |||
[[image:HeaderFlow00.png]] | |||
At the top level, the dashboards a user can see is represented by '''Stacks''' which are a collection of '''Boards'''. Each Board is a separate dashboard in it's own right with it's own set of visualization '''Widgets'''. Widgets visualize a '''Data Collection''' which could have been filtered on the server side, or the client side. Finally these data collections are driven by data from external '''Data Sources''' such as databases. | |||
=== Data Sources === | |||
Good data visualization requires good data. This data can be stored in a variety of different locations and formats, which can lead to problems when trying to create holistic summary views. AppBoard has a dedicated "Data Source" mode that allows you to access all this information, regardless of where it is or what format it is in. | |||
[[image:DataSources.png]] | |||
Another challenge to data visualization is that the raw data available from these "data sources" must first be manipulated or optimized before it can be useful. Appboard provides you with some powerful data manipulation tools to optimize data so that it can be effectively visualized. | |||
# Appboard gives you the ability to Group, Pivot, and Sort information both on the client, and at the server. | |||
# "Server Side Filters" also allow you to optimize large data sets before you bring it into a memory on the client. | |||
# "Client Side Filters" allow you to take advantage of information that's already available in client memory. | |||
# An optional "Entity Adapter" allows you to write custom queries and make associations based on data in the server's memory. | |||
# [[Caching_And_Polling|Caching and Polling]] settings allow you to optimize the performance of refreshing data. | |||
[[image:AdapterFlow.png]] | |||
There are several different ways to apply a "Server Side Filter" inside of Appboard. | |||
Refer to the following sections for more information about server side filtering: | |||
* [[Data_Sources|Creating Data Sources]] | |||
* [[AppBoard_Associations|Associations]] | |||
* [[AppBoard_Server-Side_Queries|Server-Side Queries]] | |||
* [[AppBoard_Query_Entities|Query Entities]] | |||
=== Data Collections === | |||
Any data that is pulled into AppBoard gets placed into a "Data collection". This information is stored in memory on the client, so it is rapidly available to any widget or board that has appropriate permissions. Like "Data Sources", AppBoard has a dedicated mode that allows you to manage all your "Data Collections". The "Data Collections Wizard" allows you to control how much information you are bringing into memory via "Server Side Filter", but you can also manipulate the data already in memory via "Client Side Filter". | |||
[[image:DataCollection.png]] | |||
Data Collections are the foundational block that all AppBoard visualizations are based upon. | |||
Refer to the following sections for more information about Data Collections: | |||
* [[Data_Collections|Creating Data Collections]] | |||
* [[Filtering_Data_Collections|Filtering of Collections]] | |||
=== Widgets === | |||
Data visualization inside AppBoard is done by associating a Data Collection with a Widget. AppBoard contains a number of widgets, but every widget requires a Data Collection. | |||
[[image:WidgetFlow.png]] | |||
On top of just visualizing data, Widgets allow you to configure "Actions". For example, you can contextually filter one widget based on a selection in another, or you can drill down into a child board that shows details based on an item selected in the parent. The key is knowing that when you click on a Widget, you're actually clicking on the piece of data that's being represented by the widget. Actions allow you to use this piece of data as context to alter client or server side filters for any Data Collection inside AppBoard. This flexibility allows for extremely powerful interactions. | |||
[[image:WidgetActionsFlow.png]] | |||
Refer to the following section for more information about Widgets: | |||
* [[Widget_Types|Available Types of Widgets]] | |||
* [[Action_Switch_To_A_Board|Drill-Downs]] | |||
* [[Actions|Actions]] | |||
=== Stacks and Boards === | |||
In AppBoard, Widgets are placed on "Boards". A collection of Boards is called a "Stack". | |||
[[image:BoardFlow.png]] | |||
Each stack has a corresponding tab in the banner area of the builder which lets you navigate to that stack. Stacks are an important concept because user permissions are provisioned at the Stack level. | |||
[[image:StackFlow.png]] | |||
Refer to the following sections for more information about Stacks and Provisioning: | |||
* [[Stacks|Creating Stacks]] | |||
* [[Boards|Creating Boards]] | |||
* [[AppBoard_Provisioning|Provisioning]] | |||
=== Data Sources === | |||
Good data visualization requires good data. This data can be stored in a variety of different locations and formats, which can lead to problems when trying to create holistic summary views. AppBoard has a dedicated "Data Source" mode that allows you to access all this information, regardless of where it is or what format it is in. | |||
[[image:DataSources.png]] | |||
Another challenge to data visualization is that the raw data available from these "data sources" must first be manipulated or optimized before it can be useful. Appboard provides you with some powerful data manipulation tools to optimize data so that it can be effectively visualized. | |||
# Appboard gives you the ability to Group, Pivot, and Sort information both on the client, and at the server. | |||
# "Server Side Filters" also allow you to optimize large data sets before you bring it into a memory on the client. | |||
# "Client Side Filters" allow you to take advantage of information that's already available in client memory. | |||
# An optional "Entity Adapter" allows you to write custom queries and make associations based on data in the server's memory. | |||
# [[Caching_And_Polling|Caching and Polling]] settings allow you to optimize the performance of refreshing data. | |||
[[image:AdapterFlow.png]] | |||
There are several different ways to apply a "Server Side Filter" inside of Appboard. | |||
Refer to the following sections for more information about server side filtering: | |||
* [[Data_Sources|Creating Data Sources]] | |||
* [[AppBoard_Associations|Associations]] | |||
* [[AppBoard_Server-Side_Queries|Server-Side Queries]] | |||
* [[AppBoard_Query_Entities|Query Entities]] | |||
=== Data Collections === | |||
Any data that is pulled into AppBoard gets placed into a "Data collection". This information is stored in memory on the client, so it is rapidly available to any widget or board that has appropriate permissions. Like "Data Sources", AppBoard has a dedicated mode that allows you to manage all your "Data Collections". The "Data Collections Wizard" allows you to control how much information you are bringing into memory via "Server Side Filter", but you can also manipulate the data already in memory via "Client Side Filter". | |||
[[image:DataCollection.png]] | |||
Data Collections are the foundational block that all AppBoard visualizations are based upon. | |||
Refer to the following sections for more information about Data Collections: | |||
* [[Data_Collections|Creating Data Collections]] | |||
* [[Filtering_Data_Collections|Filtering of Collections]] | |||
=== Widgets === | |||
Data visualization inside AppBoard is done by associating a Data Collection with a Widget. AppBoard contains a number of widgets, but every widget requires a Data Collection. | |||
[[image:WidgetFlow.png]] | |||
On top of just visualizing data, Widgets allow you to configure "Actions". For example, you can contextually filter one widget based on a selection in another, or you can drill down into a child board that shows details based on an item selected in the parent. The key is knowing that when you click on a Widget, you're actually clicking on the piece of data that's being represented by the widget. Actions allow you to use this piece of data as context to alter client or server side filters for any Data Collection inside AppBoard. This flexibility allows for extremely powerful interactions. | |||
[[image:WidgetActionsFlow.png]] | |||
Refer to the following section for more information about Widgets: | |||
* [[Widget_Types|Available Types of Widgets]] | |||
* [[Action_Switch_To_A_Board|Drill-Downs]] | |||
* [[Actions|Actions]] | |||
=== Stacks and Boards === | |||
In AppBoard, Widgets are placed on "Boards". A collection of Boards is called a "Stack". | |||
[[image:BoardFlow.png]] | |||
Each stack has a corresponding tab in the banner area of the builder which lets you navigate to that stack. Stacks are an important concept because user permissions are provisioned at the Stack level. | |||
[[image:StackFlow.png]] | |||
Refer to the following sections for more information about Stacks and Provisioning: | |||
* [[Stacks|Creating Stacks]] | |||
* [[Boards|Creating Boards]] | |||
* [[AppBoard_Provisioning|Provisioning]] | |||
Revision as of 04:25, 4 September 2013
AppBoard is a data visualization tool that works by fetching data from a variety of data sources and caches, transforms, associates, and then presents the data in a set of dashboards. AppBoard dashboards are not static however, as actions can be defined to perform drill-downs, filter content, show additional details, and more. As a result it's possible to build highly interactive dashboards that allows users to quickly both visualize data and zero-in on the information they need to perform their job.
Building dashboards in AppBoard is easy using the Builder tool which is a graphical Adobe Flash based client. All configuration is GUI based including configuring collecting and managing data, building out content, and other system administration functions.
End-users of the system use the AppBoard Viewer which is also a Adobe Flash based client. This provides users with a restricted set of dashboards with the ability to interact but not modify the contents or behaviour.
Basic Concepts
At the top level, the dashboards a user can see is represented by Stacks which are a collection of Boards. Each Board is a separate dashboard in it's own right with it's own set of visualization Widgets. Widgets visualize a Data Collection which could have been filtered on the server side, or the client side. Finally these data collections are driven by data from external Data Sources such as databases.
Data Sources
Good data visualization requires good data. This data can be stored in a variety of different locations and formats, which can lead to problems when trying to create holistic summary views. AppBoard has a dedicated "Data Source" mode that allows you to access all this information, regardless of where it is or what format it is in.
Another challenge to data visualization is that the raw data available from these "data sources" must first be manipulated or optimized before it can be useful. Appboard provides you with some powerful data manipulation tools to optimize data so that it can be effectively visualized.
- Appboard gives you the ability to Group, Pivot, and Sort information both on the client, and at the server.
- "Server Side Filters" also allow you to optimize large data sets before you bring it into a memory on the client.
- "Client Side Filters" allow you to take advantage of information that's already available in client memory.
- An optional "Entity Adapter" allows you to write custom queries and make associations based on data in the server's memory.
- Caching and Polling settings allow you to optimize the performance of refreshing data.
There are several different ways to apply a "Server Side Filter" inside of Appboard.
Refer to the following sections for more information about server side filtering:
Data Collections
Any data that is pulled into AppBoard gets placed into a "Data collection". This information is stored in memory on the client, so it is rapidly available to any widget or board that has appropriate permissions. Like "Data Sources", AppBoard has a dedicated mode that allows you to manage all your "Data Collections". The "Data Collections Wizard" allows you to control how much information you are bringing into memory via "Server Side Filter", but you can also manipulate the data already in memory via "Client Side Filter".
Data Collections are the foundational block that all AppBoard visualizations are based upon.
Refer to the following sections for more information about Data Collections:
Widgets
Data visualization inside AppBoard is done by associating a Data Collection with a Widget. AppBoard contains a number of widgets, but every widget requires a Data Collection.
On top of just visualizing data, Widgets allow you to configure "Actions". For example, you can contextually filter one widget based on a selection in another, or you can drill down into a child board that shows details based on an item selected in the parent. The key is knowing that when you click on a Widget, you're actually clicking on the piece of data that's being represented by the widget. Actions allow you to use this piece of data as context to alter client or server side filters for any Data Collection inside AppBoard. This flexibility allows for extremely powerful interactions.
Refer to the following section for more information about Widgets:
Stacks and Boards
In AppBoard, Widgets are placed on "Boards". A collection of Boards is called a "Stack".
Each stack has a corresponding tab in the banner area of the builder which lets you navigate to that stack. Stacks are an important concept because user permissions are provisioned at the Stack level.
Refer to the following sections for more information about Stacks and Provisioning:
Data Sources
Good data visualization requires good data. This data can be stored in a variety of different locations and formats, which can lead to problems when trying to create holistic summary views. AppBoard has a dedicated "Data Source" mode that allows you to access all this information, regardless of where it is or what format it is in.
Another challenge to data visualization is that the raw data available from these "data sources" must first be manipulated or optimized before it can be useful. Appboard provides you with some powerful data manipulation tools to optimize data so that it can be effectively visualized.
- Appboard gives you the ability to Group, Pivot, and Sort information both on the client, and at the server.
- "Server Side Filters" also allow you to optimize large data sets before you bring it into a memory on the client.
- "Client Side Filters" allow you to take advantage of information that's already available in client memory.
- An optional "Entity Adapter" allows you to write custom queries and make associations based on data in the server's memory.
- Caching and Polling settings allow you to optimize the performance of refreshing data.
There are several different ways to apply a "Server Side Filter" inside of Appboard.
Refer to the following sections for more information about server side filtering:
Data Collections
Any data that is pulled into AppBoard gets placed into a "Data collection". This information is stored in memory on the client, so it is rapidly available to any widget or board that has appropriate permissions. Like "Data Sources", AppBoard has a dedicated mode that allows you to manage all your "Data Collections". The "Data Collections Wizard" allows you to control how much information you are bringing into memory via "Server Side Filter", but you can also manipulate the data already in memory via "Client Side Filter".
Data Collections are the foundational block that all AppBoard visualizations are based upon.
Refer to the following sections for more information about Data Collections:
Widgets
Data visualization inside AppBoard is done by associating a Data Collection with a Widget. AppBoard contains a number of widgets, but every widget requires a Data Collection.
On top of just visualizing data, Widgets allow you to configure "Actions". For example, you can contextually filter one widget based on a selection in another, or you can drill down into a child board that shows details based on an item selected in the parent. The key is knowing that when you click on a Widget, you're actually clicking on the piece of data that's being represented by the widget. Actions allow you to use this piece of data as context to alter client or server side filters for any Data Collection inside AppBoard. This flexibility allows for extremely powerful interactions.
Refer to the following section for more information about Widgets:
Stacks and Boards
In AppBoard, Widgets are placed on "Boards". A collection of Boards is called a "Stack".
Each stack has a corresponding tab in the banner area of the builder which lets you navigate to that stack. Stacks are an important concept because user permissions are provisioned at the Stack level.
Refer to the following sections for more information about Stacks and Provisioning:
