WID/HIW - Revision history

Mwest: Text replacement - "Agent Desktop" to "Agent Workspace"

2022-08-02T18:27:01Z

Text replacement - "Agent Desktop" to "Agent Workspace"

Monique.gionet@genesys.com: Published

2021-09-14T16:13:36Z

Published

Chrissy.forrest@genesys.com: Published

2021-05-10T17:23:06Z

Published

Ed.jamer@genesys.com: Reverted edits by Ed.jamer@genesys.com (talk) to last revision by Chrissyforrest

2021-01-06T20:05:49Z

Reverted edits by Ed.jamer@genesys.com (talk) to last revision by Chrissyforrest

Ed.jamer@genesys.com: Published

2021-01-06T19:36:34Z

Published

Chrissyforrest: Published

2020-10-27T21:17:40Z

Published

Chrissyforrest: Published

2020-09-14T12:32:32Z

Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

2020-07-25T02:38:11Z

Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"

2020-07-15T11:49:20Z

Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Chrissyforrest: Published

2020-07-10T15:56:25Z

Published

@@ Line 49: / Line 49: @@
 *[[PEC-COB|Co-Browse]]
 *[[PEC-Chat|Chat]]
-*[[PEC-AD|Agent Desktop]]
+*[[PEC-AD|Agent Workspace]]
 }}{{HIWSection
 |HIWSectionHeading=How to use Genesys Widgets

@@ Line 14: / Line 14: @@
 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.
-[[File:Webchat main new.jpg|750x750px|link=https://all.docs.genesys.com/File:Webchat_main_new.jpg]]
+[[File:Webchat main new.jpg|750x750px|link=https://all.docs.genesys.com/File:Webchat_main_new.jpg|alt=Web Chat window displaying how to start a chat session.]]
 |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.
-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.[[File:Widgets-architecture.png|center|600x600px|link=https://all.docs.genesys.com/File:Widgets-architecture.png]]
+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.[[File:Widgets-architecture.png|center|600x600px|link=https://all.docs.genesys.com/File:Widgets-architecture.png|Widgets architecture diagram displaying how Widgets is built on top of CX Bus.]]
 |HIWSection={{HIWSection
 |HIWSectionHeading=Widgets behavior
@@ Line 40: / Line 40: @@
 |HIWSectionText=Widgets-specific documentation:
-* {{Link-AnywhereElse|product=WID|version=Current|manual=Developer|display text=Widgets Developer's Guide}}
+*{{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}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|display text=Widgets API Reference}}
 *{{#Widget:ExtLink|link=https://docs.genesys.com/Documentation/PSAAS/Public/RN/GW|displaytext=Genesys Widgets Release Notes}}

@@ Line 1: / Line 1: @@
 {{HIW
-|DisplayName=How Widgets works
+|product=Draft:WID
 |TocName=How Widgets works
-|Context=Learn how Genesys Widgets works.
+|Context=Genesys Widgets relies on certain technologies in order to function. This article describes the requirements for widget implementation.
 |ComingSoon=No
 |Platform=GenesysEngage-cloud
@@ Line 12: / Line 14: @@
 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.
-[[File:Webchat main new.jpg|750x750px]]
+[[File:Webchat main new.jpg|750x750px|link=https://all.docs.genesys.com/File:Webchat_main_new.jpg]]
-|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.
+|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.
-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.
+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.[[File:Widgets-architecture.png|center|600x600px|link=https://all.docs.genesys.com/File:Widgets-architecture.png]]
-[[File:Widgets-architecture.png|center|600x600px]]
+|HIWSection={{HIWSection
-<br />
+|HIWSectionHeading=Widgets behavior
-===CXBus===
+|HIWSectionAlignment=Vertical
-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.
+|HIWSectionGif=No
-===Widgets-Core===
+|HIWSectionAnchor=behavior
-These plugins make up the Widgets framework. All of the other plugins depend on them:
+|HIWSectionText====How widgets behave when jumping from page to page===
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=App-combined|display text=App}} (main parent controller for Genesys Widgets)
+===How session recovery works after closing and opening the browser within the same domain===
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=Common|display text=Common}}
+Genesys Widgets uses session cookies, which persist until you completely exit your browser application. When viewing an active chat session, closing the current window will not eliminate the session cookie, unless the action taken also exited the browser completely.
-===Service plugins===
+If you close the browser window or tab running the chat session, but you do not exit the browser completely, returning to that domain in another window or tab will restore the chat session.
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=CallbackService-combined|display text=CallbackService}}
+===What happens when multiple browser windows are open===
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=StatsService-combined|display text=StatsService}}
+When running multiple tabs from the same domain, the chat session will attempt to restore on each one. Closing one tab will not end the session. All tabs must be closed and the browser exited completely for the session cookies to be eliminated.
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChatService-combined|display text=WebChatService}}
+}}{{HIWSection
 |HIWSectionHeading=Related stuff
 |HIWSectionAlignment=Vertical
 |HIWSectionGif=No
-|HIWSectionText=*{{Link-AnywhereElse|product=WID|version=Current|manual=Developer|display text=Widgets Developer's Guide}}
+|HIWSectionAnchor=related
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|display text=Widgets API Reference}}
+|HIWSectionText=Widgets-specific documentation:
 *{{#Widget:ExtLink|link=https://docs.genesys.com/Documentation/PSAAS/Public/RN/GW|displaytext=Genesys Widgets Release Notes}}
 }}{{HIWSection
 |HIWSectionHeading=How to use Genesys Widgets
 |HIWSectionAlignment=Vertical
 |HIWSectionGif=No
-|HIWSectionText=Read the {{Link-AnywhereElse|product=WID|version=Current|manual=Developer|topic=GWCDeployment|display text=Get started}} article.
+|HIWSectionAnchor=howto
 }}
 }}

@@ 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
 |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
 |HIWSectionText=Read the {{Link-AnywhereElse|product=WID|version=Current|manual=Developer|topic=GWCDeployment|display text=Get started}} article.
 }}
 |advanced=No
 }}

@@ Line 2: / Line 2: @@
 |DisplayName=How Widgets works
 |TocName=How Widgets works
-|Context=Learn how Genesys Widgets works.
+|Context=Genesys Widgets relies on certain technologies in order to function. This article describes what is required for widgets to work.
 |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 {{#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.
+|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.
 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=CallbackService}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=CallbackService-combined|display text=Callback Service}}
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=StatsService-combined|display text=StatsService}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=StatsService-combined|display text=Stats Service}}
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChatService-combined|display text=WebChatService}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChatService-combined|display text=Web Chat Service}}
 ===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=CallUs}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=CallUs-combined|display text=Call Us}}
-*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=ChannelSelector-combined|display text=ChannelSelector}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=ChannelSelector-combined|display text=Channel Selector}}
 *{{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=WebChat}}
+*{{Link-AnywhereElse|product=WID|version=Current|manual=SDK|topic=WebChat-combined|display text=Web Chat}}
 ===Bridge plugins===
@@ Line 56: / Line 56: @@
 |HIWSectionAlignment=Vertical
 |HIWSectionGif=No
 |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 63: / Line 64: @@
 |HIWSectionAlignment=Vertical
 |HIWSectionGif=No
 |HIWSectionText=Read the {{Link-AnywhereElse|product=WID|version=Current|manual=Developer|topic=GWCDeployment|display text=Get started}} article.
 }}
 |advanced=No
 }}

@@ Line 11: / Line 11: @@
 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.
-[[File:CXWChatWidget_082017.png|1000x1000px]]
+[[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 {{#Widget:ExtLink|link=https://en.wikipedia.org/wiki/Publish–subscribe_pattern|displaytext=publish-subscribe}} model 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.

@@ Line 4: / Line 4: @@
 |Context=Learn how Genesys Widgets works.
 |ComingSoon=No
-|Platform=GenesysEngage-onpremises
+|Platform=GenesysEngage-cloud
 |Role=Developer
 |featurename=Widgets

WID/HIW - Revision history

Mwest: Text replacement - "Agent Desktop" to "Agent Workspace"

Monique.gionet@genesys.com: Published

Chrissy.forrest@genesys.com: Published

Ed.jamer@genesys.com: Reverted edits by Ed.jamer@genesys.com (talk) to last revision by Chrissyforrest

Ed.jamer@genesys.com: Published

Chrissyforrest: Published

Chrissyforrest: Published

WikiSysop: Text replacement - "\|Platform=([^\|]*)GenesysEngage-onpremises([\|]*)" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|]*)PureEngage([\|]*)" to "|Platform=$1GenesysEngage-onpremises$2"

Chrissyforrest: Published

WikiSysop: Text replacement - "\|Platform=([^\|])GenesysEngage-onpremises([\|])" to "|Platform=$1GenesysEngage-cloud$2"

WikiSysop: Text replacement - "\|Platforms?=([^\|])PureEngage([\|])" to "|Platform=$1GenesysEngage-onpremises$2"