Difference between revisions of "WID/HIW"

Revision as of 20:05, January 6, 2021

Learn how Genesys Widgets works.

What Widgets does[edit source]

Modern contact centers need more than voice channels to keep up with their customers. Whether it's a chat session or screen sharing—or even if it's just a matter of scheduling a callback—digital channels and other modern customer support functions are a necessity for providing a unified customer journey.

Genesys Widgets is a set of APIs that provides specific types of user interface elements—normally referred to as widgets—and the services to drive them, enabling you to enhance your website with chat or callback, or your own customized contact center functionality.

How Widgets works[edit source]

Genesys Widgets is built on top of the CXBus messaging bus. CXBus uses the publish–subscribe pattern to facilitate communication between the Widgets components, all of which are plugins that can both publish events on the bus and subscribe to the events they are interested in.

With the help of the Widgets-Core plugins, CXBus makes it possible to combine the logic implemented by user interface plugins, service plugins, and utility plugins into cohesive products that can provide chat sessions, schedule callbacks, and so on.

CXBus

This messaging bus allows you to create your own plugins with a namespaced API consisting of commands, events, and a data model. CXBus also loads your plugins and resources—either manually or automatically. Every other component in Genesys Widgets is a CXBus plugin. In addition to creating your own plugins for use on the bus, you can use CXBus to manually call plugin commands, subscribe to events, or read data.

Widgets-Core

These plugins make up the Widgets framework. All of the other plugins depend on them:

App (main parent controller for Genesys Widgets)
Common
Overlay
Toaster
WindowManager

Service plugins

These handle the network connections to Genesys channels. UI plugins use their services to communicate with the server indirectly. They can also be used independently to develop your own UI plugins.

UI plugins

Also known as Widgets:

Bridge plugins

The Engage plugin interfaces Genesys Widgets with other products.

Modules

These are standalone bits of code or data that can be loaded-into plugins directly. WebChatService has both a version 1 and a version 2 controller. The proper controller module is loaded at runtime, based on your configuration options.

Related stuff

How to use Genesys Widgets

Read the Get started article.

@@ Line 2: / Line 2: @@
 |DisplayName=How Widgets works
 |TocName=How Widgets works
-|Context=Genesys Widgets relies on certain technologies in order to function. This article describes what is required for widgets to work.
+|Context=Learn how Genesys Widgets works.
 |ComingSoon=No
 |Platform=GenesysEngage-cloud
@@ Line 13: / Line 13: @@
 [[File:Webchat main new.jpg|750x750px]]
-|featureoverview=Genesys Widgets is built on top of the {{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=GWCBusAPIOverview|display text=CXBus}} messaging bus. CXBus uses the [https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern publish–subscribe pattern] to facilitate communication between the Widgets components, all of which are ''plugins'' that can both ''publish'' events on the bus and ''subscribe'' to the events they are interested in.
+|featureoverview=Genesys Widgets is built on top of the {{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=GWCBusAPIOverview|display text=CXBus}} messaging bus. CXBus uses the {{#Widget:ExtLink|link=https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern|displaytext=publish–subscribe pattern}} to facilitate communication between the Widgets components, all of which are ''plugins'' that can both ''publish'' events on the bus and ''subscribe'' to the events they are interested in.
 With the help of the Widgets-Core plugins, CXBus makes it possible to combine the logic implemented by user interface plugins, service plugins, and utility plugins into cohesive products that can provide chat sessions, schedule callbacks, and so on.
@@ Line 20: / Line 20: @@
 ===CXBus===
 This messaging bus allows you to create your own plugins with a namespaced API consisting of commands, events, and a data model. CXBus also loads your plugins and resources—either manually or automatically. Every other component in Genesys Widgets is a CXBus plugin. In addition to creating your own plugins for use on the bus, you can use CXBus to manually call plugin commands, subscribe to events, or read data.
-===Widgets core===
+===Widgets-Core===
 These plugins make up the Widgets framework. All of the other plugins depend on them:
@@ Line 32: / Line 32: @@
 These handle the network connections to Genesys channels. UI plugins use their services to communicate with the server indirectly. They can also be used independently to develop your own UI plugins.
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=CallbackService-combined|display text=Callback Service}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=CallbackService-combined|display text=CallbackService}}
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=StatsService-combined|display text=Stats Service}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=StatsService-combined|display text=StatsService}}
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChatService-combined|display text=Web Chat Service}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChatService-combined|display text=WebChatService}}
 ===UI plugins===
@@ Line 41: / Line 41: @@
 *{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=Calendar-combined|display text=Calendar}}
 *{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=Callback-combined|display text=Callback}}
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=CallUs-combined|display text=Call Us}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=CallUs-combined|display text=CallUs}}
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=ChannelSelector-combined|display text=Channel Selector}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=ChannelSelector-combined|display text=ChannelSelector}}
 *{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=Console-combined|display text=Console}}
 *{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=SideBar-combined|display text=SideBar}}
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChat-combined|display text=Web Chat}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChat-combined|display text=WebChat}}
 ===Bridge plugins===
@@ Line 56: / Line 56: @@
 |HIWSectionAlignment=Vertical
 |HIWSectionGif=No
-|HIWSectionAnchor=related
 |HIWSectionText=*{{Link-AnywhereElse|product=WID|version=Current|manual=Developer|display text=Widgets Developer's Guide}}
 *{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|display text=Widgets API Reference}}
@@ Line 64: / Line 63: @@
 |HIWSectionAlignment=Vertical
 |HIWSectionGif=No
-|HIWSectionAnchor=howto
 |HIWSectionText=Read the {{Link-AnywhereElse|product=WID|version=Current|manual=Developer|topic=GWCDeployment|display text=Get started}} article.
 }}
 |advanced=No
 }}