Appboard/2.4/overview - Revision history

imported>Jason.nicholls: /* Data Sources */

2014-02-07T02:00:14Z

Data Sources

← Older revision		Revision as of 02:00, 7 February 2014
Line 30:		Line 30:
	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.		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.

	[[File:DataSources.png\|link=]]		[[File:DataSources.png\|center\|link=]]

imported>Jason.nicholls: /* Stacks and Boards */

2014-02-07T01:59:07Z

Stacks and Boards

← Older revision		Revision as of 01:59, 7 February 2014
Line 65:		Line 65:
	In AppBoard, Widgets are placed on "Boards". A collection of Boards is called a "Stack".		In AppBoard, Widgets are placed on "Boards". A collection of Boards is called a "Stack".

	[[image:BoardFlow.png]]		[[image:BoardFlow.png\|link=]]

	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 provisioning is done at the stack level by assigning stacks to roles.		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 provisioning is done at the stack level by assigning stacks to roles.

	[[image:StackFlow.png]]		[[image:StackFlow.png\|link=]]


	Refer to the main [[appboard/2.4/builder\|Builder]] page for more information on Stacks, Boards, and Provisioning.		Refer to the main [[appboard/2.4/builder\|Builder]] page for more information on Stacks, Boards, and Provisioning.

imported>Jason.nicholls: /* Widgets */

2014-02-07T01:58:43Z

Widgets

← Older revision		Revision as of 01:58, 7 February 2014
Line 54:		Line 54:
	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.		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]]		[[image:WidgetFlow.png\|link=]]

	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.		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]]		[[image:WidgetActionsFlow.png\|link=]]

	Refer to the [[appboard/2.4/builder/widgets\|Widgets]] page for more information.		Refer to the [[appboard/2.4/builder/widgets\|Widgets]] page for more information.

imported>Jason.nicholls: /* Data Collections */

2014-02-07T01:58:25Z

Data Collections

← Older revision		Revision as of 01:58, 7 February 2014
Line 47:		Line 47:
	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".		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]]		[[image:DataCollection.png\|link=]]

	Data Collections are the foundational block that all AppBoard visualizations are based upon. For more information refer to the [[appboard/2.4/builder/data_collections\|Data Collections]] page.		Data Collections are the foundational block that all AppBoard visualizations are based upon. For more information refer to the [[appboard/2.4/builder/data_collections\|Data Collections]] page.

imported>Jason.nicholls: /* Data Sources */

2014-02-07T01:58:00Z

Data Sources

← Older revision		Revision as of 01:58, 7 February 2014
Line 39:		Line 39:
	# Data caching also provides a way to optimize performance to clients and also reduce the load on the back-end data source.		# Data caching also provides a way to optimize performance to clients and also reduce the load on the back-end data source.

	[[File:AdapterFlow.png\|center\|~~800px~~\|link=\|Flow of data through AppBoard]]		[[File:AdapterFlow.png\|center\|750px\|link=\|Flow of data through AppBoard]]

	For more information refer to the [[appboard/2.4/builder/data_sources\|Data Sources]] page.		For more information refer to the [[appboard/2.4/builder/data_sources\|Data Sources]] page.

imported>Jason.nicholls: /* Data Sources */

2014-02-07T01:57:39Z

Data Sources

← Older revision		Revision as of 01:57, 7 February 2014
Line 30:		Line 30:
	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.		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.

	[[File:DataSources.png]]		[[File:DataSources.png\|link=]]


Line 39:		Line 39:
	# Data caching also provides a way to optimize performance to clients and also reduce the load on the back-end data source.		# Data caching also provides a way to optimize performance to clients and also reduce the load on the back-end data source.

	[[File:AdapterFlow.png\|center\|800px\|Flow of data through AppBoard]]		[[File:AdapterFlow.png\|center\|800px\|link=\|Flow of data through AppBoard]]

	For more information refer to the [[appboard/2.4/builder/data_sources\|Data Sources]] page.		For more information refer to the [[appboard/2.4/builder/data_sources\|Data Sources]] page.

imported>Jason.nicholls: /* Basic Concepts */

2014-02-07T01:57:14Z

Basic Concepts

← Older revision		Revision as of 01:57, 7 February 2014
Line 11:		Line 11:
	== Basic Concepts ==		== Basic Concepts ==

	[[image:HeaderFlow00.png]]		[[image:HeaderFlow00.png\|link=]]

	At the top level, the dashboards a user can see are represented by '''Stacks''' which are a collection of '''Boards'''. Each Board is a separate dashboard in its own right with its own set of visualization '''Widgets'''. Widgets visualize a '''Data Collection''' that may 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.		At the top level, the dashboards a user can see are represented by '''Stacks''' which are a collection of '''Boards'''. Each Board is a separate dashboard in its own right with its own set of visualization '''Widgets'''. Widgets visualize a '''Data Collection''' that may 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.

imported>David.moore: /* Data Sources */

2013-12-24T22:09:38Z

Data Sources

← Older revision		Revision as of 22:09, 24 December 2013
Line 33:		Line 33:


	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.		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.		# 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.		# "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.		# "Client Side Filters" allow you to take advantage of information that's already available in client memory.

imported>David.moore: /* Basic Concepts */

2013-12-24T22:06:25Z

Basic Concepts

← Older revision		Revision as of 22:06, 24 December 2013
Line 13:		Line 13:
	[[image:HeaderFlow00.png]]		[[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''' that may 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.		At the top level, the dashboards a user can see are represented by '''Stacks''' which are a collection of '''Boards'''. Each Board is a separate dashboard in its own right with its own set of visualization '''Widgets'''. Widgets visualize a '''Data Collection''' that may 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.

	As an AppBoard administrator tasked with building dashboards the process is roughly broken into two parts:		As an AppBoard administrator tasked with building dashboards the process is roughly broken into two parts:

imported>Jason.nicholls at 08:58, 13 December 2013

2013-12-13T08:58:49Z

← Older revision		Revision as of 08:58, 13 December 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:AppBoard Overview}}		{{DISPLAYTITLE:AppBoard Overview}}
			[[Category:AppBoard 2.4]]

	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.		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.