Release Advisory
Composer
8.1.x
Genesys Telecommunications Laboratories, Inc. ©2011–2014
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.
Link to 8.0 Product Release Advisory
The following information applies to the Genesys 8.1.x software
and is important for you to note:
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.
To obtain the full functionality of Composer 8.1, the following Genesys products/software components are required:
- Orchestration Server 8.1.4 or later for developing and running SCXML session-based applications.
- Composer 8.1.4 and Interaction Server 8.5.1 are required for enhanced pulling of multimedia interactions. While other eServices components can be 8.1 Genesys recommends that other eServices be 8.5.0 or later.
- Genesys Voice Platform (GVP) Media Control Platform 8.1.6 or later for testing and running VXML applications.
- Genesys Configuration Server 7.5or later for support of eServices capabilities.
- If you wish to use the Context Services capability of Universal Contact Server, you will need Universal Contact Server 8.1.000.10 or later.
- If you wish to use Outbound Campaigns, you will need Outbound Contact Server 8.1.100.09 or later.
- If you wish to use Business Rules, you will need Genesys Rules System 8.1.0 or later for business logic, which can be customized, and then invoked by VXML and SCXML applications.
For information on components required by Orchestration Server, such as eServices components for processing multimedia interactions, see the Orchestration Server documentation.
User Data does not become available to a routing application immediately after the application sets the data (for example, provides some key-value pairs to the setuData() function in an ECMAScript block). There is a delay of several seconds, after which the User Data can be successfully queried again in the application. The Pause Treatment can be used to introduce this delay.
Top of Page