Interaction Workspace 8.0.0 .NET Developer's Guide and API Reference
Introducing Interaction Workspace

The following topics provide details about Interaction Workspace:

Interaction Workspace is the customer interaction interface for the Genesys 8 software suite. Interaction Workspace contains many components that you can use to enrich the content of Interaction Workspace with custom views and functionality.

You can use the following Interaction Workspace components to customize your interface:

A set of Interaction Workspace Extension Samples is also provided to illustrate the best coding practices for Interaction Workspace customization.

Interaction Workspace Architecture

Figure 1 illustrates a minimal deployment that consists of agent workstations that are connected directly to the Genesys back-end servers.

Architecture Simple

Figure 1: Simple Client-Server Architecture

Dependency Injection Container Application Block

The Dependency Injection Container Application Block is available for use when you use loosely-coupled applications to develop Interaction Workspace. This lightweight, extensible Dependency Injection container enables developers to build loosely-coupled applications and provides the following advantages:

Note: Genesys Enterprise SDK also implements Dependency Injection recommendations, which makes integration easier.

Technical and Design Concepts Application to Customization
Dependency Injection and Inversion of Control Used by developers to declare and retrieve alternative implementation of services, models, views, and presenters. Developers can use the Dependency Injection and Inversion of Control when they are developing software.

Loosely-coupled Application Library

The Interaction Workspace is built by using a loosely-coupled application library. This library is used by developers to create composite Windows Presentation Foundation (WPF) applications. It is designed to help architects and developers achieve the following objectives:

The Interaction Workspace provides guidance and implements patterns that make customization easier. In general, all of these concepts have a common aim, which is to implement loosely-coupled applications and ease extensibility.

Technical and Design Concepts Description Application to Customization
Model View Presenter The Model View Presenter can separate the responsibilities of the visual display and the the responsibilities of user interface state and behavior into different classes named View and Presentation Model, respectively. The View class manages the controls on the user interface, and the Presentation Model class acts as a façade on the model with UI-specific state and behavior. The Presentation Model class acts as a façade by encapsulating the access to the model and by providing a public interface that is easy to consume from the View (for example, using data binding). An alternate custom View can be built for any given out-of-the-box Presenter. An alternate custom Presenter can be built for any given out-of-the-box View.
Module A module can be individually developed, tested, and deployed by different teams. Customization can be implemented by partners or by customers, in a reusable or single-use purpose.
Region Manager Regions enable a compositional pattern and are commonly used in template layouts and multiple view layouts. Integration of custom views into out-of-the-box named and documented Regions is simplified, even without knowledge of the application construction. For example, in a typical application, a region can be a tab area.

Interaction Workspace Modules

As defined in the software development kit (SDK), a module is a software element that can be individually developed, tested, and deployed by different teams. Interaction Workspace contains several modules that can cover one or several layers of the application. They can contain views, presenters, or models. In general, the functional modules cover the full stack, whereas the service modules focus on a particular layer.

By using a modular approach in the application, Genesys is able to provide an SDK to developers who are planning to add customized code into Interaction Workspace.

Figure 2 summaries the various types of modules in Interaction Workspace.

Types of Modules

Figure 2: Types of Modules in Interaction Workspace

Additional Information

Refer to the Genesys Developer Documentation CD or the Genesys Developer website, DevZone. DevZone is available at http://www.genesyslab.com/developer. It contains the latest versions of all Software Development Kit (SDK) documents, and forums, along with other important sources of developer-related information.

Genesys DevZone

For additional information about the Genesys Telecommunications Laboratories, Inc., see our Technical Support website.

The following documentation contains information about Interactive Workspace. Genesys recommends that you consult the Deployment Guide first.

Top of Page