Jump to: navigation, search

Working with the Playground Application

The Playground application website features a header block and four other functional blocks that can all be collapsed with a click. You can use the links and buttons in these blocks to trigger chat, business rules, and business events.

The Playground application.

PlayGround

The PlayGround header block displays the current page name (Start page in the image above) and links to the Read Me file for the application.

The PlayGround header block.

Change instrumentation script

The Change instrumentation script block allows you to configure the instrumentation script on the fly. For details about configuring the script, see Configuring the Instrumentation Script.

The Change instrumentation script block.

Reactive engagement

The Reactive engagement block allows you to initiate chat interactions with an agent simply by clicking a link.

The Reactive engagement block.

The block contains three links that demonstrate reactive chat, with and without the pacing algorithm.

  • Get pacing state for chat — Displays true if the pacing algorithm allows reactive chat and false if the pacing algorithm doesn't allow reactive chat. See Configuring the Pacing Algorithm for details.
  • Chat with pacing — Opens a registration form for a chat if the pacing algorithm allows reactive chat.
  • Chat without pacing — Opens a registration form for a chat, regardless of whether the pacing algorithm allows reactive chat.

You can modify the code for each of the actions by clicking the related view code button GWE-user-info-button.png, making your changes, and then clicking Save.

Proactive engagement

The Proactive engagement block.

The Proactive engagement block contains a set of links that trigger business rules. Clicking one of these links changes the address of the page, the page title, and the name of the page in the PlayGround header block. In this way, the application simulates a functioning multi-page website.

To trigger business rules, the following conditions must be true:

  • All system components must work. See Step 7 in Installing Genesys Web Engagement for component information.
  • The website must have a properly configured instrumentation script in the Change instrumentation script block.
  • All resources fro the instrumentation script should be available.
  • There are available agents for the selected media channel.
  • The invitation limit (3 by default) should not be exhausted. The invitation limit is set in the Engagement strategy for the application. See Engagement Policy (Decision Workflow) for details.

Here is a summary of events when you trigger a business rule:

  • The application displays the engagement invitation. You can accept, reject, or ignore the invite.
  • If you ignore, the invitation disappears. If you reject, the invitation closes.
  • If you accept and are logged in (see the User Identification block for details), the application does not display the registration form and you begin the chat session.
  • If you accept and are not authorized, the application displays the registration form. If you complete the registration form, the information is passed on to the agent in Interaction Workspace. If you do not complete the registration form, you communicate with the agent as an anonymous user.

The Proactive block lets you try out different business rules based on the default rule templates included with Genesys Web Engagement. See Creating Business Information for details about rule templates and Deploying a Rules Package for more information about rules.

Business Rule Description
Singleton Entrance to the page is specified in the PlayGround-Singleton category.

Category: PlayGround-Singleton

Timeout 30 Entrance to the page is specified in the PlayGround-Timeout30 category. A business rule is triggered after a 30-second delay.

Category: PlayGround-Timeout30

Sequence Serial input to the first page First, then on page Second. The sequence may be any length. For example, this could be extended to check if all the necessary pages of a Wizard have been successfully completed.

Categories: PlayGround-Seq-First and PlayGround-Seq-Second

Sequence Ads Serial input to the first page AdvertisementOne, then on page AdvertisementTwo. The sequence may be any length. For example, this could be used to display advertisements. Note that Advertisement sequence does not passed through the Orchestration server and instead sends notification directly to the browser.

Categories: PlayGround-Ads-First and PlayGround-Ads-Second

Set Bypassing pages set in any order. The user can go to PageA, then on to PageB, or vice versa.
Counter (3) Counts multiple entries on the same page.

Category: Playground-Counter

Simple search Search for a specific keyword. The keyword is hard-coded in the business rule.
Search with category Search for a specific keyword. The keyword is defined by the PlayGround-Search category. A regular expression can be used to describe the keyword.

Category: PlayGround-Search

User Identification

The User Identification block contains links to send events that are generated by the Monitoring API. All events in this block can be modified by clicking the related view code button GWE-user-info-button.png and then Save. You can use the user information to manage registration (from the registration form for the authorized user) and send the necessary information to the agent.

The User Identification block.

This block demonstrates three generated events:

  • Send User Info—Send events with user information. You can use this event to identify an authorized user who has previously visited the site.
  • Sign In—Send the authorized user login event.
  • Sign Out—Send the authorized user log out event.

System events

The System events block contains links that demonstrate the PageEntered and PageExited system events that are part of the Monitoring JS API. You can modify the code for each of the actions by clicking the related view code button GWE-user-info-button.png, making your changes, and then clicking Save.


The System events block.


Important: The PageEntered event updates the current pageID. Make sure that a PageExited event is sent before sending a PageEntered event, as it is important for correctly modeling the actions of a Single Page Application.

This page was last modified on June 28, 2019, at 12:23.

Feedback

Comment on this article:

blog comments powered by Disqus