Appboard/2.4/builder/widgets/actions/launch url - Revision history

imported>Cmace: action filtering based on data source, not data collection

2014-05-01T18:31:43Z

action filtering based on data source, not data collection

← Older revision		Revision as of 18:31, 1 May 2014
Line 23:		Line 23:
	### Click <b>Add Rule</b> to create one or more rules that indicate what data should trigger the Action, when selected.		### Click <b>Add Rule</b> to create one or more rules that indicate what data should trigger the Action, when selected.
	### Click <b>Close</b> to save the Filter settings.		### Click <b>Close</b> to save the Filter settings.
	## Select the Data ~~Collection~~ name. When the Widget is run, selection of data in this Data ~~Collection~~ will trigger the Action.		## Select the Data Source name. When the Widget is run, selection of data in this Data Source will trigger the Action.
	# Under <b>Target</b>, select one of the targeting options:		# Under <b>Target</b>, select one of the targeting options:
	#* <b>New Window</b>: The URL will be launched in a new browser window, independent of AppBoard.		#* <b>New Window</b>: The URL will be launched in a new browser window, independent of AppBoard.

imported>Jason.nicholls at 08:54, 14 December 2013

2013-12-14T08:54:05Z

← Older revision		Revision as of 08:54, 14 December 2013
Line 1:		Line 1:
	{{DISPLAYTITLE:~~AppBoard~~ Launch URL ~~Action~~}}		{{DISPLAYTITLE:Launch URL}}
			[[Category:AppBoard 2.4]]
	The "Launch URL" Action loads and displays a pre-configured piece of web content. You can launch the content in the current Widget, in a new window, or in any AppBoard Web Widget.		The "Launch URL" Action loads and displays a pre-configured piece of web content. You can launch the content in the current Widget, in a new window, or in any AppBoard Web Widget.

imported>Jason.nicholls: /* Sample Use Cases */

2013-09-18T04:19:57Z

Sample Use Cases

← Older revision		Revision as of 04:19, 18 September 2013
Line 53:		Line 53:

	[[Image:LaunchURLExampleConfiguration.png\|thumb\|center\|700px\|Configuration of the Example Launch URL Action]]		[[Image:LaunchURLExampleConfiguration.png\|thumb\|center\|700px\|Configuration of the Example Launch URL Action]]

			=== Launch enPortal Channel ===

			The Launch URL action can be used to launch enPortal channels in-context and/or to provide context to the channel based on what was clicked.

			For example the enPortal PIM for IBM Tivoli Network Manager provides a channel to display a network topology. This channel can accept a seed device IP address.

			The following screenshot shows a drill-down child board where both the topology view and list of events are proxied PIM content from Tivoli applications with context passed in by the Launch URL action.

			[[File:appboard-2.4-launch-url-topology.png\|750px\|thumb]]

			For more information on using enPortal proxied content please refer to the main [[appboard/2.4/builder/widgets/web_page\|Web Page Widget]] documentation.


	=== Execute Javascript ===		=== Execute Javascript ===

imported>Jason.nicholls: /* Sample Use Cases */

2013-09-18T04:02:14Z

Sample Use Cases

← Older revision		Revision as of 04:02, 18 September 2013
Line 59:		Line 59:

	<pre>javascript:alert('${CommandName}');void(0)</pre>		<pre>javascript:alert('${CommandName}');void(0)</pre>


	The javascript itself can have multiple statements semi-colon separated, blocks, but must always finish in <tt>void(0)</tt>.		The javascript itself can have multiple statements semi-colon separated, blocks, but must always finish in <tt>void(0)</tt>.

			As an exercise we can have javascript open a new window with the "CommandHelpURL" as in the previous example by setting the ''URL'' field to:

			<pre>javascript:window.open('${CommandHelpURL}','targetName');void(0)</pre>

	== Launching File-Based URLs ==		== Launching File-Based URLs ==

	In some cases, AppBoard can be configured to directly access files on a server through a URL reference. It is possible to represent the paths of local or network files using various forms of URL syntax. Although this can be done, the administrator should be careful to test the file access under all scenarios where AppBoard may be deployed. There are security restrictions that apply to any browser plug-in, and what is accessible depends on the security policy of the browser and the OS where the files are hosted. URLs that work in one environment may not work in another. In some cases, error messages may be displayed back to the user, due to the browser attempting to access a file resource in AppBoard that is not permitted by the network security model.		In some cases, AppBoard can be configured to directly access files on a server through a URL reference. It is possible to represent the paths of local or network files using various forms of URL syntax. Although this can be done, the administrator should be careful to test the file access under all scenarios where AppBoard may be deployed. There are security restrictions that apply to any browser plug-in, and what is accessible depends on the security policy of the browser and the OS where the files are hosted. URLs that work in one environment may not work in another. In some cases, error messages may be displayed back to the user, due to the browser attempting to access a file resource in AppBoard that is not permitted by the network security model.

imported>Jason.nicholls: /* Execute Javascript */

2013-09-18T03:58:20Z

Execute Javascript

← Older revision		Revision as of 03:58, 18 September 2013
Line 56:		Line 56:
	=== Execute Javascript ===		=== Execute Javascript ===

	While the Launch URL action is intended to do just that, it is also possible to execute javascript. For example to show a javascript alert showing "CommandName" (following on from previous example), then configure ''Target'' to "This Window" and the the URL field to:		While the Launch URL action is intended to do just that, it is also possible to execute javascript. For example to show a javascript alert showing "CommandName" (following on from previous example), then configure ''Target'' to "This Window" and the the ''URL'' field to:

	<pre>javascript:alert('${CommandName}');void(0)</pre>		<pre>javascript:alert('${CommandName}');void(0)</pre>

			The javascript itself can have multiple statements semi-colon separated, blocks, but must always finish in <tt>void(0)</tt>.

	== Launching File-Based URLs ==		== Launching File-Based URLs ==

	In some cases, AppBoard can be configured to directly access files on a server through a URL reference. It is possible to represent the paths of local or network files using various forms of URL syntax. Although this can be done, the administrator should be careful to test the file access under all scenarios where AppBoard may be deployed. There are security restrictions that apply to any browser plug-in, and what is accessible depends on the security policy of the browser and the OS where the files are hosted. URLs that work in one environment may not work in another. In some cases, error messages may be displayed back to the user, due to the browser attempting to access a file resource in AppBoard that is not permitted by the network security model.		In some cases, AppBoard can be configured to directly access files on a server through a URL reference. It is possible to represent the paths of local or network files using various forms of URL syntax. Although this can be done, the administrator should be careful to test the file access under all scenarios where AppBoard may be deployed. There are security restrictions that apply to any browser plug-in, and what is accessible depends on the security policy of the browser and the OS where the files are hosted. URLs that work in one environment may not work in another. In some cases, error messages may be displayed back to the user, due to the browser attempting to access a file resource in AppBoard that is not permitted by the network security model.

imported>Jason.nicholls: /* Sample Use Cases */

2013-09-18T03:54:57Z

Sample Use Cases

← Older revision		Revision as of 03:54, 18 September 2013
Line 53:		Line 53:

	[[Image:LaunchURLExampleConfiguration.png\|thumb\|center\|700px\|Configuration of the Example Launch URL Action]]		[[Image:LaunchURLExampleConfiguration.png\|thumb\|center\|700px\|Configuration of the Example Launch URL Action]]

			=== Execute Javascript ===

			While the Launch URL action is intended to do just that, it is also possible to execute javascript. For example to show a javascript alert showing "CommandName" (following on from previous example), then configure ''Target'' to "This Window" and the the URL field to:

			<pre>javascript:alert('${CommandName}');void(0)</pre>

	== Launching File-Based URLs ==		== Launching File-Based URLs ==

	In some cases, AppBoard can be configured to directly access files on a server through a URL reference. It is possible to represent the paths of local or network files using various forms of URL syntax. Although this can be done, the administrator should be careful to test the file access under all scenarios where AppBoard may be deployed. There are security restrictions that apply to any browser plug-in, and what is accessible depends on the security policy of the browser and the OS where the files are hosted. URLs that work in one environment may not work in another. In some cases, error messages may be displayed back to the user, due to the browser attempting to access a file resource in AppBoard that is not permitted by the network security model.		In some cases, AppBoard can be configured to directly access files on a server through a URL reference. It is possible to represent the paths of local or network files using various forms of URL syntax. Although this can be done, the administrator should be careful to test the file access under all scenarios where AppBoard may be deployed. There are security restrictions that apply to any browser plug-in, and what is accessible depends on the security policy of the browser and the OS where the files are hosted. URLs that work in one environment may not work in another. In some cases, error messages may be displayed back to the user, due to the browser attempting to access a file resource in AppBoard that is not permitted by the network security model.

imported>Jason.nicholls: /* Launch Help URLs in a New Window */

2013-09-18T03:46:25Z

Launch Help URLs in a New Window

← Older revision		Revision as of 03:46, 18 September 2013
Line 42:		Line 42:

	Perform the following steps to configure the Launch URL Action:		Perform the following steps to configure the Launch URL Action:


	# Log in to AppBoard Builder as administrator.		# Log in to AppBoard Builder as administrator.
Line 52:		Line 51:
	# Click <b>Finish</b>.		# Click <b>Finish</b>.
	# In the Table Widget display, click a row in the table. A new window is launched with the URL from the selected row.		# In the Table Widget display, click a row in the table. A new window is launched with the URL from the selected row.


	[[Image:LaunchURLExampleConfiguration.png\|thumb\|center\|700px\|Configuration of the Example Launch URL Action]]		[[Image:LaunchURLExampleConfiguration.png\|thumb\|center\|700px\|Configuration of the Example Launch URL Action]]

imported>Jason.nicholls: /* Sample Use Cases */

2013-09-18T03:45:19Z

Sample Use Cases

← Older revision		Revision as of 03:45, 18 September 2013
Line 32:		Line 32:

	== Sample Use Cases ==		== Sample Use Cases ==

	~~===Launch a Contextual Map in Another Widget===~~


	Suppose you have a Table Widget with data related to a geographical region; each row of the table represents a local area in the region. Next to the table is a Map Widget. When the User clicks on a row in the table, you want to pass that location in to the Map Widget so that the selected local area will be displayed on the map. For instructions on configuring this example, see [[launch_enPortal_channel\|how to launch a contextual map Channel]].


	===Launch Help URLs in a New Window===		===Launch Help URLs in a New Window===

			Suppose you have a table that lists web pages that provide additional information on a topic. The fields in the table are "CommandName" and "CommandHelpURL", as shown in the following image:
	~~As another example, suppose~~ you have a table that lists web pages that provide additional information on a topic. The fields in the table are "CommandName" and "CommandHelpURL", as shown in the following image:


Line 62:		Line 55:

	[[Image:LaunchURLExampleConfiguration.png\|thumb\|center\|700px\|Configuration of the Example Launch URL Action]]		[[Image:LaunchURLExampleConfiguration.png\|thumb\|center\|700px\|Configuration of the Example Launch URL Action]]


	== Launching File-Based URLs ==		== Launching File-Based URLs ==

	In some cases, AppBoard can be configured to directly access files on a server through a URL reference. It is possible to represent the paths of local or network files using various forms of URL syntax. Although this can be done, the administrator should be careful to test the file access under all scenarios where AppBoard may be deployed. There are security restrictions that apply to any browser plug-in, and what is accessible depends on the security policy of the browser and the OS where the files are hosted. URLs that work in one environment may not work in another. In some cases, error messages may be displayed back to the user, due to the browser attempting to access a file resource in AppBoard that is not permitted by the network security model.		In some cases, AppBoard can be configured to directly access files on a server through a URL reference. It is possible to represent the paths of local or network files using various forms of URL syntax. Although this can be done, the administrator should be careful to test the file access under all scenarios where AppBoard may be deployed. There are security restrictions that apply to any browser plug-in, and what is accessible depends on the security policy of the browser and the OS where the files are hosted. URLs that work in one environment may not work in another. In some cases, error messages may be displayed back to the user, due to the browser attempting to access a file resource in AppBoard that is not permitted by the network security model.

imported>Mike.berman at 00:07, 5 September 2013

2013-09-05T00:07:01Z

← Older revision		Revision as of 00:07, 5 September 2013
Line 16:		Line 16:

	# Follow the instructions above to create the basic "Launch URL" Action.		# Follow the instructions above to create the basic "Launch URL" Action.
	# <b>Name</b>: Enter a name for this Action. For convenience, a default name is provided ~~that you may use~~. The Name is not used anywhere else in AppBoard, and only displayed on this configuration page.		# <b>Name</b>: Enter a name for this Action. For convenience, a default name is provided. The Name is not used anywhere else in AppBoard, and only displayed on this configuration page.
	# <b>On selection of</b>:		# <b>On selection of</b>:
	## Select "any" or "specific" for the type of data selection by the User that will trigger the Action. When selecting "specific", perform the following additional steps:		## Select "any" or "specific" for the type of data selection by the User that will trigger the Action. When selecting "specific", perform the following additional steps:

imported>Mike.berman at 20:57, 4 September 2013

2013-09-04T20:57:05Z

← Older revision		Revision as of 20:57, 4 September 2013
Line 22:		Line 22:
	### Click <b>Add Rule</b> to create one or more rules that indicate what data should trigger the Action, when selected.		### Click <b>Add Rule</b> to create one or more rules that indicate what data should trigger the Action, when selected.
	### Click <b>Close</b> to save the Filter settings.		### Click <b>Close</b> to save the Filter settings.
			## Select the Data Collection name. When the Widget is run, selection of data in this Data Collection will trigger the Action.
	# Under <b>Target</b>, select one of the targeting options:		# Under <b>Target</b>, select one of the targeting options:
	#* <b>New Window</b>: The URL will be launched in a new browser window, independent of AppBoard.		#* <b>New Window</b>: The URL will be launched in a new browser window, independent of AppBoard.