Appboard/old/associations - Revision history

imported>Jason.nicholls: /* Using Associations to Filter Data */

2014-07-17T18:11:41Z

Using Associations to Filter Data

← Older revision		Revision as of 18:11, 17 July 2014
Line 31:		Line 31:
	==Using Associations to Filter Data==		==Using Associations to Filter Data==

	In the article [[~~Filtering_Collections_Concepts~~#Using_Actions_To_Filter_and_Collect_Data\|Filtering Collections Concepts]], it was illustrated how an action in a Widget can invoke a client-side filter being applied to a Data Collection, which then presented filtered data in a different Widget on a Child Board.		In the article [[appboard/old/filtering_collections_concepts#Using_Actions_To_Filter_and_Collect_Data\|Filtering Collections Concepts]], it was illustrated how an action in a Widget can invoke a client-side filter being applied to a Data Collection, which then presented filtered data in a different Widget on a Child Board.

	The following example uses a different approach to achieve the same result:		The following example uses a different approach to achieve the same result:
Line 40:		Line 40:
	# A special filter did not need to be applied to the "Zip Codes" Data Collection when the action was invoked on the "States Map" widget. The data is filtered automatically by the Association that exists between the "States" and "Zip Codes" Data Sources.		# A special filter did not need to be applied to the "Zip Codes" Data Collection when the action was invoked on the "States Map" widget. The data is filtered automatically by the Association that exists between the "States" and "Zip Codes" Data Sources.
	# In this example, The action in the "States Map" Widget does not need to modify the Data Collection. It simply launches the "Zip Code" Widgets.		# In this example, The action in the "States Map" Widget does not need to modify the Data Collection. It simply launches the "Zip Code" Widgets.


	==Summary==		==Summary==

imported>Jason.nicholls: /* Summary */

2014-07-17T15:32:21Z

Summary

← Older revision		Revision as of 15:32, 17 July 2014
Line 44:		Line 44:
	==Summary==		==Summary==

	This article outlined a method for configuring an action to launch a Board with relevant data by pre-configuring a server-side Association among the Data Sources in the current Board and the Child Board. Another way to launch a Board with information associated to a selected item is by applying a client-side filter. For more information about this approach, see [[~~Action_Apply_a_Filter_to_a_Data_Collection~~\|Action - Apply a Filter to a Data Collection]].		This article outlined a method for configuring an action to launch a Board with relevant data by pre-configuring a server-side Association among the Data Sources in the current Board and the Child Board. Another way to launch a Board with information associated to a selected item is by applying a client-side filter. For more information about this approach, see [[appboard/old/actions/client_side_filter\|Action - Apply a Filter to a Data Collection]].

	A common concept in AppBoard is to click on an item in a Widget to request more detailed information about that specific item. In many cases, this will launch a Child Board with Widgets detailing data for the selected item, as described in this article above. This concept of digging deeper into the data is called a "Drill-down". For information about other Drill-down configuration options, see [[appboard/old/actions/switch_to_a_board\|AppBoard Drill-Downs]].		A common concept in AppBoard is to click on an item in a Widget to request more detailed information about that specific item. In many cases, this will launch a Child Board with Widgets detailing data for the selected item, as described in this article above. This concept of digging deeper into the data is called a "Drill-down". For information about other Drill-down configuration options, see [[appboard/old/actions/switch_to_a_board\|AppBoard Drill-Downs]].

imported>Jason.nicholls at 15:31, 17 July 2014

2014-07-17T15:31:49Z

← Older revision		Revision as of 15:31, 17 July 2014
Line 5:		Line 5:
	Associations are a method of linking AppBoard Data Sources to one another. The concept is similar to creating a Foreign Key in a database table. Once you establish an Association, you can then use that Association as a Data Source in AppBoard Widgets.		Associations are a method of linking AppBoard Data Sources to one another. The concept is similar to creating a Foreign Key in a database table. Once you establish an Association, you can then use that Association as a Data Source in AppBoard Widgets.

	Associations are made on the Server side of AppBoard. If there are certain relationships that you will always want to enforce among data sources, then it will be more efficient to make Associations than to use [[~~Action_Apply_a_Filter_to_a_Data_Collection~~\|Client-side filtering]]. So having the proper Associations in place is an important part of maximizing AppBoard's performance.		Associations are made on the Server side of AppBoard. If there are certain relationships that you will always want to enforce among data sources, then it will be more efficient to make Associations than to use [[appboard/old/actions/client_side_filter\|Client-side filtering]]. So having the proper Associations in place is an important part of maximizing AppBoard's performance.

	__TOC__		__TOC__

imported>Jason.nicholls: /* Summary */

2014-07-17T04:07:41Z

Summary

← Older revision		Revision as of 04:07, 17 July 2014
Line 46:		Line 46:
	This article outlined a method for configuring an action to launch a Board with relevant data by pre-configuring a server-side Association among the Data Sources in the current Board and the Child Board. Another way to launch a Board with information associated to a selected item is by applying a client-side filter. For more information about this approach, see [[Action_Apply_a_Filter_to_a_Data_Collection\|Action - Apply a Filter to a Data Collection]].		This article outlined a method for configuring an action to launch a Board with relevant data by pre-configuring a server-side Association among the Data Sources in the current Board and the Child Board. Another way to launch a Board with information associated to a selected item is by applying a client-side filter. For more information about this approach, see [[Action_Apply_a_Filter_to_a_Data_Collection\|Action - Apply a Filter to a Data Collection]].

	A common concept in AppBoard is to click on an item in a Widget to request more detailed information about that specific item. In many cases, this will launch a Child Board with Widgets detailing data for the selected item, as described in this article above. This concept of digging deeper into the data is called a "Drill-down". For information about other Drill-down configuration options, see [[~~Action_Switch_To_A_Board~~\|AppBoard Drill-Downs]].		A common concept in AppBoard is to click on an item in a Widget to request more detailed information about that specific item. In many cases, this will launch a Child Board with Widgets detailing data for the selected item, as described in this article above. This concept of digging deeper into the data is called a "Drill-down". For information about other Drill-down configuration options, see [[appboard/old/actions/switch_to_a_board\|AppBoard Drill-Downs]].

imported>Jason.nicholls at 03:44, 17 July 2014

2014-07-17T03:44:52Z

← Older revision		Revision as of 03:44, 17 July 2014
Line 1:		Line 1:
			{{DISPLAYTITLE:AppBoard Associations}}
			[[Category:AppBoard old]]
	[[Image:HeaderFlow01.png]]		[[Image:HeaderFlow01.png]]

imported>Jason.nicholls: moved AppBoard Associations to appboard/old/associations

2014-07-17T03:44:24Z

moved AppBoard Associations to appboard/old/associations

← Older revision	Revision as of 03:44, 17 July 2014
(No difference)

imported>Jason.nicholls at 15:09, 27 August 2013

2013-08-27T15:09:50Z

← Older revision		Revision as of 15:09, 27 August 2013
Line 20:		Line 20:
	After an association is created, there is a new Data Source available, as shown in the following illustration:		After an association is created, there is a new Data Source available, as shown in the following illustration:

	[[Image:~~countyAssociationExample~~.jpg\|thumb\|center\|500px\|Selecting a Data Association as a Widget Data Source]]		[[Image:CountyAssociationExample.jpg\|thumb\|center\|500px\|Selecting a Data Association as a Widget Data Source]]

	Associations are indicated by the -> symbol in an AppBoard drop-down listing of Data Sources.		Associations are indicated by the -> symbol in an AppBoard drop-down listing of Data Sources.
Line 33:		Line 33:
	The following example uses a different approach to achieve the same result:		The following example uses a different approach to achieve the same result:

	[[Image:~~stateAssociationExample~~.jpg\|thumb\|center\|500px\|Using an Association to Launch Contextual Widgets on Another Board]]		[[Image:StateAssociationExample.jpg\|thumb\|center\|500px\|Using an Association to Launch Contextual Widgets on Another Board]]

	Two things are observed in the above example:		Two things are observed in the above example:

imported>Cmace: edited filtering collections links

2012-05-01T15:50:24Z

edited filtering collections links

← Older revision		Revision as of 15:50, 1 May 2012
Line 3:		Line 3:
	Associations are a method of linking AppBoard Data Sources to one another. The concept is similar to creating a Foreign Key in a database table. Once you establish an Association, you can then use that Association as a Data Source in AppBoard Widgets.		Associations are a method of linking AppBoard Data Sources to one another. The concept is similar to creating a Foreign Key in a database table. Once you establish an Association, you can then use that Association as a Data Source in AppBoard Widgets.

	Associations are made on the Server side of AppBoard. If there are certain relationships that you will always want to enforce among data sources, then it will be more efficient to make Associations than to use [[~~Filtering_Collections_in_AppBoard~~\|Client-side filtering]]. So having the proper Associations in place is an important part of maximizing AppBoard's performance.		Associations are made on the Server side of AppBoard. If there are certain relationships that you will always want to enforce among data sources, then it will be more efficient to make Associations than to use [[Action_Apply_a_Filter_to_a_Data_Collection\|Client-side filtering]]. So having the proper Associations in place is an important part of maximizing AppBoard's performance.

	__TOC__		__TOC__
Line 29:		Line 29:
	==Using Associations to Filter Data==		==Using Associations to Filter Data==

	In the article [[~~Filtering_Collections_in_AppBoard~~#Using_Actions_To_Filter_and_Collect_Data\|Filtering Collections ~~in AppBoard~~]], it was illustrated how an action in a Widget can invoke a client-side filter being applied to a Data Collection, which then presented filtered data in a different Widget on a Child Board.		In the article [[Filtering_Collections_Concepts#Using_Actions_To_Filter_and_Collect_Data\|Filtering Collections Concepts]], it was illustrated how an action in a Widget can invoke a client-side filter being applied to a Data Collection, which then presented filtered data in a different Widget on a Child Board.

	The following example uses a different approach to achieve the same result:		The following example uses a different approach to achieve the same result:
Line 42:		Line 42:
	==Summary==		==Summary==

	This article outlined a method for configuring an action to launch a Board with relevant data by pre-configuring a server-side Association among the Data Sources in the current Board and the Child Board. Another way to launch a Board with information associated to a selected item is by applying a client-side filter. For more information about this approach, see [[~~Filtering_Collections_in_AppBoard~~\|~~Filtering Collections in AppBoard~~]].		This article outlined a method for configuring an action to launch a Board with relevant data by pre-configuring a server-side Association among the Data Sources in the current Board and the Child Board. Another way to launch a Board with information associated to a selected item is by applying a client-side filter. For more information about this approach, see [[Action_Apply_a_Filter_to_a_Data_Collection\|Action - Apply a Filter to a Data Collection]].

	A common concept in AppBoard is to click on an item in a Widget to request more detailed information about that specific item. In many cases, this will launch a Child Board with Widgets detailing data for the selected item, as described in this article above. This concept of digging deeper into the data is called a "Drill-down". For information about other Drill-down configuration options, see [[Action_Switch_To_A_Board\|AppBoard Drill-Downs]].		A common concept in AppBoard is to click on an item in a Widget to request more detailed information about that specific item. In many cases, this will launch a Child Board with Widgets detailing data for the selected item, as described in this article above. This concept of digging deeper into the data is called a "Drill-down". For information about other Drill-down configuration options, see [[Action_Switch_To_A_Board\|AppBoard Drill-Downs]].

imported>Cmace at 19:04, 8 March 2012

2012-03-08T19:04:15Z

← Older revision		Revision as of 19:04, 8 March 2012
Line 44:		Line 44:
	This article outlined a method for configuring an action to launch a Board with relevant data by pre-configuring a server-side Association among the Data Sources in the current Board and the Child Board. Another way to launch a Board with information associated to a selected item is by applying a client-side filter. For more information about this approach, see [[Filtering_Collections_in_AppBoard\|Filtering Collections in AppBoard]].		This article outlined a method for configuring an action to launch a Board with relevant data by pre-configuring a server-side Association among the Data Sources in the current Board and the Child Board. Another way to launch a Board with information associated to a selected item is by applying a client-side filter. For more information about this approach, see [[Filtering_Collections_in_AppBoard\|Filtering Collections in AppBoard]].

	A common concept in AppBoard is to click on an item in a Widget to request more detailed information about that specific item. In many cases, this will launch a Child Board with Widgets detailing data for the selected item, as described in this article above. This concept of digging deeper into the data is called a "Drill-down". For information about other Drill-down configuration options, see [[Action_Switch_To_A_Board\|~~Switch to a Board~~]].		A common concept in AppBoard is to click on an item in a Widget to request more detailed information about that specific item. In many cases, this will launch a Child Board with Widgets detailing data for the selected item, as described in this article above. This concept of digging deeper into the data is called a "Drill-down". For information about other Drill-down configuration options, see [[Action_Switch_To_A_Board\|AppBoard Drill-Downs]].

imported>Cmace: fixed drilldown link to action switch to a board link

2012-03-08T19:02:57Z

fixed drilldown link to action switch to a board link

← Older revision		Revision as of 19:02, 8 March 2012
Line 44:		Line 44:
	This article outlined a method for configuring an action to launch a Board with relevant data by pre-configuring a server-side Association among the Data Sources in the current Board and the Child Board. Another way to launch a Board with information associated to a selected item is by applying a client-side filter. For more information about this approach, see [[Filtering_Collections_in_AppBoard\|Filtering Collections in AppBoard]].		This article outlined a method for configuring an action to launch a Board with relevant data by pre-configuring a server-side Association among the Data Sources in the current Board and the Child Board. Another way to launch a Board with information associated to a selected item is by applying a client-side filter. For more information about this approach, see [[Filtering_Collections_in_AppBoard\|Filtering Collections in AppBoard]].

	A common concept in AppBoard is to click on an item in a Widget to request more detailed information about that specific item. In many cases, this will launch a Child Board with Widgets detailing data for the selected item, as described in this article above. This concept of digging deeper into the data is called a "Drill-down". For information about other Drill-down configuration options, see [[~~AppBoard_Drill-Downs~~\|~~AppBoard Drill-Downs~~]].		A common concept in AppBoard is to click on an item in a Widget to request more detailed information about that specific item. In many cases, this will launch a Child Board with Widgets detailing data for the selected item, as described in this article above. This concept of digging deeper into the data is called a "Drill-down". For information about other Drill-down configuration options, see [[Action_Switch_To_A_Board\|Switch to a Board]].