| Release Number | AIX | HP-UX PA | HP-UX IPF | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 8.1.400.15 [04/27/15] – Hot Fix | X | X | X | X | ||
| 8.1.400.13 [11/07/14] – Hot Fix | X | X | ||||
| 8.1.400.12 [10/24/14] – Hot Fix | X | X | X | X | ||
| 8.1.400.11 [06/18/14] – Hot Fix | X | X | X | X | ||
| 8.1.400.10 [12/17/13] – General | X | X | X | X | ||
| 8.1.300.13 [05/31/13] – General | X | X | X | X | ||
| 8.1.201.05 [02/25/13] – General | X | X | X | X | ||
| 8.1.200.12 [05/07/13] – Hot Fix | X | |||||
| 8.1.200.11 [01/21/13] – Hot Fix | X | |||||
| 8.1.200.10 [11/12/12] – Hot Fix | X | |||||
| 8.1.200.09 [05/31/12] – General | X | X | X | X | ||
| 8.1.000.06 [04/18/12] – Hot Fix | X | X | X | |||
| 8.1.000.05 [10/27/11] – 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 8.1 releases of E-mail 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 Genesys Customer Care representative if you have any questions.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections:
When sending a new outbound email, E-mail Server keeps the original Thread ID. Previously the Thread ID was modified, preventing it from being used to identify the interaction. (ESR-9942)
Unparsable messages are now properly moved to the 'failed item directory', so they no longer prevent E-mail Server from loading new incoming messages. (ESR-9932)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction:
Now E-mail Server properly inserts an inbound e-mail in the database if an outbound e-mail has the same message ID. Previously E-mail Server treated the inbound e-mail as a duplicate and did not insert it. This situation could arise with Non-Delivery Report e-mails. (ESR-8622)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction:
E-mail Server now properly resumes e-mail processing after reconnecting to Configuration Server. Previously, e-mail processing could fail to resume after reconnection to Configuration Server, making it necessary to restart E-mail Server. (ESR-8438)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following corrections:
Password fields configured in the application's options are no longer displayed in debug logs when the options are updated or created. (ESR-8195)
Advanced configuration of log4j loggers is now disabled to prevent displaying sensitive data from raw Configuration Server XML logs. (ESR-8196)
This release can be installed on AIX, Linux Red Hat, and Solaris when Configuration Server is set to support multiple languages (UTF encoding).
Note: This Correction applies only to builds issued after 08/07/14. (ESR-8346)
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 E-mail Server.
Support of Java 7 64-bit
Support of IPv6
Support for the retrieval of e-mail using Exchange Web Services protocol
The type option (pop-client section)
has the additional possible value ews.
This value is required for connecting to an Exchange Server running EWS.
If an attachment in an e-mail has no name,
E-mail Server gives it the filename attachment.
In this release, E-mail Server can also automatically add a file extension,
based on the e-mail's MIME type (if present),
to the filename. Some examples:
To enable this feature, create an option called force-attachement-extension-creation
in the email-processing section, with the value true.
With any other value or if this option is not present, E-mail Server
creates the filename with no extension, as in previous releases.
folder-path
inbox
pop-client section. Specifies the folder that E-mail Server checks for messages.
If E-mail Server is connected to Exchange Server, the value must be empty
(Exchange Server's underlying library opens inbox by default).
folder-separator
pop-client section. Specifies the separator to use when defining or accessing a folder,
as in the folder-path option, for example.
exchange-version
Default value: (empty string)
Valid values: Exchange2007_SP1, Exchange2010, Exchange2010_SP1, Exchange2010_SP2
Changes take effect: At the next POP cycle
pop-client and smtp-client sections. Specifies the version of Exchange Server
that E-mail Server connects to.
failed-items-folder-name
Default value: faileditems
Valid values: Any string
Changes take effect: At the next POP cycle
pop-client section. Specifies the folder to which failed items are moved.
Effective only if move-failed-ews-item (next item) is set to true.
The value must be the name of a valid folder on the corporate server.
If a folder with that name does not exist in the corporate server, E-mail Server tries to create it.
If folder creation fails for some reason, a log message similar to the following is sent:
15:01:02.115 Std 25118 [MsgIn-11]
move-failed-ews-item
Default value: true
Valid values: true, false, yes, no
Changes take effect: At the next POP cycle
pop-client section. Specifies whether E-mail Server does (true)
or does not (false) take items that fail to be loaded and move them to the folder specified
in the failed-items-folder-name option (previous item).
Explanation: When using EWS to connect to an Exchange Server, if an item cannot be loaded, the entire retrieving cycle fails. (Item here means a named item such as an e-mail, contact, folder, and so on). Moving such "killer" items to another folder prevents E-mail Server from trying to read them again (and failing again). Note that with this option set to
true, such items still make the cycle fail,
but then they are moved. If there are several such faulty items, it takes several cycles to move them all.
server-type
Default value: smtp
Valid values: smtp, ews
Changes take effect: At the next POP cycle
smtp-client section. Specifies whether the server that E-mail Server
connects to uses SMTP or EWS.
ucs-reconnect-timeout
Default value: 65000
Valid values: Positive integer
Changes take effect: Upon restart
settings section. Specifies, in milliseconds, the timeout of E-mail Server's
connection to UCS.
Note: To avoid inconsistency, E-mail Server, like every other client of UCS, should have the timeout of its connection to UCS set to a higher value than the timeout of UCS's connection to its Database Access Point (DAP). This allows UCS to consistently either perform long queries or abort them, in accord with the clients' requirements.
As described below, starting in this release, if UCS has the timeout set to 0 for its DAP connection, this is interpreted as 60 seconds. Previously 0 was interpreted as an infinite timeout. The default value of 65 seconds for the connection from E-mail Server to UCS then ensures that E-mail Server works well with UCS out of the box—that is, without changing any default values.
This release includes the following corrections and modifications:
In prior versions, when E-mail Server sent an e-mail, it incorrectly updated the corresponding interaction in the UCS database. This incorrect update prevented statistics from being computed correctly. Now E-mail Server provides the correct parameters for tenant ID, Interaction type, Interaction subtype, status, and parent ID in its requests to UCS.
Therefore, when E-mail Server updates interactions in UCS, the parent interaction must still exist in the UCS database. For example, in the case of a chat interaction and a chat transcript being sent, the parent must not be deleted before E-mail Server successfully sends the transcript.
Starting in this release, if UCS has the timeout set to 0 for its DAP connection, this is interpreted as 60 seconds. Previously, 0 was interpreted as an infinite timeout. This prevents the issue of E-mail Server duplicating e-mails when a switch of Oracle RAC node occurs, as described in ER# 304334929. The default value of 65 seconds for the connection from E-mail Server to UCS then ensures that E-mail Server works well with UCS out of the box—that is, without changing any default values.
E-mail Server now processes interactions with no interaction content. Previously, it failed to process such interactions and produced a NullPointerException. (ESR-7508)
E-mail Server no longer reports connection lost when a connection to UCS times out.
It now correctly reports a connection timeout message with ID 25116.
(ESR-7278)
E-mail Server now correctly triggers General_Email_Responded and General_Email_Response_Time
reporting statistics on UCS.
(ESR-7557)
E-mail Server now correctly activates ADDP on its initial connection to Configuration Server. (ESR-7618)
E-mail Server now consistently processes requests while attempting to reconnect to Message Server, even under high loads. In some rare cases in a scenario with high loads, E-mail Server stopped processing requests. (ESR-6873)
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 E-mail Server.
Support of Java 7
Support of client-side port definition
Support of TLS, including FIPS 140-2 compliant cipher algorithms
This release includes the following corrections and modifications:
When E-mail Server is configured in a multi-tenant environment, it no longer requires the Configuration Server Application object to have the E-mail Server tenant set in its Tenants tab for E-mail Server to connect to a backup Configuration Server after switchover.
This correction was accomplished by addressing several issues in Configuration Server's warm standby management, tenant filtering, and configuration cache management. (ER# 318687174)
Modifications in the log section of an E-mail Server application are now instantly applied to its log output. (ER# 316170403)
E-mail Server no longer outputs the informational exception Failed to create message #41 when
connected to LCA.
(ER# 316343461)
E-mail Server can now send an EmailOut when the SubTypeId is set to null in the database.
Previously, a SubTypeId was mandatory even though Universal Contact Server does allow setting this field to null.
(ER# 322817301)
E-mail Server no longer fails to process requests whose size is exactly 65424 bytes. Previously, E-mail Server would time out while attempting to process such requests. (ER# 320158288)
Note: This is a porting of the correction that was previously made in release 8.1.200.12, for ER 321572343.
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 E-mail Server.
Support for Red Hat Enterprise Linux (RHEL) 6.0 64-bit.
This release includes the following corrections and modifications:
E-mail Server now correctly receives and processes all events from Local Control Agent. Previously, when E-mail Server received from Local Control Agent several events requesting a restart (Stop and Start) over a short period of time, the most recent event was not always taken into account. (ER# 314958501)
E-mail Server now correctly processes email from standard responses which
contain field code with localization operations such as <$WeekdayName(Interaction.DateCreated)$>
or <$MonthName(Interaction.DateCreated)$>. E-mail Server
now correctly takes into account the option email-processing/fieldcode-format-locale.
Note: This correction requires Universal Contact Server 8.1.300.xx or higher
to be installed and running. (ER# 313106681)
When Universal Contact Server is down, E-mail Server now rejects strategy
block requests and returns an error code.
(ER# 312633584)
The application Database ID and application Host are now correctly set in log messages, which allows raising alarms in Solution Control Interface. (ER# 311812195, 311257877, 309772715)
When E-mail Server sends outbound emails to the mailbox for inbound emails
and then retrieves them, it now logs Trace error 21225 Interaction table
contains already the Message Id <ID>. Previously, the log incorrectly
said Inbound emails table contains already the Message Id <ID>.
(ER# 310899119)
All options related to a pop-client section are now written in the logs on
a single line, which starts with the name of the pop-client. Previously, options
were written on multiple lines and knowing the associated pop-client was impossible.
(ER# 309772706)
Now E-mail Server writes the correct boolean value in its log file for the
option leave-msg-on-server. Previously, E-mail Server wrote the
opposite value (true instead of false, and vice-versa).
(ER# 309674679)
E-mail Server now successfully handles Configuration Server switchover and disconnect/reconnect scenarios. (ER# 307988491, 306185053, 306394711)
E-mail Server no longer fails while processing emails which contain attached files of size 65536 bytes. Previously, failure occurred when E-mail Server attempted to insert or query email content or attachments of this exact size. (ER# 307143080)
Note: This correction requires Universal Contact Server 8.1.200.03 or higher to be installed and running. (ER# 308860704).
E-mail Server now correctly handles email by extracting comma-separated Message-IDs
from the References header. Previously, when a retrieved MIME message
was not compliant to RFC-2822 and contained comma-separated Message-IDs in the
header retrieved, E-mail Server could loop during attempts to process some emails, causing
an increase of logs with exception traces. (ER# 307031651, 308310942)
E-mail Server now correctly sets the options smtp-connection-security
and/or pop-connection-security, and uses the correct default in
the option template. Previously, setting these options incorrectly could result
in failure to connect to the corporate e-mail server, and failure to send email.
(ER# 304305955)
E-mail Server no longer requires increased memory when Configuration Server
contains a large number of objects. (ER# 298464849)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction:
E-mail Server no longer fails to process requests whose size is exactly 65424 bytes. Previously, E-mail Server would time out while attempting to process such requests. (ER# 321572343)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction:
E-mail Server no longer fails while processing emails which contain attached files of size 65536 bytes. Previously, failure occurred when E-mail Server attempted to insert or query email content or attachments of this exact size. (ER# 313806056, 310033725, 307503417)
Note: You must use Universal Contact Server 8.1.200.xx or higher. (ER# 308860704)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction:
The E-mail Server application DBID is now correctly set in log messages to allow raising alarms in Solution Control Interface. Previously, the application DBID was incorrectly set and alarms for E-mail Server were not triggered in SCI. (ER# 311257877)
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 E-mail Server.
Support of secured connection to Interaction Server.
E-mail Server no longer has a dependency on the Java Environment and Libraries for eServices and Universal Contact Server (UCS) components.
E-mail Server now connects to UCS using ESP protocol.
Support of Advanced Disconnect Detection Protocol (ADDP) to UCS.
Support of secured connection to UCS.
This release includes the following corrections and modifications:
You no longer must use the default port on Configuration Server
to enable E-mail Server to support high availability (HA) of Configuration Server
and Advanced Disconnect Detection Protocol (ADDP) connections to Configuration
Server. Now, upon Configuration Server switchover, E-mail Server reconnects
to the identical Port ID name configured in the backup Configuration Server
application. (ER# 282803010)
The timeout for configuration object loading is now configurable by setting
the -Dcfg.psdk.object.timeout property (new name starting from
8.1.1) to the number of milliseconds. (ER# 283890635,
260909085)
In some rare cases, an issue arises for E-mail Server in decoding e-mails with the body in the UTF-7 encoding. Now, when E-mail Server encounters this issue, it builds a wrapping message that includes the un-decoded message content. Previously, E-mail Server exited when it encountered this issue. (ER# 284820012)
When an e-mail has a header Content-Description that is longer
than 256 characters, E-mail Server truncates it and continues normal processing.
Previously in such scenarios, the e-mail could not be inserted in the database.
(ER# 286228993)
E-mail Server now successfully initializes when Configuration Server contains
applications based on new types, which were introduced in Configuration
Server 8.1.100, such as Genesys Administrator Server or Genesys Administrator.
Previously, E-Mail Server might fail to initialize with a NullPointerException
error. (ER# 298240199)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new features or functionality.
This release includes the following correction and modification:
E-Mail Server now successfully initializes when Configuration Server contains
applications based on new types, which were introduced in Configuration
Server 8.1.100, such as Genesys Administrator Server or Genesys Administrator.
Previously, E-Mail Server might fail to initialize with a NullPointerException
error. (ER# 298240190)
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 8.1 release of E-mail Server.
Support of Transport Layer Security (TLS) with Genesys External Services Protocol (ESP)
Ability to configure TLS ports in the Genesys configuration environment
Support of TLS connection to Configuration Server
Enhanced support for chat transcripts:
Reporting in User Data of a list of files that were attached to e-mail interactions
Ability to exclude first name and last name when creating a contact from an incoming e-mail
Option of keeping or stopping the original e-mail after a reply from an external resource
Support for the provision of contact data in the personal part of the e-mail address in web forms, as well as in e-mails
Ability to edit the list of forbidden headers
Configurable masking of values in key-value pairs in E-mail Server logs
Additional operating system support:
This release includes the following corrections and modifications that were made between Release 8.0 or earlier releases and the initial 8.1 release:
E-mail Server now reports a correct autoreply count of zero (0)
in the following scenario:
Previously, in this scenario, E-mail Server attached a wrongly computed autoreply count when it submitted the e-mail to Interaction Server. (ER# 271301394)
As a workaround to a known Java bug (bug ID# 4508058), E-mail Server now
recognizes and skips byte order mark (BOM) characters at the start of UTF-8
text streams. Previously, the BOM remained in the text string and displayed
as a question mark (?) at the start of structured text. (ER# 265447987)
With Universal Contact Server (UCS) connected to an Oracle Real Application Cluster (RAC) database, switching from one node to another no longer occasionally results in duplicated interactions in the UCS database. Previously, duplicate records might have been created because a task was incorrectly released. (ER# 262701171)
If submission of an interaction to Interaction Server fails, E-mail Server no longer becomes caught in a loop as it continually attempts to allocate CPU resources. Previously, E-mail Server might enter a loop when the Interaction Server database was not working properly—for example, when no space was left on the server. (ER# 80270)
This section provides the latest information on known issues and recommendations associated with this product.
If you are running JVM in a version prior to 6u34 and want to use IPv6,
you must set the Netty transport parameter to OIO.
To do this, add the following line to the JavaArgs section
of the JavaEmailServerDriver.ini file:
-Dcom.genesyslab.platform.commons.connection.impl.netty.transport=OIO
E-mail Server may encounter an issue with TLS that is related to the Java issue described at http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=2215658. To avoid this issue, Genesys recommends using either (a) JDK/JRE 1.6.0_45 or higher or (b) JDK/JRE 1.7.0_2 or higher. (ESR-7766)
The underscore character ( _ ) is not supported for host names that E-mail Server connects to. Having this character in a host name can result in unstable behavior, such as inability to connect to the target host. Note that RFC 1123, section 2.1 "Host Names and Numbers" limits host names to letters, digits, and hyphen. If a host that E-mail Server connects to contains underscore in its name, Genesys recommends that you create an alias and change the host name in the Configuration Layer.
E-mail Server can enter a deadlock situation when a new log file is created. This issue is very rare but can occur if the server is undergoing heavy log activity while the new log file is being written or when a new log file name is configured in the log options.
If such a situation occurs, no more logs are written to the file or console,
and the server accepts client connections but does not respond to requests.
In this situation only restarting the server enables it to serve requests again.
As a workaround, disable two of the loggers by adding the following options to the log section:
log/log4j.logger.com.genesyslab.util.log.CustomFileHeaderProvider = OFF
log/log4j.logger.stderr = OFF
| Found In: 8.1.400.10 | Fixed In: |
E-mail Server might enter a deadlock situation when it is connected to Message Server using TLS
and the Platform SDK logger is set to all
(log/log4j.logger.com.genesyslab.platform=all).
When troubleshooting issues that require the Platform SDK logger
to be set to the all or debug level,
Genesys recommends that you temporarily remove the connection to Message Server to avoid such deadlocks.
You will need to restart E-mail Server for this connection change to take effect. (ESR-7797)
| Found In: 8.1.400.10 | Fixed In: |
To use the Exchange Web Services (EWS) connector, you must select JDK 1.7 (or higher when available) when installing E-mail Server. (ESR-7706)
| Found In: 8.1.400.10 | Fixed In: |
When using E-mail Server with the Exchange Web Services (EWS) connector, in the rare case of an e-mail with an HTML part formated as UTF-7 with a Byte Order Mark (BOM) character, an incorrect character may be displayed at the beginning of the text. (ESR-7645)
| Found In: 8.1.400.10 | Fixed In: |
In some Non-Delivery Reports (NDR), Exchange Server puts the wrong address in the to field
of the e-mail header.
(ESR-7406)
| Found In: 8.1.400.10 | Fixed In: |
When E-mail Server is configured in a multi-tenant environment,
it can connect to a backup Configuration Server after switchover only if
the Configuration Server Application object has the E-mail Server
tenant set in its Tenants tab. (ER# 318687174)
| Found In: 8.1.201.05 | Fixed In: 8.1.300.13 |
When E-mail Server has Transport Layer Security (TLS) configured, either as a server on its ESP port or as a client in its connections to UCS and Message Server, follow these steps to enable it as a Windows Service:
Log on as local system
account.Log on as this account and provide the login/password
of a local host user.(ER# 316521457)
| Found In: 8.1.201.05 | Fixed In: 8.1.300.13 |
The Transport Layer Security (TLS) management for E-mail Server as a client of UCS and Message Server is done as described below:
<serial_#>_<host_name>_cert.pem file.<serial_#>_<host_name>_priv_key.pem file.ca_cert.pem
file.(ER# 316521451)
| Found In: 8.1.201.05 | Fixed In: 8.1.300.13 |
This error and exception when E-mail Server connects to LCA...
LCA Channel error: com.genesyslab.platform.management.protocol.LocalControlAgentProtocol@6df86df8@{lca
- tcp://localhost:4999}
com.genesyslab.platform.commons.protocol.ProtocolException: Failed to create
message #41*
...is a minor issue : there is no problem in supervision from SCI. (ER# 316343461)
| Found In: 8.1.201.05 | Fixed In: 8.1.300.13 |
E-mail Server with JDK 1.7 cannot start on 64-bit Windows, because msvcr100.dll
is not found. Workaround: Copy the version of msvcr100.dll that
matches the target platform (64bit or 32bit ). (ER# 316170403)
| Found In: 8.1.201.05 | Fixed In: 8.1.300.13 |
The creation of a file added in the log/trace option is no longer
dynamic. (ER# 315131551)
| Found In: 8.1.201.05 | Fixed In: 8.1.300.13 |
E-mail Server 8.1.2x works only with Universal Contact Server (UCS) 8.1.1x and higher.
| Found In: 8.1.201.05 | Fixed In: |
To avoid E-mail Server duplicating e-mails in the database when a switch of
Oracle RAC node occurs, you must set a longer timeout on the connection
from E-mail Server to UCS
than the one in the Database Access Point (DAP).
To set the timeout in the connection to UCS, please contact the Technical Support.
(ER# 304334929)
| Found In: 8.1.200.09 | Fixed In: 8.1.400.10 |
If Configuration Server contains a large number of configured objects, you
might need to increase allocated memory for E-mail Server. Genesys recommends
the following values based on the number of configured Persons:
You must perform the following steps to increase allocated memory:
emailServer.sh and update both instances
of $JAVACMD -Xmx512M with the recommended value of allocated
memory, for example, $JAVACMD -Xmx1024M.JavaEmailServerDriver.ini and update the instance
of -Xmx512M with the recommended value of allocated memory, for
example, -Xmx1024M.(ER# 298464849)
| Found In: 8.1.000.05 | Fixed In: 8.1.201.05 |
E-mail Server does not support client-side port connection to Configuration Server. (ER# 283107087)
| Found In: 8.1.000.05 | Fixed In: 8.1.201.05 |
Starting with release 8.1.000.05, the timeout for configuration object loading
is no longer configurable; the timeout is set at 2 minutes. Previously,
you could use the -Dcfg.object.timeout property to increase the
value of this timeout. (ER# 283890635)
| Found In: 8.1.000.05 | Fixed In: 8.1.200.09 |
For E-mail Server to support high availability (HA) of Configuration Server
and Advanced Disconnect Detection Protocol (ADDP) connections to Configuration
Server, you must use the default port on Configuration Server.
(ER# 282803010)
| Found In: 8.1.000.05 | Fixed In: 8.1.200.09 |
Do not set both the enable-ssl and enable-starttls
options (pop-client and smtp-client sections) to true.
Having enable-ssl set to true creates an encrypted
connection from the start, which makes an enable-starttls connection
impossible. (An enable-starttls connection must start with an unencrypted
connection, after which the socket connection is encrypted.)
Note: Both enable-ssl and enable-starttls
have been retired but are still supported for backwards compatibility. The new
options pop-connection-security and smtp-connection-security
are now used for encryption management.
(ER# 294454004)
| Found In: 8.0.200.03 | Fixed In: 8.1.200.09 |
Genesys Agent Desktop does not display images in HTML e-mail. A red x
is displayed, and the image appears as a link at the end of the e-mail. (ER# 195952111)
| Found In: 7.6.100.07 | Fixed In: |
By design, E-mail Server does not support HTML with embedded objects. E-mail Server treats these objects as attachments. (ER# 211078869)
| Found In: 7.6.000.09 | Fixed In: |
E-mail Server does not support processing of inline text/xml. E-mail Server functionality such as classification and redirect cannot be done with inline text/xml. (ER# 152217106)
| Found In: 7.5.000.11 | 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.
AIX 5.3 and RHEL 4.x are no longer supported.
| Discontinued As Of: 8.1.400.10 |
AIX 5.1, AIX 5.2, and Solaris 8 are no longer supported.
| Discontinued As Of: 8.1.000.05 |
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.
The following are accessible directly from the eServices product page on the Genesys Documentation website:
eServices 8.1 Deployment Guide describes deployment procedures for all eServices components. It also contains a high-level description of the eServices system, its architecture, and a list of new features in the current release.
eServices Administrator's Guide presents recommendations for monitoring and adjusting your eServices configuration, plus detailed explanations of procedures to use for selected special purposes.
eServices Knowledge Manager User's Guide provides information about Genesys Knowledge Management, including category structures, standard responses, and screening rules, as well as the natural language processing functionality optionally available as Genesys Content Analyzer.
eServices Interaction Properties Reference Manual provides information about the key-value pairs that represent properties of eServices interactions.
eServices Integrated Capture Points Guide provides information on configuring and using integrated capture points, which are a feature of Interaction Server providing a mechanism for capturing new interactions from external source systems, and for issuing requests to existing interactions.
eServices Multi-tenancy and Load Balancing Guide provides information on configuring multi-tenant environments and on load balancing among multiple instances of certain eServices servers.
eServices Social Media Solution Guide describes deployment and use of the Genesys Social Messaging product.
eServices 8.1 Reference Manual provides a reference listing of all configuration options and of field codes used in standard responses.
eServices 8.1 Web API Client Developer's Guide describes the structure of the Web API, explains the Simple Samples, and describes procedures for customizing them.
eServices (Multimedia) 8.0 Selected Conceptual Data Models for the UCS Database describes a portion of the Universal Contact Server (UCS) database.
8.1 Universal Contact Server Manager Help is a guide to the Universal Contact Server Manager user interface.
eServices 8.1 Knowledge Manager Help is a guide to the Knowledge Manager user interface.
The following are also accessible on the Genesys Documentation website:
For a listing of classes, methods, fields, and constants of the Web API portion of the Web API Server component, see:
Universal Routing 8.1 Interaction Routing Designer Help is a guide to Interaction Routing Designer, including the portion of it that designs interaction workflows and business processes for eServices.
Universal Routing 8.1 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 eServices.
Genesys Events and Models Reference Manual includes a set of basic interaction models, showing the components involved and the event messages sent among them. For authoritative description of the event messages, see the next item.
Genesys 8.1 Security Deployment Guide describes the deployment and configuration of some of the security features provided in Genesys software.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, 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.