Appboard/2.5/builder/widgets/actions - Revision history

imported>Jason.nicholls: /* Action Filtering */

2014-12-15T12:33:08Z

Action Filtering

← Older revision		Revision as of 12:33, 15 December 2014
Line 123:		Line 123:
	The following descriptions apply to the screenshot above:		The following descriptions apply to the screenshot above:

	# This shows the default action filtering for a widget that ~~does not support attribute~~ filtering. In the default case any user selection will result in the action firing.		# This shows the default action filtering for a widget that only supports filtering on the selected row data. In the default case any user selection will result in the action firing.
	# For widgets that support attribute filtering there is an additional section ''with [any] attribute''. Again by default any user selection will result in the action firing. If the attribute has been configured, then in order to reset to the ''[any]'' state use <tt>CTRL+click</tt> on the selected item to un-select it.		# For widgets that support attribute filtering there is an additional section ''with [any] attribute''. Again by default any user selection will result in the action firing. If the attribute has been configured, then in order to reset to the ''[any]'' state use <tt>CTRL+click</tt> on the selected item to un-select it.
	# This filter rule has been configured with a ''specific Filter'' and with an ''attribute''. Clicking the ''Filter'' button will bring up the ''Filter Editor''. This editor is just as with the Icon, Color, and Status Shape filters and allows a set of conditions to be constructed which will be tested against data from the selected row.		# This filter rule has been configured with a ''specific Filter'' and with an ''attribute''. Clicking the ''Filter'' button will bring up the ''Filter Editor''. This editor is just as with the Icon, Color, and Status Shape filters and allows a set of conditions to be constructed which will be tested against data from the selected row.

	If multiple actions need to fire using the same conditions it can become cumbersome to set up action filters on each action. Instead, use ''Bundled Actions''. That way just the bundle action itself needs to have an action filter configured and all actions within the bundle will fire.		If multiple actions need to fire using the same conditions it can become cumbersome to set up action filters on each action. Instead, use ''Bundled Actions''. That way just the bundle action itself needs to have an action filter configured and all actions within the bundle will fire.

imported>Jason.nicholls: /* Action Filtering */

2014-12-15T12:32:16Z

Action Filtering

← Older revision		Revision as of 12:32, 15 December 2014
Line 120:		Line 120:

	[[File:appboard-2.5-widget-action-filtering.png\|frame\|center\|Action filtering]]		[[File:appboard-2.5-widget-action-filtering.png\|frame\|center\|Action filtering]]

			The following descriptions apply to the screenshot above:

	# This shows the default action filtering for a widget that does not support attribute filtering. In the default case any user selection will result in the action firing.		# This shows the default action filtering for a widget that does not support attribute filtering. In the default case any user selection will result in the action firing.

imported>Jason.nicholls: /* Action Filtering */

2014-12-15T12:30:06Z

Action Filtering

← Older revision		Revision as of 12:30, 15 December 2014
Line 112:		Line 112:
	=== Action Filtering ===		=== Action Filtering ===

	In addition to performing actions in context the context itself can be used to determine whether the action should fire at all. The ~~context will include~~ the row a user has selected, and depending on the widget type, may also include the attribute selected. This provides a powerful mechanism to do different things depending on what the user selects.		In addition to performing actions in context, the context itself can be used to determine whether the action should fire at all. The information available to action filtering includes the data from the row a user has selected, and depending on the widget type, may also include the attribute selected. This provides a powerful mechanism to do different things depending on what the user selects.

	For example, take a visualization which presents regional locations, main offices, and data centers all on the same map. If the location type information is available within the data collection then this can be used to drive visualization filters to visually indicate the difference between locations, and an administrator can configure actions to fire based on the location type too. Such as each location type taking the end-user to a ''different'' drill-down board based on that type.		For example, take a visualization which presents regional locations, main offices, and data centers all on the same map. If the location type information is available within the data collection then this can be used to drive visualization filters to visually indicate the difference between locations, and an administrator can configure actions to fire based on the location type too. Such as each location type taking the end-user to a ''different'' drill-down board based on that type.

imported>Jason.nicholls: /* Action Filtering */

2014-12-15T12:28:46Z

Action Filtering

← Older revision		Revision as of 12:28, 15 December 2014
Line 111:		Line 111:

	=== Action Filtering ===		=== Action Filtering ===
	~~Not only does clicking or hovering on something allow you~~ to ~~perform~~ actions in context~~, but~~ the context can ~~also~~ be used to determine ~~what actions to~~ fire. This provides a powerful mechanism to do different things depending on what the user ~~has selected~~.
			In addition to performing actions in context the context itself can be used to determine whether the action should fire at all. The context will include the row a user has selected, and depending on the widget type, may also include the attribute selected. This provides a powerful mechanism to do different things depending on what the user selects.

	For example, take a visualization which presents regional locations, main offices, and data centers all on the same map. If the location type information is available within the data collection then this can be used to drive visualization filters to visually indicate the difference between locations, and an administrator can configure actions to fire based on the location type too. Such as each location type taking the end-user to a ''different'' drill-down board based on that type.		For example, take a visualization which presents regional locations, main offices, and data centers all on the same map. If the location type information is available within the data collection then this can be used to drive visualization filters to visually indicate the difference between locations, and an administrator can configure actions to fire based on the location type too. Such as each location type taking the end-user to a ''different'' drill-down board based on that type.

			Another example, a table includes a column with an icon representing an external link. It's possible with attribute selection to create a Launch URL action that will only fire when the user selects this column specifically.


	[[File:appboard-2.5-widget-action-filtering.png\|frame\|center\|Action filtering]]		[[File:appboard-2.5-widget-action-filtering.png\|frame\|center\|Action filtering]]

	~~The line below~~ the action ~~name~~ that ~~begins~~ with ''On selection of .~~..'' is used~~ to ~~configure action filtering. By default this is set~~ to ''any''~~, which means~~ the ~~action will fire on any selection~~. ~~To enable action filtering:~~		# This shows the default action filtering for a widget that does not support attribute filtering. In the default case any user selection will result in the action firing.
			# For widgets that support attribute filtering there is an additional section ''with [any] attribute''. Again by default any user selection will result in the action firing. If the attribute has been configured, then in order to reset to the ''[any]'' state use <tt>CTRL+click</tt> on the selected item to un-select it.
	# ~~Change the~~ ''~~On selection of~~'' ~~preference to~~ ''~~specific~~''.		# This filter rule has been configured with a ''specific Filter'' and with an ''attribute''. Clicking the ''Filter'' button will bring up the ''Filter Editor''. This editor is just as with the Icon, Color, and Status Shape filters and allows a set of conditions to be constructed which will be tested against data from the selected row.
	~~# Click~~ the ''Filter'' button ~~to manage~~ the ~~filter conditions. Using the (action)~~ Filter Editor is just as with the Icon, Color, and Status Shape filters~~. Build out one or more rules that~~ will ~~determine whether~~ the ~~action will fire~~.

	If multiple actions need to fire using the same conditions it can become cumbersome to set up action filters on each action. Instead, use ''Bundled Actions''. That way just the bundle action itself needs to have an action filter configured and all actions within the bundle will fire.		If multiple actions need to fire using the same conditions it can become cumbersome to set up action filters on each action. Instead, use ''Bundled Actions''. That way just the bundle action itself needs to have an action filter configured and all actions within the bundle will fire.

imported>Jason.nicholls: /* Action Filtering */

2014-12-15T12:09:24Z

Action Filtering

← Older revision		Revision as of 12:09, 15 December 2014
Line 115:		Line 115:
	For example, take a visualization which presents regional locations, main offices, and data centers all on the same map. If the location type information is available within the data collection then this can be used to drive visualization filters to visually indicate the difference between locations, and an administrator can configure actions to fire based on the location type too. Such as each location type taking the end-user to a ''different'' drill-down board based on that type.		For example, take a visualization which presents regional locations, main offices, and data centers all on the same map. If the location type information is available within the data collection then this can be used to drive visualization filters to visually indicate the difference between locations, and an administrator can configure actions to fire based on the location type too. Such as each location type taking the end-user to a ''different'' drill-down board based on that type.

	[[File:appboard-2.4-widget-action-filtering.png\|frame\|center\|Action filtering ~~enabled~~]]		[[File:appboard-2.5-widget-action-filtering.png\|frame\|center\|Action filtering]]

	The line below the action name that begins with ''On selection of ...'' is used to configure action filtering. By default this is set to ''any'', which means the action will fire on any selection. To enable action filtering:		The line below the action name that begins with ''On selection of ...'' is used to configure action filtering. By default this is set to ''any'', which means the action will fire on any selection. To enable action filtering:

imported>Jason.nicholls: /* Managing Actions */

2014-09-10T17:41:55Z

Managing Actions

← Older revision		Revision as of 17:41, 10 September 2014
Line 103:		Line 103:
	* use the ''Add Action'' button to add a new action		* use the ''Add Action'' button to add a new action
	* edit action configuration for existing actions		* edit action configuration for existing actions
			** The ''Name'' field is information only, please set to something descriptive.
	** For details on configuring individual actions refer to the tables above.		** For details on configuring individual actions refer to the tables above.
	** For details on configuring action filtering see the section below.		** For details on configuring action filtering see the section below.

imported>Jason.nicholls: /* Action Filtering */

2014-09-10T17:25:20Z

Action Filtering

← Older revision		Revision as of 17:25, 10 September 2014
Line 112:		Line 112:
	Not only does clicking or hovering on something allow you to perform actions in context, but the context can also be used to determine what actions to fire. This provides a powerful mechanism to do different things depending on what the user has selected.		Not only does clicking or hovering on something allow you to perform actions in context, but the context can also be used to determine what actions to fire. This provides a powerful mechanism to do different things depending on what the user has selected.

	For example, ~~imagine~~ a ~~map showing both data center~~ locations and ~~office locations represented with differing icons. The~~ data ~~collection driving~~ the map ~~would need to include~~ the information ~~about what type of location each point~~ is ~~and~~ this ~~could~~ be used to ~~trigger one set of~~ actions ~~when clicking~~ on a ~~data center, versus a~~ different ~~set of actions when clicking~~ on ~~an office location~~.		For example, take a visualization which presents regional locations, main offices, and data centers all on the same map. If the location type information is available within the data collection then this can be used to drive visualization filters to visually indicate the difference between locations, and an administrator can configure actions to fire based on the location type too. Such as each location type taking the end-user to a ''different'' drill-down board based on that type.

			[[File:appboard-2.4-widget-action-filtering.png\|frame\|center\|Action filtering enabled]]

	The line below the action name that begins with ''On selection of ...'' is used to configure action filtering. By default this is set to ''any'', which means the action will fire on any selection. To enable action filtering:		The line below the action name that begins with ''On selection of ...'' is used to configure action filtering. By default this is set to ''any'', which means the action will fire on any selection. To enable action filtering:

	# Change the ''On selection of'' preference to ''specific''.		# Change the ''On selection of'' preference to ''specific''.
			# Click the ''Filter'' button to manage the filter conditions. Using the (action) Filter Editor is just as with the Icon, Color, and Status Shape filters. Build out one or more rules that will determine whether the action will fire.

	~~[[File:appboard-2~~.~~4-widget-~~action~~-filtering~~.~~png\|frame\|center\|Action filtering enabled]]~~		If multiple actions need to fire using the same conditions it can become cumbersome to set up action filters on each action. Instead, use ''Bundled Actions''. That way just the bundle action itself needs to have an action filter configured and all actions within the bundle will fire.

imported>Jason.nicholls: /* Action Filtering */

2014-09-10T17:16:51Z

Action Filtering

← Older revision		Revision as of 17:16, 10 September 2014
Line 118:		Line 118:
	# Change the ''On selection of'' preference to ''specific''.		# Change the ''On selection of'' preference to ''specific''.

	[[File:appboard-2.4-widget-action-filtering.png\|frame\|Action filtering enabled]]		[[File:appboard-2.4-widget-action-filtering.png\|frame\|center\|Action filtering enabled]]

imported>Jason.nicholls: /* Action Filtering */

2014-09-10T17:16:39Z

Action Filtering

← Older revision		Revision as of 17:16, 10 September 2014
Line 110:		Line 110:

	=== Action Filtering ===		=== Action Filtering ===
			Not only does clicking or hovering on something allow you to perform actions in context, but the context can also be used to determine what actions to fire. This provides a powerful mechanism to do different things depending on what the user has selected.

			For example, imagine a map showing both data center locations and office locations represented with differing icons. The data collection driving the map would need to include the information about what type of location each point is and this could be used to trigger one set of actions when clicking on a data center, versus a different set of actions when clicking on an office location.

			The line below the action name that begins with ''On selection of ...'' is used to configure action filtering. By default this is set to ''any'', which means the action will fire on any selection. To enable action filtering:

			# Change the ''On selection of'' preference to ''specific''.

			[[File:appboard-2.4-widget-action-filtering.png\|frame\|Action filtering enabled]]

imported>Jason.nicholls: /* Managing Actions */

2014-09-10T17:08:27Z

Managing Actions

← Older revision		Revision as of 17:08, 10 September 2014
Line 103:		Line 103:
	* use the ''Add Action'' button to add a new action		* use the ''Add Action'' button to add a new action
	* edit action configuration for existing actions		* edit action configuration for existing actions
			** For details on configuring individual actions refer to the tables above.
			** For details on configuring action filtering see the section below.
	* delete an existing action using the red X icon associated with that action.		* delete an existing action using the red X icon associated with that action.

	[[File:appboard-2.4-widget-actions.png\|frame\|center\|Widget Actions configuration dialog]]		[[File:appboard-2.4-widget-actions.png\|frame\|center\|Widget Actions configuration dialog]]

			=== Action Filtering ===