Difference between revisions of "WID/Current/SDK/Console-combined"

From Genesys Documentation
Jump to: navigation, search
(Published)
Line 2: Line 2:
 
|Standalone=No
 
|Standalone=No
 
|DisplayName=Console
 
|DisplayName=Console
|Role=Developer
 
 
|TocName=Console
 
|TocName=Console
 +
|Context=Learn how to debug commands and events on the widget bus.
 +
|ComingSoon=No
 
|Platform=PureEngage
 
|Platform=PureEngage
|ComingSoon=No
+
|Role=Developer
|Context=Learn how to debug commands and events on the widget bus.
 
 
|Section={{Section
 
|Section={{Section
 
|sectionHeading=Overview
 
|sectionHeading=Overview
|Standalone=No
 
|ComingSoon=No
 
 
|alignment=Vertical
 
|alignment=Vertical
 
|structuredtext=Use the Console Widget to debug commands and events on the widget bus. You can use dynamically populated lists to test, debug, or demo all of the commands. You can also create event watchlists that alert you when an event has fired.  
 
|structuredtext=Use the Console Widget to debug commands and events on the widget bus. You can use dynamically populated lists to test, debug, or demo all of the commands. You can also create event watchlists that alert you when an event has fired.  
Line 19: Line 17:
 
===Usage===
 
===Usage===
 
Launch WebChat manually by using the following methods:
 
Launch WebChat manually by using the following methods:
* Call the '''Console.open''' command
+
 
* Configure the settings to show Console when the browser window is opened.
+
*Call the '''Console.open''' command
* Create your own custom button or link to open Console (using the "Console.open" command)
+
*Configure the settings to show Console when the browser window is opened.
|advanced=No
+
*Create your own custom button or link to open Console (using the "Console.open" command)
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
 
|sectionHeading=Configuration
 
|sectionHeading=Configuration
|Standalone=No
 
|ComingSoon=No
 
 
|alignment=Vertical
 
|alignment=Vertical
 
|structuredtext====Description===
 
|structuredtext====Description===
Line 49: Line 45:
 
{{!}}{{!}}open
 
{{!}}{{!}}open
 
{{!}}{{!}}boolean
 
{{!}}{{!}}boolean
{{!}}{{!}}Set to true for console to open at start.
+
{{!}}{{!}}Set to <code>true</code> for console to open at start.
 
{{!}}{{!}}false
 
{{!}}{{!}}false
 
{{!}}{{!}}false
 
{{!}}{{!}}false
 
{{!}}}
 
{{!}}}
|advanced=No
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
 
|sectionHeading=Localization
 
|sectionHeading=Localization
|Standalone=No
 
|ComingSoon=No
 
 
|alignment=Vertical
 
|alignment=Vertical
|structuredtext=Console doesn't have any localization options.
+
|structuredtext={{NoteFormat|For information on how to set up localization, please refer to {{Link-AnywhereElse|product=WID|version=Current|manual=Developer|topic=GWCInternat}}.|1}}
|advanced=No
+
==Strings==
 +
<source lang="javascript">{
 +
"ConsoleTitle": "CXBus Console",
 +
"Commands": "Commands",
 +
"Plugin": "Plugin",
 +
"ConsoleErrorButton": "OK",
 +
"Execute": "Execute",
 +
"Event": "Event",
 +
"SubscribeTo": "Subscribe to",
 +
"Unsubscribe": "Unsubscribe",
 +
"ReturnData": "Return Data",
 +
"EventsSubscriber": "Events Subscriber",
 +
"Watch": "Watch",
 +
"pluginNameEvent": "PluginName.Event",
 +
"ClearAll": "Clear All",
 +
"OptionsSample": "JSON Formatted Options {'option': value}"
 +
}</source><br />
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
 
|sectionHeading=API Commands
 
|sectionHeading=API Commands
|Standalone=No
 
|ComingSoon=No
 
 
|alignment=Vertical
 
|alignment=Vertical
 
|structuredtext=Once you've registered your plugin on the bus, you can call commands on other registered plugins. Here's how to use the global bus object to register a new plugin on the bus.
 
|structuredtext=Once you've registered your plugin on the bus, you can call commands on other registered plugins. Here's how to use the global bus object to register a new plugin on the bus.
Line 72: Line 79:
 
{{NoteFormat|The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see {{Link-SomewhereInThisManual|topic=GWCBusExtensions|anchor=top|display text=Widgets Extensions}} for more information about extending Genesys Widgets.|1}}
 
{{NoteFormat|The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see {{Link-SomewhereInThisManual|topic=GWCBusExtensions|anchor=top|display text=Widgets Extensions}} for more information about extending Genesys Widgets.|1}}
  
<source lang='javascript'>var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');
+
<source lang="javascript">var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');
  
 
oMyPlugin.command('Console.open');</source>
 
oMyPlugin.command('Console.open');</source>
Line 78: Line 85:
 
Opens the Console UI.
 
Opens the Console UI.
 
====Example====
 
====Example====
<source lang='javascript'>
+
<source lang="javascript">
 
oMyPlugin.command('Console.open').done(function(e){
 
oMyPlugin.command('Console.open').done(function(e){
  
Line 110: Line 117:
 
Closes the Console UI.
 
Closes the Console UI.
 
====Example====
 
====Example====
<source lang='javascript'>
+
<source lang="javascript">
 
oMyPlugin.command('Console.close').done(function(e){
 
oMyPlugin.command('Console.close').done(function(e){
  
Line 142: Line 149:
 
Modifies the Console configuration options. See the Console configuration page.
 
Modifies the Console configuration options. See the Console configuration page.
 
====Example====
 
====Example====
<source lang='javascript'>
+
<source lang="javascript">
 
oMyPlugin.command('Console.configure', {
 
oMyPlugin.command('Console.configure', {
  
Line 187: Line 194:
 
{{!}}{{!}}'Invalid Configuration'
 
{{!}}{{!}}'Invalid Configuration'
 
{{!}}}
 
{{!}}}
|advanced=No
 
 
|Status=No
 
|Status=No
 
}}{{Section
 
}}{{Section
 
|sectionHeading=API Events
 
|sectionHeading=API Events
|Standalone=No
 
|ComingSoon=No
 
 
|alignment=Vertical
 
|alignment=Vertical
 
|structuredtext=Once you've registered your plugin on the bus, you can subscribe to and listen for published events. Here's how to use the global bus object to register a new plugin on the bus.
 
|structuredtext=Once you've registered your plugin on the bus, you can subscribe to and listen for published events. Here's how to use the global bus object to register a new plugin on the bus.
Line 198: Line 202:
 
{{NoteFormat|The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see {{Link-SomewhereInThisManual|topic=GWCBusExtensions|anchor=top|display text=Widgets Extensions}} for more information about extending Genesys Widgets.|1}}
 
{{NoteFormat|The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see {{Link-SomewhereInThisManual|topic=GWCBusExtensions|anchor=top|display text=Widgets Extensions}} for more information about extending Genesys Widgets.|1}}
  
<source lang='javascript'>var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');
+
<source lang="javascript">var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');
  
 
oMyPlugin.subscribe('Console.ready', function(e){});</source>
 
oMyPlugin.subscribe('Console.ready', function(e){});</source>
Line 219: Line 223:
 
{{!}}{{!}}n/a
 
{{!}}{{!}}n/a
 
{{!}}}
 
{{!}}}
|advanced=No
 
 
|Status=No
 
|Status=No
 
}}
 
}}
 
}}
 
}}

Revision as of 20:42, January 27, 2020

This topic is part of the manual Widgets API Reference for version Current of Widgets.

Learn how to debug commands and events on the widget bus.

Related documentation:

Overview

Use the Console Widget to debug commands and events on the widget bus. You can use dynamically populated lists to test, debug, or demo all of the commands. You can also create event watchlists that alert you when an event has fired.

Console example

Console provides an easy-to-use interface for debugging the widget bus that compliments the standard command line methods. You can drag and drop the console anywhere on your screen and when you refresh the page or move to another one, Console reappears right where you left it, as you left it. It is a great tool for getting to know the widget bus, the API for each widget, and debugging issues.

Usage

Launch WebChat manually by using the following methods:

  • Call the Console.open command
  • Configure the settings to show Console when the browser window is opened.
  • Create your own custom button or link to open Console (using the "Console.open" command)

Configuration

Description

Console option to open on initial loading.

Example

window._genesys.widgets.console = {open: true};

Options

Name Type Description Default Required
open boolean Set to true for console to open at start. false false

Localization

Important
For information on how to set up localization, please refer to Localize widgets and services.

Strings

{
	"ConsoleTitle": "CXBus Console",
	"Commands": "Commands",
	"Plugin": "Plugin",
	"ConsoleErrorButton": "OK",
	"Execute": "Execute",
	"Event": "Event",
	"SubscribeTo": "Subscribe to",
	"Unsubscribe": "Unsubscribe",
	"ReturnData": "Return Data",
	"EventsSubscriber": "Events Subscriber",
	"Watch": "Watch",
	"pluginNameEvent": "PluginName.Event",
	"ClearAll": "Clear All",
	"OptionsSample": "JSON Formatted Options {'option': value}"
}

API Commands

Once you've registered your plugin on the bus, you can call commands on other registered plugins. Here's how to use the global bus object to register a new plugin on the bus.

Important
The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see Widgets Extensions for more information about extending Genesys Widgets.
var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');

oMyPlugin.command('Console.open');

open

Opens the Console UI.

Example

oMyPlugin.command('Console.open').done(function(e){

	// Console opened successfully

}).fail(function(e){

	// Console failed to open
});

Resolutions

Status When Returns
resolved When Console is successfully opened n/a
rejected When Console is already open 'Already opened'


close

Closes the Console UI.

Example

oMyPlugin.command('Console.close').done(function(e){

	// Console closed successfully

}).fail(function(e){

	// Console failed to close
});

Resolutions

Status When Returns
resolved When Console successfully closed n/a
rejected When Console is already closed 'Already closed'


configure

Modifies the Console configuration options. See the Console configuration page.

Example

oMyPlugin.command('Console.configure', {

	open: false

}).done(function(e){

	// Console configured successfully

}).fail(function(e){

	// Console failed to configure
});

Options

Option Type Description
open boolean If setting is open: true, the console will automatically be open when widgets is launched and the console is ready.


Resolutions

Status When Returns
resolved When Console configuration is provided n/a
rejected When no configuration provided 'Invalid Configuration'

API Events

Once you've registered your plugin on the bus, you can subscribe to and listen for published events. Here's how to use the global bus object to register a new plugin on the bus.

Important
The global bus object is a debugging tool. When implementing Widgets on your own site, do not use the global bus object to register your custom plugins. Instead, see Widgets Extensions for more information about extending Genesys Widgets.
var oMyPlugin = window._genesys.widgets.bus.registerPlugin('MyPlugin');

oMyPlugin.subscribe('Console.ready', function(e){});
Name Description Data
ready Console is initialized and ready to accept commands. n/a
opened The Console widget has appeared on screen. n/a
closed The Console widget has been removed from the screen. n/a
Retrieved from "https://all.docs.genesys.com/WID/Current/SDK/Console-combined (2025-06-19 17:13:02)"
Comments or questions about this documentation? Contact us for support!