Release Number | AIX | HP-UX | Linux | Solaris | Tru64 UNIX | Windows |
---|---|---|---|---|---|---|
7.6.101.40 [04/07/14] – Hot Fix | X | X | X | X | ||
7.6.101.39 [10/31/12] – Hot Fix | X | X | ||||
7.6.101.38 [09/14/12] – Hot Fix | X | |||||
7.6.101.37 [05/09/12] – Hot Fix | X | |||||
7.6.101.35 [11/03/11] – Hot Fix | X | X | X | X | ||
7.6.101.34 [02/23/11] – Hot Fix | X | X | X | X | ||
7.6.101.33 [09/29/10] – Hot Fix | X | X | X | X | ||
7.6.101.29 [07/07/10] – Hot Fix | X | |||||
7.6.101.27 [05/07/10] – Hot Fix | X | X | X | X | ||
7.6.101.25 [04/09/10] – Hot Fix | X | X | X | X | ||
7.6.101.24 [10/21/09] – Hot Fix | X | X | X | X | ||
7.6.101.21 [08/26/09] – Hot Fix | X | X | X | X | ||
7.6.101.19 [07/02/09] – Hot Fix | X | X | X | X | ||
7.6.101.18 [06/05/09] – Hot Fix | X | X | ||||
7.6.101.16 [04/24/09] – Hot Fix | X | |||||
7.6.101.15 [01/30/09] – General | X | X | X | X | ||
7.6.000.25 [03/12/09] – Hot Fix | X | |||||
7.6.000.23 [07/03/08] – General | X | X | X | X | ||
7.6.000.20 [05/19/08] – General | X | X | X | X | ||
7.6.000.15 [02/15/08] – General | X | X | X | X |
As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesys.com for more details.
This release note applies to all 7.6 releases of Interaction Server.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information about third-party software used in this product, see the Read Me. Please contact your Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections or modifications.
Interaction Server now includes the attribute attr_have_more_interactions,
with
the correct value, in EventSnapshotTaken
when there are more interactions than the limit
set by the corresponding request or by the max-interactions-per-snapshot
option.
(ESR-7945)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections or modifications.
In this release, Interaction Server no longer deadlocks when agents or places that are logged in are simultaneously (a) being logged out or disconnected and (b) being deleted from the configuration. (ER# 309595185)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections or modifications.
In this release, when an interaction has been placed in a queue by request from an agent desktop,
Interaction Server acknowledges this action to the desktop
without waiting for the interactions
database to finish updating.
Previously, in cases in which the database response was delayed, Stat Server received premature notification that
desktop capacity had been freed, before it actually was.
This sometimes caused increased loading on the desktop, because URS could possibly route a new interaction to the desktop
while the desktop was still waiting for confirmation from Interaction Server that it was free of the old interaction.
(ER# 308023018)
Note: Because of this modification, it may occur that a custom desktop
receives an acknowledgement to RequestPlaceInQueue
before it receives the
acknowledgement to a preceding RequestChangeProperties
if
the desktop issues new requests without waiting for a response to the previous request.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections or modifications.
Interaction Server no longer delays sending requests to the DB Server when it receives snapshot requests from multiple clients. (ER# 299065800)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections or modifications.
Interaction Server no longer terminates unexpectedly while reconnecting to Configuration Server. Previously, this sometimes happened during conditions of network delay. (ER# 281508104)
Interaction Server no longer exits if you update a routing strategy and save the changes before Interaction Server has finished initializing. (ER# 57111954)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections or modifications.
Interaction Server is now able to send Java statistics to Stat Servers that are running in backup mode as well as those running in primary mode.
Note: To receive statistics, a backup Stat Server must also satisfy all of the following requirements:
Connections
tab of the Interaction Server.
accept-clients-in-backup-mode
in its statserver
section
with a value of yes.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This section describes new features that were introduced in this release of Interaction Server.
flexible_properties
field of its database.
The flexible_properties
field stores most of the Business Properties
(see the "Interaction Properties" chapter in the eServices (Multimedia) 8.0 User's Guide)
and must be unpacked by Interaction Server.
When Interaction Server fails to unpack the flexible_properties
field,
it ignores the data loaded from the database, and logs one of the following messages,
identifying the specific interaction and specific data that Interaction Server has failed to unpack.
Unable to process data received from DAP:'[DAP name]'([DBServer connection ID]), request id:'[database request ID]', dbchannel stack id:'[transaction ID]': More BLOB records received than there are interaction records[new line character]Statement: [[SQL statement text]]
Unable to process data received from DAP:'[DAP name]'([DBServer connection ID]), request id:'[database request id]', dbchannel stack id:'[transaction id]': Can't unpack BLOB, Suspected interaction id: [Interaction id], binary data: [binary data][new line character]Statement: [[SQL statement text]]
(ER# 256781811)
This release includes the following corrections or modifications.
When scanning views for interactions, Interaction Server now continues to scan until either the required number of interactions is submitted to the strategy or all views contain no interactions. Previously, if the last view in the cycle was empty, submission stopped. This could lead to a rate of submission that was lower than expected. (ER# 259472471)
This release corrects an issue that sometimes caused Interaction Server to send an interaction to Universal Routing Server with attached data from another interaction. (ER# 260479439)
This release corrects an issue that caused Interaction Server's memory consumption to increase, even when it was idle. (ER# 256703301)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections or modifications.
In this release, Interaction Server properly handles reconnection with Universal Routing Server after a network disconnect. Previously, in some cases, Interaction Server allowed a second connection from the same client. Now Interaction Server permits a client, such as Universal Routing Server, to open a new connection only after any previous connection from that client is closed.
Note: The ADDP protocol must be enabled in connections to Interaction Server. Otherwise Interaction Server may not detect disconnections correctly. (ER# 254611919)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This section describes new features that were introduced in this release of Interaction Server.
This release includes two new features relating to
the segmentation feature (Segmentation
tab in the View object of a Business Process).
cached_at
to the Interaction Server database
by executing one of the following statements:
alter table interactions add cached_at datetime
alter table interactions add cached_at date
alter table interactions add cached_at timestamp
honor-segmentation-generations
to the settings
section
of the Interaction Server application object and set its value to true.
The default value of this option is false
and changes to it take effect after restart.
Note: Interaction Server does not check the presence of the
cached_at
field or its type at startup.
If the honor-segmentation-generations
option is set to true
and the field is absent, the segmentation feature does not work and
there will be SQL errors in the Interaction Server log.
If the option is set to the default value false,
database modification is not necessary.
(ER# 252019251)
View
section on the Annex
tab,
create an option called default-limit
and assign it a positive integer value.
Now, instead of calculating the per segment limit dynamically based on segments that are actually present, Interaction Server will use this default segment limit. (ER# 252019251)
Note:
This release also includes the following corrections or modifications.
Interaction Server no longer exits unexpectedly when a DB Server has not been assigned
on the General
tab of the Logger DAP for Interaction Server.
(ER# 215418771)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release includes the following corrections or modifications.
A new option event-filter-by-id
was added to the event-filtering
section of the Interaction Server DAP object.
This option provides the ability to specify a comma-separated list of EventIDs
to be written to the Event Logger database.
This option is also included in release 8.0.1 and is documented in
the eServices (Multimedia) 8.0 Reference Manual.
(ER# 245862245)
The dbo
account does not have to be an owner of the Interaction Server database on MS SQL.
This restriction was removed for this release of Interaction Server.
To support this feature, a new option schema-name
has been added,
which specifies the name of the MS SQL database schema.
It is applicable to MS SQL database only, its default value is dbo,
and its valid values are any valid MS SQL database schema name.
This option is also included in release 8.0.1 and is documented in the eServices (Multimedia) 8.0 Reference Manual.
(ER# 232115123)
Interaction Server now correctly sets attr_ref_id=-1
for self-generated events
(events that are not responses for requests).
In previous releases, Interaction Server incorrectly set the attr_ref_id=0
for these events.
(ER# 239018638)
This release includes improved behavior of Interaction Server
when a primary instance is shut down from Solution Control Interface.
Now Interaction Server finishes updating its database before it signals Local Control Agent that it is exiting.
Previously in this scenario, some agent clients received Unknown interaction identifier specified
messages
after the backup server took over.
(ER# 241592136)
This release corrects an issue that prevented Interaction Server from connecting to a backup DB Server, on rare occasions during its own switchover from backup to primary mode. (ER# 231244931)
Interaction Server is now able to distribute an EventInteractionSubmitted
when
an interaction is submitted by a client application without an established client name.
(ER# 234763306)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This section describes new features that were introduced in this release of Interaction Server.
Two possible values have been added to the not-ready-on-invitation-timeout
option.
This option determines Interaction Server's behavior when the time set by the delivering-timeout
option expires while attempting to deliver an interaction. For this option to take effect, the delivery attempt must result from routing
(not from transfer, conference, or intrusion).
The effects of the possible values are as follows:
false
No action.
true
(default)Set agent to not ready
for the media type of this interaction.
dnd-on
Set agent's DND to on
(nothing will be delivered to the agent).
all-media
Set agent to not ready
for all media.
See the Multimedia 7.6 Reference Manual for a full description of these options. (ER# 236814211)
This release also includes the following corrections or modifications.
Interaction Server now accumulates event messages in memory, then writes them to the reporting events (Event Logger) database (as determined by the configuration), without any undesirable behavior. Previously, Interaction Server exited during the accumulation stage. (ER# 236515641)
Interaction Server no longer exits when a Place occupied by an Agent is deleted from the configuration. Previously, this was an issue for the 32-bit build for AIX. (ER# 237178891)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. This section describes new features that were introduced in this release of Interaction Server.
The following configuration option has been added to the settings
section:
allow-multiple-agent-connections
Default value: true
Valid values: true, false, yes, no
Changes take effect: Immediately for all new login attempts
If set to false
or no,
Interaction Server does not allow an agent to log in using more than one connection (desktop application).
Agents that already logged in on more than one connection are not affected.
(ER# 233711001)
This release also includes the following corrections or modifications.
This release corrects an issue that caused Interaction Server to exit when a Place occupied by an Agent was deleted from the configuration. (ER# 231638359)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release also includes the following corrections and modifications.
Interaction Server no longer responds to RequestChangeProperties with an error message of no interaction ID found. (ER# 229276147)
This release corrects an issue in the Stat Server listener that caused Interaction Server to terminate. (ER# 229190935)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release also includes the following corrections and modifications.
This release improves handling of requests to the interactions
database on the DB2 platform.
As a result, deadlocks occur less frequently.
(ER# 226810769)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release also includes the following corrections and modifications.
This release correctly handles deadlocks arising from database requests that do not initiate any explicit database transaction (such as snapshot requests without locks). Previously, this scenario caused the database channel to be disabled, and no response was sent to the client. (ER# 221039168, 224593366)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Interaction Server.
Support of IBM DB2 9.1.
Support of SQL hints in Interaction Queue View (for Oracle only).
The number of records in Snapshot query results can now be limited.
Custom fields can be added to the Interaction Server database.
Built-in scheduling is provided in workflow.
Pre-routing segmentation of interactions for proportional queuing has been added.
Event Logger has been added for storing reporting events.
Support for multiple agent desktops has been added.
Interaction Server now provides the ability to pull interactions from Universal Routing Server for distribution.
This release also includes the following corrections and modifications.
Interaction Server now correctly retrieves any interactions from the database
when the connection to DB Server is lost and then regained. Previously, Interaction Server would not
retrieve any interactions until default‑freeze‑interval
had expired. (ER# 174145831)
For environments with StatServer 7.6.100.12 and above,
this release corrects an issue with an events flow that blocked the calculation of
the statistics Internal_Interactions_Initiated
and Outbound_Interactions_Initiated.
(ER# 200264271)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix release of this product. No new features were introduced in this release of Interaction Server.
This release also includes the following corrections and modifications.
This release correctly handles deadlocks arising from database requests that do not initiate any explicit database transaction (such as snapshot requests without locks). Previously, this scenario caused the database channel to be disabled, and no response was sent to the client. (ER# 220311702)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. No new features were introduced in this release of Interaction Server.
This release also includes the following corrections and modifications.
This release corrects an issue with exchanging user data between interactions when they are submitted to Universal Routing Server. That issue was caused by an incorrect SQL statement that was used to pull several interactions at once. The issue occurred in release 7.6.000.20 with Oracle databases only. (ER# 194009156)
Interaction Server now processes RequestLockInteraction
correctly.
This request was not processed properly in release 7.6.000.20, with Oracle databases only.
(ER# 195600276 )
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in this release of Interaction Server.
The following configuration option has been added to the settings
section:
max-workbin-interactions
Default value: 200
Valid values: Any integer in the range of 50
to 1000
Changes take effect: Immediately
Specifies the maximum number of interactions that Interaction Server returns in response
to RequestGetWorkbinContent.
(ER# 186521545)
When an interaction is pulled by a client other than Universal Routing Server (URS), Interaction Server now adds a reason
to the EventRouteUsed
that it sends to URS. It does this by giving the event a Reason
attribute
containing the following key-value pairs:
ReasonSystemName;
value PulledOut
ReasonDescription;
value Pulled out of router by other client
This release also includes the following corrections and modifications.
This release corrects issues (except in some rare scenarios)
with the statistics queue-current in processing,
queue-current length, queue-current waiting processing,
tenant-current in processing,
and tenant-current waiting processing
(these are the internal names used by Interaction Server).
Previously, in some event flow scenarios, these statistics were miscalculated.
(ER# 178855946)
In a failover scenario in which a backup Configuration Server is promoted to primary, Interaction Server now correctly attempts to connect to the new primary Configuration Server. Previously, when Interaction Server and Configuration Server were running on the Solaris platform, Interaction Server did not attempt to connect to the new primary Configuration Server. (ER# 180591061)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This section describes new features that were introduced in the initial 7.6 release of Interaction Server.
Support of Red Hat Enterprise Linux 4.0 has been added.
Chats that are abandoned by customers while in a virtual queue now result in EventAbandoned
.
Interaction Server is now able to pull interactions from the system view by external_id
,
and to request properties of interactions by external_id
.
Interaction Server now provides ReasonCodes
to Universal Routing Server when it removes an interaction from a strategy.
Open Media reporting data is now made available to ICON and Info Mart so that reports can be built and generated on Third Party Media interactions.
A new option default‑view‑freeze‑interval
has been added to the settings
section. This option specifies the length of time, in seconds, that Interaction Server suspends database checks for views that do not have any interactions.
A new option low‑pull‑threshold
has been added to the settings
section. This option specifies the number of interactions cached for any view that triggers Interaction Server to check for more interactions in the database.
A new option high‑pull‑threshold
has been added to the settings
section. This option specifies the maximum number of interactions that Interaction Server tries to cache for a view when it checks for more interactions in the database.
A new option submit‑timer‑interval
has been added to the settings
section. This option specifies the frequency, in milliseconds, with which Interaction Server checks views for interactions.
A new section log‑filter
with the option default‑filter‑type
has been added to Interaction Server's configuration options. This option is used to set the default log filter settings (skip
, hide
, or copy
) for user data keys.
A new section log‑filter‑data
has been added to Interaction Server's configuration options. This section is used to configure custom log output settings (skip
, hide
, or copy
) for specific user data keys.
In the Interaction Queue View
object, a new freeze‑interval
option has been added to the View
section of the Annex
tab. This option specifies the length of time, in seconds, that Interaction Server suspends database checks for a particular view when it has no interactions.
This release includes the following corrections and modifications that were made between Release 7.5 or earlier releases and the initial 7.6 release:
In previous releases, in rare circumstances under heavy loads, Interaction Server would return the message Client does not own the interaction
to Universal Routing Server. This release has resolved that issue. (ER# 118637429).
On shutdown, Interaction Server now generates Events and distributes messages correctly. In previous releases, Interaction Server would only distribute statistics updates during shutdown. (ER# 100573685)
Now Interaction Server activates/deactivates workflow Submitters correctly upon reconnecting with Universal Routing Server after a disconnection caused by addp
timeout. (ER# 78345)
This release also includes all fixes made in previous releases of this product (including hot fix releases) at the time of this initial 7.6 release.
This section provides the latest information on known issues and recommendations associated with this product.
The Interaction Server Database Access Point (DAP) must have its Case Conversion
attribute (on the
DB Info
tab) set to any
or upper.
Setting it to lower
causes an error when Interaction Server initializes.
The scripts for setting up and pruning the Event Logger database, which are supplied with Interaction Server, do not support MSSQL 2000.
When using an IBM DB2 database engine, the usage of properties with a decimal data type in database fields for routing segmentation is not supported. (ER# 218576691)
Found In: 7.6.101.15 | Fixed In: |
In rare circumstances on UNIX, when Interaction Server is stopped from Solution Control Interface while under load, Interaction Server will exit with a core dump. (ER# 217483826)
Found In: 7.6.101.15 | Fixed In: |
On AIX, the value of the last key-value pair in lists of key-value pairs might be partially printed in the text log file and console. Closing quotation marks may not be printed for strings. (ER# 216954830)
Found In: 7.6.101.15 | Fixed In: |
Interaction Server may exit unexpectedly if a DB Server has not been assigned on the General
tab of the Logger DAP for Interaction Server. (ER# 215418771)
Found In: 7.6.101.15 | Fixed In: 7.6.101.27 |
It is not possible to lock a snapshot with more than 1000 interactions in Oracle. The Interaction Server option max-interactions-per-snapshot
has a maximum value of 2000
, but Oracle has a limitation of 1000
. If using an Oracle database, be aware of this Oracle limitation.
(ER# 204795083)
Found In: 7.6.101.15 | Fixed In: |
Release 7.6.1 does not support the mandatory-logging
option in the logger-settings
section of the Interaction Server DAP options, described in the Multimedia 7.6 Reference Manual. This option is reserved for future use. (ER# 195790067)
Found In: 7.6.101.15 | Fixed In: |
When the connection to DB Server is lost and then regained,
Interaction Server does not retrieve any interactions from the database until default‑freeze‑interval
has expired. (ER# 174145831)
Workaround: Restart Interaction Server.
Found In: 7.6.000.15 | Fixed In: 7.6.101.15 |
In rare cases under heavy loads, Interaction Server might not switch to primary mode during switchover. This problem is intermittent; it occurs if switchovers are performed simultaneously with short intervals between switchovers. (ER# 172356768)
Workaround: Restart both primary and backup Interaction Servers.
Found In: 7.6.000.15 | Fixed In: |
When the option delay‑updates
is set to true
,
and the external_id
is changed during the current handling session,
requests to get properties based on external_id
may fail if the database was not updated with the new value. (ER# 168597976)
Found In: 7.6.000.15 | Fixed In: |
Under heavy loads, extra interactions may be submitted to Universal Routing Server in the following situations:
(ER# 166786271)
Found In: 7.6.000.15 | Fixed In: |
In rare cases when multiple clients are manipulating the same interaction simultaneously,
the following statistics may be miscalculated: queue-current in processing, queue-current length, queue-current waiting processing,
tenant-current in processing,
and tenant-current waiting processing.
(ER# 180485806)
Found In: 7.5.000.19 | Fixed In: |
Interaction Server does not issue any warning when it sees an invalid value
for option max-submitted-interactions
(in the Annex
tab of a Strategy
object)
and max-submission-rate
(in section Interaction Server Name
of the Annex
of
Universal Routing Server). Interaction Server uses the default value zero
if the value submitted is invalid; this disables submission to Universal Routing Server.
(ER# 107154166, 107154168)
Found In: 7.5.000.10 | Fixed In: |
Setting an interaction custom property to an empty string value effectively removes this property from attached data in the interaction when Interaction Server uses Oracle database. (ER# 105650427)
Found In: 7.5.000.10 | Fixed In: |
If you update a routing strategy and save the changes before Interaction Server has finished initializing, Interaction Server exits. (ER# 57111954)
Found In: 7.2.000.10 | Fixed In: 7.6.101.35 |
If Interaction Server is processing multiple interactions when it receives a command to terminate normally, it may take several minutes to fully shut down. This is because of the time it takes for Interaction Server to properly finalize all updates. (ER# 41880734)
Found In: 7.2.000.10 | Fixed In: |
Interaction Server may freeze under the following condition: If a Tenant is added/removed in the Interaction Server Application when Interaction Server has not yet finished reading the configuration of its existing Tenants. (ER# 34221195)
Workaround: Restart Interaction Server after making Tenant changes.
Found In: 7.2.000.07 | Fixed In: |
If the name of a custom property in the Interactions table contains a space character, Interaction Server does not convert the name into a standard property name. (ER# 102339)
Found In: 7.1.000.03 | Fixed In: |
In the rare situation where both Configuration Server and Interaction Server are running without a network connection between them, Interaction Server does not react to the deletion or addition of objects in Configuration Manager. (ER# 101751)
Found In: 7.1.000.03 | Fixed In: |
Interaction Server does not support interaction level logging. (ER# 74418)
Found In: 7.0.000.09 | Fixed In: |
This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.
Solaris 8 and Solaris 9 are no longer supported.
Discontinued As Of: 7.6.101.15 |
Information in this section is included for international customers.
There are no internationalization issues for this product.
Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
Multimedia 7.6 Deployment Guide describes deployment procedures for all Multimedia components. It also contains a high-level description of the Multimedia system, its architecture, and a list of new features in the current release.
Multimedia 7.6 User's Guide provides overall information about and recommendations on the use and operation of Genesys Multimedia.
Multimedia 7.6 Reference Manual provides a reference listing of all configuration options and of field codes used in standard responses.
Multimedia 7.6 Web API Client Developer's Guide describes the structure of the Web API, explains the Simple and Compound Samples, and describes procedures for customizing them.
Multimedia 7.6 Web API Reference is a Javadoc listing of classes, methods, fields, and constants of the Web API portion of the Web API Server component.
Multimedia 7.6 Selected Conceptual Data Models for the UCS Database describes a portion of the Universal Contact Server (UCS) database.
Multimedia 7.6 Universal Contact Server Manager Help is a guide to the Universal Contact Server Manager user interface.
Multimedia 7.6 Universal Contact Server Help is a guide to the Universal Contact Server user interface.
Universal Routing 7.6 Interaction Routing Designer Help is a guide to Interaction Routing Designer, including the portion of it that designs interaction workflows and business processes for Multimedia.
Universal Routing 7.6 Business Process User's Guide contains step-by-step instructions for using Interaction Routing Designer to design interaction workflows. It also describes the sample business processes supplied with Multimedia.
Genesys Desktop 7.6 Help is a guide to using the Genesys Desktop.
Genesys Events and Models Reference Manual includes a set of basic interaction models, showing the components involved and the event messages sent among them. These models and events were formerly presented in the Open Media Interaction Models Reference Manual. The request messages that were also described in that book are now documented in the API References of the Platform SDK.
Product documentation is provided on the Customer Care website, the Genesys Documentation wesbite, and the Documentation Library DVD (produced monthly).
Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.