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

imported>Jason.nicholls: /* Overview */

2014-10-24T10:06:03Z

Overview

← Older revision		Revision as of 10:06, 24 October 2014
Line 5:		Line 5:
	''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on the same action filter. The action filter applies to the bundle and all actions within the bundle are run when there is a match. Logically grouping actions into bundles is also useful for widgets that have a lot of actions to keep things organized.		''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on the same action filter. The action filter applies to the bundle and all actions within the bundle are run when there is a match. Logically grouping actions into bundles is also useful for widgets that have a lot of actions to keep things organized.

	Bundling actions together also makes it possible to reuse action configuration on multiple widgets. While this is possible there are some caveats due to actions often being widget specific, data collection specific, or similar which means the actions may not work as expected when ~~firing~~ from the ~~secondary widget~~.		Bundling actions together also makes it possible to reuse action configuration on multiple widgets. While this is possible there are some caveats due to actions often being widget specific, data collection specific, or similar which means the actions may not work as expected when triggered from a different widget to the original.

imported>Jason.nicholls: /* Overview */

2014-10-24T10:05:25Z

Overview

← Older revision		Revision as of 10:05, 24 October 2014
Line 5:		Line 5:
	''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on the same action filter. The action filter applies to the bundle and all actions within the bundle are run when there is a match. Logically grouping actions into bundles is also useful for widgets that have a lot of actions to keep things organized.		''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on the same action filter. The action filter applies to the bundle and all actions within the bundle are run when there is a match. Logically grouping actions into bundles is also useful for widgets that have a lot of actions to keep things organized.

	Bundling actions together also makes it possible to reuse action configuration on ~~another widget~~. While this is possible there are some caveats due to actions often being widget specific, data collection specific, or similar which means the actions may not work as expected when firing from the secondary widget.		Bundling actions together also makes it possible to reuse action configuration on multiple widgets. While this is possible there are some caveats due to actions often being widget specific, data collection specific, or similar which means the actions may not work as expected when firing from the secondary widget.

imported>Jason.nicholls: /* Overview */

2014-10-24T10:04:56Z

Overview

← Older revision		Revision as of 10:04, 24 October 2014
Line 3:		Line 3:
	== Overview ==		== Overview ==

	''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on the same action filter. The action filter applies to the bundle and all actions within the bundle are ~~triggered~~ when there is a match. Logically grouping actions into bundles is also useful for widgets that have a lot of actions to keep things organized.		''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on the same action filter. The action filter applies to the bundle and all actions within the bundle are run when there is a match. Logically grouping actions into bundles is also useful for widgets that have a lot of actions to keep things organized.

	Bundling actions together also makes it possible to reuse action configuration on another widget. While this is possible there are some caveats due to actions often being widget specific, data collection specific, or similar which means the actions may not work as expected when firing from the secondary widget.		Bundling actions together also makes it possible to reuse action configuration on another widget. While this is possible there are some caveats due to actions often being widget specific, data collection specific, or similar which means the actions may not work as expected when firing from the secondary widget.

imported>Jason.nicholls: /* Overview */

2014-10-24T10:04:31Z

Overview

← Older revision		Revision as of 10:04, 24 October 2014
Line 3:		Line 3:
	== Overview ==		== Overview ==

	''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on same action filter. The action filter applies to the bundle and all actions within the bundle are triggered when there is a match. Logically grouping actions into bundles is also useful for widgets that have a lot of actions to keep things organized.		''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on the same action filter. The action filter applies to the bundle and all actions within the bundle are triggered when there is a match. Logically grouping actions into bundles is also useful for widgets that have a lot of actions to keep things organized.

	Bundling actions together also makes it possible to reuse action configuration on another widget. While this is possible there are some caveats due to actions often being widget specific, data collection specific, or similar which means the actions may not work as expected when firing from the secondary widget.		Bundling actions together also makes it possible to reuse action configuration on another widget. While this is possible there are some caveats due to actions often being widget specific, data collection specific, or similar which means the actions may not work as expected when firing from the secondary widget.

imported>Jason.nicholls: /* Configuration */

2014-10-24T10:03:08Z

Configuration

← Older revision		Revision as of 10:03, 24 October 2014
Line 23:		Line 23:
	The screenshot above is from the ''Feature List'' widget in the Welcome content that ships with AppBoard. Most of the actions triggered by clicking a feature are grouped into bundles so this serves as a good example of how to use this feature.		The screenshot above is from the ''Feature List'' widget in the Welcome content that ships with AppBoard. Most of the actions triggered by clicking a feature are grouped into bundles so this serves as a good example of how to use this feature.

	~~When editing~~ an action bundle ~~the interface~~ is very similar to ~~when editing~~ actions.		=== Editing Bundles ===

			Editing an action bundle is very similar to the normal widget actions editor.

	Use the ''Add Action'' button to add actions. Use the red <tt>X</tt> button on each action to remove the action. The main difference is that actions added into an action bundle do not have an action filter. Also make sure to set a unique '''Action Bundle Name''' to avoid confusion in systems with multiple action bundles. The screenshot below shows the bundle configuration from the same example as above.		Use the ''Add Action'' button to add actions. Use the red <tt>X</tt> button on each action to remove the action. The main difference is that actions added into an action bundle do not have an action filter. Also make sure to set a unique '''Action Bundle Name''' to avoid confusion in systems with multiple action bundles. The screenshot below shows the bundle configuration from the same example as above.

	[[File:appboard-2.5-bundled-actions-editing.png\|frame\|center\|example editing an action bundle]]		[[File:appboard-2.5-bundled-actions-editing.png\|frame\|center\|example editing an action bundle]]

imported>Jason.nicholls: /* Configuration */

2014-10-24T10:01:02Z

Configuration

← Older revision		Revision as of 10:01, 24 October 2014
Line 21:		Line 21:
	* '''Select Action Bundle''': shows the currently selected bundle. Use the ''Add'' button to create a new action bundle, or the ''Edit'' button to edit the currently selected bundle.		* '''Select Action Bundle''': shows the currently selected bundle. Use the ''Add'' button to create a new action bundle, or the ''Edit'' button to edit the currently selected bundle.

	The screenshot above is from the ''Feature List'' widget in the Welcome ~~archive~~ that ships with AppBoard. Most of the actions triggered by clicking a feature are grouped into bundles so this serves as a good example of how to use this feature.		The screenshot above is from the ''Feature List'' widget in the Welcome content that ships with AppBoard. Most of the actions triggered by clicking a feature are grouped into bundles so this serves as a good example of how to use this feature.

	When editing an action bundle the interface is very similar to when editing actions.		When editing an action bundle the interface is very similar to when editing actions.

imported>Jason.nicholls: /* Configuration */

2014-10-24T10:00:35Z

Configuration

← Older revision		Revision as of 10:00, 24 October 2014
Line 13:		Line 13:

	[[File:appboard-2.5-bundled-actions.png\|frame\|center\|example Bundled Action configuration]]		[[File:appboard-2.5-bundled-actions.png\|frame\|center\|example Bundled Action configuration]]


	Refer to [[appboard/2.5/builder/widgets/actions#Managing_Actions\|Managing Actions]] for general information on adding / editing / deleting actions.		Refer to [[appboard/2.5/builder/widgets/actions#Managing_Actions\|Managing Actions]] for general information on adding / editing / deleting actions.
Line 26:		Line 27:
	Use the ''Add Action'' button to add actions. Use the red <tt>X</tt> button on each action to remove the action. The main difference is that actions added into an action bundle do not have an action filter. Also make sure to set a unique '''Action Bundle Name''' to avoid confusion in systems with multiple action bundles. The screenshot below shows the bundle configuration from the same example as above.		Use the ''Add Action'' button to add actions. Use the red <tt>X</tt> button on each action to remove the action. The main difference is that actions added into an action bundle do not have an action filter. Also make sure to set a unique '''Action Bundle Name''' to avoid confusion in systems with multiple action bundles. The screenshot below shows the bundle configuration from the same example as above.

	[[File:appboard-2.5-~~bundle~~-actions-editing.png\|frame\|center\|example editing an action bundle]]		[[File:appboard-2.5-bundled-actions-editing.png\|frame\|center\|example editing an action bundle]]

imported>Jason.nicholls: /* Configuration */

2014-10-24T10:00:04Z

Configuration

← Older revision		Revision as of 10:00, 24 October 2014
Line 13:		Line 13:

	[[File:appboard-2.5-bundled-actions.png\|frame\|center\|example Bundled Action configuration]]		[[File:appboard-2.5-bundled-actions.png\|frame\|center\|example Bundled Action configuration]]

			Refer to [[appboard/2.5/builder/widgets/actions#Managing_Actions\|Managing Actions]] for general information on adding / editing / deleting actions.

			The following settings are available:

			* '''Select Action Bundle''': shows the currently selected bundle. Use the ''Add'' button to create a new action bundle, or the ''Edit'' button to edit the currently selected bundle.

			The screenshot above is from the ''Feature List'' widget in the Welcome archive that ships with AppBoard. Most of the actions triggered by clicking a feature are grouped into bundles so this serves as a good example of how to use this feature.

			When editing an action bundle the interface is very similar to when editing actions.

			Use the ''Add Action'' button to add actions. Use the red <tt>X</tt> button on each action to remove the action. The main difference is that actions added into an action bundle do not have an action filter. Also make sure to set a unique '''Action Bundle Name''' to avoid confusion in systems with multiple action bundles. The screenshot below shows the bundle configuration from the same example as above.

			[[File:appboard-2.5-bundle-actions-editing.png\|frame\|center\|example editing an action bundle]]

imported>Jason.nicholls at 09:47, 24 October 2014

2014-10-24T09:47:34Z

@@ Line 3: / Line 3: @@
 == Overview ==
-''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on same action filter. The action filter applies to the bundle and all actions within the bundle are triggered when there is a match. Logically grouping actions is also useful for widgets that have a lot of actions to keep things organized.
+''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on same action filter. The action filter applies to the bundle and all actions within the bundle are triggered when there is a match. Logically grouping actions into bundles is also useful for widgets that have a lot of actions to keep things organized.
 Bundling actions together also makes it possible to reuse action configuration on another widget. While this is possible there are some caveats due to actions often being widget specific, data collection specific, or similar which means the actions may not work as expected when firing from the secondary widget.
 {{Warning|It is '''not''' recommended to reuse action bundles on different widgets. Instead copy the widget which will make a complete copy of the actions, including the action bundle. Ensure to edit the new widget and rename the action bundle as it will have the same name as the original which can be confusing.}}
+[[File:appboard-2.5-bundled-actions.png|frame|center|example Bundled Action configuration]]

imported>Jason.nicholls: /* Overview */

2014-10-24T09:36:58Z

Overview

← Older revision		Revision as of 09:36, 24 October 2014
Line 2:		Line 2:
	[[Category:AppBoard 2.5]]		[[Category:AppBoard 2.5]]
	== Overview ==		== Overview ==

			''Bundled Actions'' is a grouping mechanism so that multiple actions can be triggered based on same action filter. The action filter applies to the bundle and all actions within the bundle are triggered when there is a match. Logically grouping actions is also useful for widgets that have a lot of actions to keep things organized.

			Bundling actions together also makes it possible to reuse action configuration on another widget. While this is possible there are some caveats due to actions often being widget specific, data collection specific, or similar which means the actions may not work as expected when firing from the secondary widget.

			{{Warning\|It is '''not''' recommended to reuse action bundles on different widgets. Instead copy the widget which will make a complete copy of the actions, including the action bundle. Ensure to edit the new widget and rename the action bundle as it will have the same name as the original which can be confusing.}}




	The ''Bundled Actions'' Action executes multiple Actions based on a single request from a User.		The ''Bundled Actions'' Action executes multiple Actions based on a single request from a User.
Line 7:		Line 16:

	Because Actions are tied directly to the type of data from the event, Bundled Actions are also tied to a specific type of data. When a Bundle is created, it is specific to a data type. When you add another "Bundle Action" instance, it will only be available for Actions using the same type of data.		Because Actions are tied directly to the type of data from the event, Bundled Actions are also tied to a specific type of data. When a Bundle is created, it is specific to a data type. When you add another "Bundle Action" instance, it will only be available for Actions using the same type of data.


	== How To Add Actions To A Widget ==		== How To Add Actions To A Widget ==