Release Note

Contents

Introduction

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.genesyslab.com for more details.

This release note applies to all 8.0 releases of Composer, an Integrated Development Environment used to develop applications for Genesys Voice Platform (GVP) and the Genesys Universal Routing Platform with its Orchestration and Universal Routing Servers. The previous version of this product was known as Composer Voice, as it was used only to develop voice applications for GVP.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Manual.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see the Read Me. Please contact your technical support representative if you have any questions.

Supported Operating Systems

New in This Release

This is a hot fix release for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction/modification:

When using the Subdialog block, Composer can now properly handle more than 14 subdialog parameters. (ER# 289809621)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Composer.

• Building on the Context Services blocks introduced in Composer 8.0.3, this release includes additional blocks for managing customer conversations. The following new Context Services blocks are available for SCXML applications: Create Customer, Start Task, Complete Task, and Query Tasks.

• The following Context Services blocks are now available for VXML applications: Start Service, Complete Service, Associate Service, Query Services, Enter State, Complete State, Query States, Start Task, Complete Task, Query Tasks, Create Customer, Identify Customer, Query Customer, Update Customer.

• This release adds support for multi-valued Context Services extension data, which is applicable to all Context Services blocks.

• You can map returned data to application variables for the following VXML/SCXML Context Services blocks: Query Customer, Identify Customer, Query Services, Query States, and Query Tasks.

• Additional VXML schemas can be added into Composer and used in namespaces for new VXML files created through Composer's VXML editor.

• The Set Call Result block for voice applications allows tagging of calls with SQA call status (success, failure).

• The Disconnect block adds a Reason field. The content can be either an ECMAScript expression created in Expression Builder or free-form text.

• New features move Composer to closer to parity with Universal Routing's strategy creation tool, Interaction Routing Designer (IRD)for building routing strategies for inbound voice interactions:

• A new Routing Rule block provides the ability to use routing rules for target selection, which were previously created through IRD and stored in the Genesys Configuration Database. Supported routing rules include load balancing, percentage allocation, and statistical routing.

• A new Force Routing block provides support for force-routing of inbound voice interactions.

• The Target block, used for routing voice interactions, adds new properties to support building conditional expressions, such as those used for share agent by service level agreement routing. A new Threshold property allows you to build threshold expressions, which can use relational operators, user-defined variables, and the following URS threshold functions:

• sdata for routing conditions based on statistics
• acfgdata for routing conditions based on data stored in Configuration Server Application objects
• callage to return the age of an interaction
• lcfgdata for routing conditions stored in Lists objects

• The Target and Route Interaction blocks add a Priority property, which lets you select a variable containing an expression returning the priority that the interaction will be given in the queue.

• The Branching block now supports segmenting incoming interactions based on call type and/or media type.

• The ECMAScript block (through Expression Builder) exposes the following functions:

• findServiceObjective, which can find/retrieve a Configuration Server service objective for a given combination of Customer Segment, Service Type, and Media Type.
• priorityTuning, which can adjust the priority of an interaction by taking into account age, expected wait time, and service objective.

• The User Input block adds support for verify digits, retry, success case, and failure case prompts.

• Voice Treatment blocks are added/enhanced:

  • The Pause block can be used to insert a pause between treatments.
  • The Create User Announcement block can be used to record an announcement from a user (supports multiple prompts).
  • The Delete User Announcement block can be used to delete an announcement from the Create User Announcement block, possibly in a different workflow.
  • The IVR block may be used to send an interaction to an Interactive Voice Response unit. It has both Compatibility and Non-Compatibility modes to support, for example, specifying a remote resource to be used for a treatment.
  • The User Input block adds support for verify digits, retry, successcase, and failure case prompts.
  • The following Voice Treatment blocks add Wait for Treatment End and Request ID properties: Play Application, Play Message, and User Input.

• The Target block is enhanced to display a busy treatments output port, which can be connected to treatment blocks, such as Play Application, Play Message, Play Sound, and User Input.

• Additional features for routing of non-voice interactions:

• Workbin blocks can be added to interaction process diagrams. The Workbin block, representing a temporary storage area for interactions, can be associated with agents, agent groups, places, or place groups. You have the option to define one or more views for a workbin, which define the conditions for extracting interactions and directing them into workflows.
• The SMS block allows you to specify pre-written text for the content of the SMS.
• The Route Interaction block adds a Workbin Name property. Its value will be used as the workbin for targets specified in the block.

• Other New Features:

  • In cases where the DB Data block returns multiple records, a new Looping block, available for both callflows and workflows, can loop through all the records. For each iteration of the loop, mapped variables can be populated with the values of the next record.

  • You can now save a callflow or workflow diagram as a template and have it appear on the list of available templates when creating a new diagram. Diagrams saved as templates can be exported to/imported from the file system.

  • When defining a database connection profile, you can enable connection pooling, which maintains a set of database connections that can be reused for requests to databases. You can use this feature to enhance performance by avoiding time-consuming re-establishment of connections to databases.

  • When defining the languages an application supports, you can now define custom locales. Also, new additional Composer-defined locales are introduced: Hong Kong Cantonese, English-Irish, English-India, English-Scottish, Mexican-Spanish, Icelandic-Iceland, Thai-Thailand, Bengali-India, Spanish-Argentina, United States-Spanish, Gujarati-India, Kannada-India, Malayalam-India, Marathi-India. Oriya-India, Punjabi-India, Tamil-India, Telugu-India.

  • A new Composer 8.0 Routing Applications User’s Guide, available on the Genesys documentation library DVD, introduces first-time Composer users to the GUI, interaction process diagrams, and workflow diagrams.

Corrections and Modifications

This release includes the following corrections and/or modifications:

In this release of Composer, applications using the DB Data block and Backend block in callflows POST data as multipart/form-data <data>. In the previous releases, applications using the DB Data block sometimes had increased latency during runtime when Next Generation Interpreter (NGI) on GVP's Media Control Platform used HTTP/1.1 and an HTTP/1.0 proxy, such as Squid. (ER#  245039961)

The Query Builder now displays all objects accessible to the specified user. In earlier versions of Composer, it showed only objects that were owned by the user. (ER#  252868115)

Empty results returned by Stored Procedures are correctly handled by the DB Data block for .NET Composer Projects. In earlier versions, an exception was returned. (ER#  253951459)

Composer uses the gvp: prefix for Genesys VXML extension tags instead of genesys:. The VXML editor schema is updated to allow langexpr in the <prompt> tag. This caused a validation error in earlier versions of Composer. (ER#  252456346)

System variable values can be edited in callflows and specified as expressions using Expression Builder, which was not possible in earlier versions. The usability of the Entry block variables dialog is improved. (ER#  253912351)

In previous versions of Composer, VXML pages containing special characters would cause an error dialog to pop up when debugging. This behavior is now fixed as UTF-8 encoding is used when communicating with GVP. (ER#  251509894)

Callflows blocks that have the Prompt property are enhanced to allow specifying values of individual Prompt items as expressions in Expression Builder, including array elements. In earlier versions of Composer, only variable names could be specified in addition to literal values. (ER#  259347871)

In this release of Composer, the compiler will include libraries from a Project's WEB-INF/lib directory. Previously, libraries from the *.JAR files from the Project's WEB-INF/lib directory were not included during *.JSP files compilation and errors were shown in the JSP editor. (ER#  247823946)

Properties specified in the DB Data block are now retained when the block is saved as a Custom Tool. In earlier versions, not all block properties were carried over to the Custom Tool. (ER#  258682561)

You can no longer select Delete Interaction when Notify UCS is selected in the Stop Interaction block. In the previous release, the selection of both Notify UCS and Delete Interaction did not function and the interaction would not be deleted from UCS. (ER#  248489161)

Composer now correctly treats the input parameter for the _genesys.ixn.setuData() function as an Object. In previous releases, the input parameter was embedded inside single quotes to mark it as a String. (ER#  246887111)

The External Service block now supports passing user data to the ESP method. In previous releases, ESP methods that required user data could not be used with the External Service block. (ER#  246933472)

When a validation error on the username field for a Custom Event for an Exception property occurs, the OK button is now properly enabled. In previous releases, the OK button was non-functional. (ER#  247467686)

When connecting to Universal Contact Server results in an error, the error message is no longer misleading. The error message is updated to: Cannot select values from Universal Contact Server because it is not connected or an error occurred. (ER#  247945860)

When using the Target block, an error is displayed when the Use Treatments flag is true and busy treatments are not specified. Previously, a validation error was not displayed.(ER#  246781841)

Composer now deletes all links from the Media Server block when a different Application object is selected. In previous releases, the links relating to the previously selected Application object would be displayed even after the Application object was changed. (ER#  247524821)

Generating code for an IPD now results in one file for each interaction queue connected to an endpoint and standalone (voice) workflow. In previous releases, when at least one interaction queue was connected to an endpoint, SCXML file(s) were not generated for workflows. (ER#  247987101)

Composer now validates variable references specified as parameters. In previous releases, if a variable was specified as a parameter for a SubRoutine block and later deleted, a validation error was not displayed. (ER#  248073837)

Composer now displays an error message when the Project name in the wizard is the same as an existing project. In the previous releases of Composer, an error message was not displayed when an existing project name was specified. (ER#  235596791)

When validation results in block-specific errors, error markers now correctly appear on both file names as well as on blocks in the diagram view. In the previous releases during a save, validation errors did not result in markers being shown on blocks. (ER#  227360698)

Outlinks originating from the Entry block cannot be renamed or assigned a name through the Properties view. There is no workaround. (ER#  227094725)

In this release of Composer, automatic text wrapping is supported for diagram notes, text, and note attachments. In previous releases of Composer, after keying in text, you needed to manually resize (increasing the height), at which point text wrapping worked correctly. (ER#  222450995)

The Grammar Menu block is now able to select Gbuilder files. In the previous releases, the Grammar Menu block did not check for the presence of .grxml files exported from its associated Gbuilder file. (ER#  215507361)

The Subdialog block's property page popup for the URI property now functions properly when maximized. In the previous release of Composer, when maximized, the Properties view did not function properly when working with blocks with popup property pages. (ER#  216609158)

The Save As option now properly saves diagrams. In the previous releases of Composer, using the Save As function would result in a copy of the diagram that caused code generation would fail. (ER#  169842128)

Top of Page

Supported Operating Systems

New in This Release

This is a hot fix for this product. Refer to the Deployment Procedure for this hot fix to deploy the installation package within your environment. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following correction and/or modification:

When using the DB Data block to connect to and query information from an Oracle database, connection pools are now re-used instead of being destroyed with each query. Previously, some connections would remain in the TIME_WAIT state and, over time, exhaust the number of allowed Oracle connections. (ER# 251810914)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Composer.

• Context Management Services Support—This release begins support for the Context Management Services capability of Universal Contact Server and the Universal Contact Server (UCS) Database, a repository of customer-related, service, and interaction-centric data (current and historical). The primary purpose of Context Management Services is to personalize/orchestrate service delivery to customers and to enhance reporting capabilities. If Context Management Services capability is enabled at your site, you can create SCXML-based applications that extract customer data elements from the UCS Database and apply this knowledge during the routing of interactions or as part of a self-service application. New blocks allow you to create workflow applications that:

  • Identify customers and update their profiles.
  • Extend customer profiles with user-defined information.
  • Query a customer's profile.
  • Associate services with customers.
  • Create/start/complete customer services.
  • Query customers' active services.
  • Enter and complete service states.
  • Query service histories.
  • Query active and completed service states.

• A Context Management Service Project template is included with this release.

• Multimedia Processing Support—This release also begins support for SCXML-based routing workflows that process multimedia (non-voice) interactions. New multimedia processing blocks let you define workflows that:

  • Create an outbound e-mail.
  • Perform various types of processing on e-mails including sending.
  • Route a multimedia interaction to a target.
  • Place a multimedia interaction in a queue.
  • Invoke functions through Genesys External Service Protocol.
  • Create, process, and send a Short Message Service text message.
  • Send Stop processing information for an interaction to Interaction Server and update the Universal Contact Server Database.

• Project templates are provided demonstrating how to create multimedia workflows.

• Interaction Process Diagrams —Composer introduces a new type of diagram, used for both voice and multimedia interaction processing, called an interaction process diagram (IPD), which creates the starting SCXML page for a routing application. When used for multimedia workflows, IPDs can move interactions from media servers (such as E-mail and SMS) to queues, pull interactions from queues, and submit interactions to workflows for specific types of processing. The following new blocks support processing interactions with IPDs:

  • Interaction Queue block for defining new queues in the Configuration Database.
  • Media Server block for getting interactions from media server endpoints into the IPD.
  • Workflow block for specifying workflow resources, such as a workflow diagram or SCXML file.

• Project templates are provided demonstrating the use of IPDs.

• A new type of variable, called a Project variable, allows you to share information across different workflows.

• This release also contains some minor enhancements for voice callflow / VXML development:

  • Example VXML code template as an example of how to handle N-Best results.
  • All Composer blocks that support prompts now support RTSP URIs.
  • The Help documents how to create and import prompts as per the Prompt Manager export specifications.
  • A new Entry block property allows suppression of data within the Nuance 9 platform ASR logs.
  • Non-numeric strings can be dialed for transfer destinations.
  • Support for the Call Progress Analysis/AMD on transfer feature using the Genesys media server, third party media gateways, and the PSTN Connector.
  • Support for the AT&T blind transfer with the following options:
  • Out of Band Courtesy
  • Out of Band Consult
  • Out of Band Conference

• Other
  • Documented ability to hide file types in Composer's File > New menu.
  • The Help documents how to create and import prompts recorded as per the Prompt Manager export specifications.

Corrections and Modifications

This release includes the following corrections and modifications:

Java Composer Projects can be deployed to any web application server that meets the following minimum pre-requisites:

• Application server should be J2EE 5 compliant
• Support for the JSP 2.1/Servlet 2.5 specification

For applications using multi-byte characters such as Hebrew, the GVP Debugger now properly debugs the application. Previously, the debug call would be properly set up and executed, but it would not be possible to step through the application or set breakpoints. (ER# 241054794)

Generated .sql files become visible automatically in Project Explorer. In previous versions of Composer, the Project Explorer had to be manually refreshed to see the newly generated .sql files. (ER#  226754715)

Prompts Manager view is correctly hidden when Composer Voice capability is switched off. In earlier versions of Composer, Prompts Manager view was always accessible. (ER#  228059269)

Project files remain in sync with the file system after a Project upgrade. If another upgrade is attempted, Composer correctly shows that the Project or diagram is up-to-date. In earlier versions, a manual refresh was required to get the Project files in sync with the file system. (ER#  231077681)

Newly added files or generated files become visible immediately in Project Explorer. In earlier versions of Composer, in certain cases, a manual refresh of Project Explorer was required to view new files. (ER#  224805101)

Migrating a Project no longer overwrites the connection.properties file in the db folder of the project. In previous versions of Composer, this file was incorrectly overwritten and had to be restored from a backup. (ER#  223467628)

Subfolders under the Resources folder no longer have a JS icon. In earlier versions of Composer, a JS icon was incorrectly used for these subfolders. (ER#  224871851)

Using the Web Service block in a .NET Composer Project correctly passes input parameters to the Web Service if an input parameter contains an array or a complex object in JSON format. This did not work in earlier versions of Composer. (ER#  235610823)

The Web Request block now supports parameters with hyphens "-" in their names. In earlier versions of Composer, such parameters could not be used. (ER#  235323181)

Web Service block properties can be modified repeatedly as needed. In earlier versions of Composer, the Service URL property had to be cleared out to set properties again. This is no longer required. (ER#  235624241)

For applications using multi-byte characters such as Hebrew, the GVP Debugger now properly displays the characters in the Call Trace view. Previously, the displayed characters would be incorrect. (ER#  240373426)

The AppState variable is now displayed properly in the GVP Debugger. Previously, the AppState variable would not display the individual callflow variables separately, and instead it would be shown unparsed as a JSON structure. This would happen when multiple variables had the same complex value, such as an identical structure. One scenario this might occur is when a Backend block was used with PassState set to true, and a complex result was returned from a DB Data query. (ER#  241016033)

Code generation no longer fails if a variable is not specified in the Output Result property of the Web Service block. In earlier versions of Composer, this caused an error and code generation would fail. (ER#  235630891)

Global commands in the Entry block and Menu options in calflows were enhanced to allow the DTMF option to be entered with more than one (1) DTMF. Previously, only a single DTMF could be selected. (ER#  247762701)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This release includes the following usability modifications:

• Expression Builder for the Assign block indicates the name of the variable being assigned.
• Users are notified if their connection to Configuration Server is lost.
• The Import/Export Custom Tooling menu item is renamed to Import/Export Custom Blocks.
• Import and export block help topics are easier to find.
• The _COMPOSER_WSSTUBBING variable is created automatically and does not require manual creation to enable the Web Service stubbing feature.
• Diagram variable creation and viewing is now accessible via the toolbar and also in the Assign block.
• The List Object Manager and Statistics Manager views are now accessible under Windows > Show View without having to go to Windows > Show View > Other.
• The Branching block icon color is changed to make it more prominent with the default pane color.
• When connecting to Configuration Server, an unsuccessful login now triggers an error message. Also, entering non-numeric characters for the port will not freeze the dialog box.

Corrections and Modifications

This release includes the following corrections and modifications:

You can no longer select shadow variables as return values in the Exit block. Previously, shadow variables were incorrectly available as return values in a callflow's Exit block(s) and, if selected, resulted in semantic errors in the generated VXML. (ER# 229011211)

Renaming List objects created via the List Objects Manager view is now possible without specifying a value for the Description field. Previously, the rename operation would fail if the Description field was left empty. (ER# 229412551)

References to invalid URLs starting with http://portal.genesyslab.com/dir/engineering are now removed from notes inside diagrams of project templates. (ER# 232013991)

Composer now properly handles global commands that are triggered via numeric DTMF when they interrupt prompts that are set with Immediate playback set to true. Previously, rootmap was ignored when the DTMF option was set to 1~9. (ER# 230102731)

Adding more than eight (8) variables in the Set Call Data block and clicking on the OK button now displays a validation error stating that a maximum of eight (8) variables are allowed. Earlier releases of Composer allowed more than eight variables to be specified. This resulted in the dialog not providing a default name for the additional variables and no visual indication about the presence of additional variables. (ER# 231158331)

Composer now correctly handles WSDL types referencing another definition with the same name. Previously, when WSDL types were defined with a reference to another definition with the same name, the WSDL parser caused a stack overflow. (ER# 230764647)

You can now enter non-English characters in the Menu block. Previously, validation would fail when non-English characters were entered. (ER# 235664066)

Composer now supports response data for Web Requests in JSON format. Input parameter values are URL-encoded in the Web Request block for voice or routing applications. In previous releases, response data in JSON format generated an error. (ER# 231231761)

The DB Prompt block is enhanced to allow specification of prerecorded prompts. This includes text as well as several standard data types as well as the capability to play DB Column values in one of the supported standard formats, such as Currency and Date. Values in each record can now be played in a customer-specified order determined by prompt order. Previously, the DB Prompt block would speak out all columns for each record returned by the database as the result of a query. The ordering of columns could only be controlled using a custom query. (ER# 214307377)

Composer Help is corrected to remove the text referring to raw audio .wav support in Prompts Manager. The help now correctly states support for .vox files. (ER# 231902091)

Reordering of prompts via Prompts Manager now works properly. In previous releases of Composer, to reorder prompts, you needed to directly change the Prompts field of the relevant block as it was not correctly handled via Prompts Manager. (ER# 228871706)

Composer Help is updated to include instructions on configuring Composer to validate the currently open diagram instead of all the diagrams in all Projects of the workspace. (ER# 224406070)

Top of Page

Supported Operating Systems

New in This Release

There are no restrictions for this release. This section describes new features that were introduced in this release of Composer.

This release of Composer is compatible with Universal Routing 8.0. It provides the following routing strategy ("workflow") development features, including:

• Authoring of workflows through a drag-and-drop visual designer or direct creation and editing of SCXML files. Universal Routing Server (URS) 8.0 is required to execute these workflows. The following categories of blocks for creating routing applications are provided: Flow Control, Routing, Voice Treatment, and Server Side.
• Workflow samples demonstrate segmenting interactions, target selection, percent allocation, statistical routing, web requests, and other functionality.
• Global exception handling, which is available through the Entry block of a workflow.
• An Expression Builder with syntax checking for creating expressions (for both workflows and callflows), which can then be used for branching and routing decisions. The Assign, Branching, and ECMAScript blocks access the Expression Builder.
• A Skill Expression Builder with syntax checking for routing based on the value of a skill expression. Routing can also be based on the value of a statistical expression.
• A List Objects Manager to create, for example, lists of 800 numbers that can be accessed by workflows. Key-value pairs can be specified in List elements. List objects are stored in Configuration Server and can be retrieved by a strategy/workflow at runtime.
• A Statistics Manager and Builder, which lets you create custom statistics from the URS predefined statistics. The ability to use the URS predefined statistics in a workflow is also provided.
• A URS Debugger for workflows, which opens a direct TCP connection for simulating calls and interacting with URS. A new perspective, URS Debugging, optimizes screen layout for debugging workflows.
• A new Composer Design perspective, which provides an interface that facilitates the creation of both callflow and workflow diagrams.
• The ability to write ECMAScript within a workflow, to be executed by an application server during runtime. Examples of how ECMAScript can be used include conditional routing, data type, and string manipulation functions. ECMAScript expressions can be created using the Genesys-supplied Functional Modules described in the Composer Help book, Universal Routing 8.0 SCXML Reference.
• The ability to connect to Genesys Configuration Server during design time, to access and validate specific Genesys configuration objects that are referenced in workflows. Composer also supports working in an offline mode, when it is not connected to Configuration Server.

This release of Composer is compatible with Genesys Voice Platform (GVP) 8.1 release features. It includes the following new features for voice applications:

• You can select the default and active locales to use for a project when creating a new project through Composer’s Project wizard. This will drive the available locales within Composer’s Grammar Builder and Prompts Manager. Additional locales may be added to the project at any time.
• Import and export of Composer projects as well as individual routing strategy files is supported.
• Full support for migrating/upgrading 8.0.1 Composer Voice Projects and callflow diagrams.
• The ability to create and then import and export custom blocks.
• You can now start and stop the bundled Tomcat server from within Composer.
• Support for catching error.com.genesyslab.subdialog.maxdepthexceeded.
• Support for catching Call Progress Analysis events through custom event handling.
• Support for offboard Dual Tone Multi-Frequency (DTMF) signal recognition.
• A new Prompts Manager perspective makes it easier to review prompts for any application.
• A new preference for prompt validation indicates if a validation check for missing prompts must be enabled.

The following new features apply to both voice applications and routing strategy workflows:

• Web services stubbing, which allows you to work with Web Services in an “offline” mode when you do not have access to the Web Service itself or if the Web Service is under development (used for both routing and voice applications).
• A new Query Builder for use with the DB Data block, in both voice application callflows as well as routing strategy workflows.
• You can now visually work with and execute database stored procedures in the DB Data block.
• You have the ability to hide voice application and/or routing workflow development capabilities through a Composer preference setting.
• Keyboard navigation in all dialogs. User entry forms and keyboard mnemonics/hot keys are provided for common tasks.
• Block look and feel has changed to make it easier to visually identify blocks.
• Support for defining custom events.
• HTTPS support is provided for the Web Services and Web Request blocks.

Corrections and Modifications

This release also includes the following corrections and modifications:

Renaming a callflow that is open in the diagram editor and has unsaved changes now displays a prompt to save or discard changes before renaming. If you select Save, Composer saves the changes and then renames the diagram. This ensures that unsaved changes are not lost in the renaming process, which could happen in previous versions of Composer. (ER# 213201511)

When exporting a Java Composer project to a WAR file, Composer generates SQL files from DB Data blocks. In the previous version of Composer, a code generation step was required to generate SQL files. This step is no longer necessary. (ER# 213429594)

A sample application, now available as a project template, demonstrates how data retrieved from a database using the DB Data block can be played using the Prompt block. This enables the retrieved data to be interpreted and played in various formats; for example: currency, number, date, and so on. This functionality was possible in the previous version of Composer, but was not clearly documented. The newly-added sample application provides additional clarity. (ER# 214492603, 214467878)

The visual database query builder now supports working with tables and table columns that have a space in their name. (ER# 214467872)

If no data is returned as part of a database query operation, the DB Data block throws a dbemptyresultset exception. It also provides an option to suppress this exception if required, such as for stored procedures that do not return records. Previously in such a scenario, the DB Data block did not throw an exception. (ER# 217123017)

Top of Page

Supported Operating Systems

New in This Release

This release is under shipping control. This section describes new features that were introduced in this release of Composer Voice.

This release of Composer Voice is compatible with Genesys Voice Platform (GVP) 8.1 release features, including:

• New and updated application blocks, such as CTI blocks, to work with CTIConnector
• Option to suppress sensitive information in GVP metrics and logs
• Full call recording blocks, ASR engine release block

This release of Composer Voice provides new application development features, including:

• New .NET Voice Project type, targeting ASP.NET/C# for server-side development
• Prompt Editor for reviewing and managing prompts, including playing and recording audio files in formats supported by GVP
• Grammar Builder for visually creating grammars and working simultaneously with multiple locales
• Code simulation view
• Additional debugging information available in exceptions
• Support for working with databases through a set of new database blocks and a visual query builder
• Support for additional web servers/application servers: JBoss 4.2.3, IBM WebSphere 6.1, Microsoft IIS 6.0, Microsoft IIS 7.0, and Tomcat 6.0 on Red Hat Linux. Note: Starting with Release 8.0.301.81, Genesys no longer certifies Composer with specific web application server vendors and versions.
• Automated migration and archival of Composer Voice 8.0 projects

This release of Composer Voice also provides user assistance features, including:

• New sample applications and cheat sheets
• Updated context-sensitive Help System integrated within Eclipse Help
• VMware support

Corrections and Modifications

This release also includes the following corrections and modifications:

This release of the Composer Voice Visual Designer now provides blocks for Full Call Recording (Start FCR and End FCR blocks). In the previous release, if a voice application needed to use Full Call Recording, custom code had to be written in the VXML Editor. (ER# 191977552)

This release of Composer Voice fixes a problem related to incorrect mapping of Web Service output key responses to separate variables using the Map Output Values to Variables property. Composer Voice now properly encodes the file name prior to its being used to create an input stream. In the previous release, this problem could have occurred when the Map Output Values to Variables property was set to true. (ER# 191370766)

This release of Composer Voice substitutes the %20 encoding for the space character (which is supported in GVP), in place of the + encoding (which is not supported in GVP). This allows test calls to function in Voice Project names that contain spaces. (ER# 194202243)

This release of Composer Voice automatically undeploys deleted Java Voice Projects and attempts to deploy Java Voice Projects that are not already deployed. This change applies to project renaming situations as well. In the previous release, if a Java Voice Project was renamed, you had to reprovision the Java Voice Project manually in order to make test calls. (ER# 194134262)

This release of Composer Voice now performs callflow validation when the Validate option is accessed by right-clicking a file name from within the Project Explorer. In the previous release, this option did not function and you had to use the Validate option from the Diagram menu or the Validate toolbar icon. (ER# 193499151)

Eclipse 3.4, the Eclipse release on which this release of Composer Voice is based, fixes an error that occurred when you opened more than two instances of a VXML, CCXML, or GRXML file from the History window. In the previous release, files opened in text mode only. (ER# 171109266)

In this release of Composer Voice, watch expressions are now created from the Variables window in the VXML Debugging perspective with the appropriate AppState. prefix. In the previous release, you had to create watch expressions manually and prepend AppState. to the desired variable name. (ER# 191088123)

This release of Composer Voice provides a sample application demonstrating usage of Hotword support in transfers. (ER# 189037481)

In this release of Composer Voice, context-sensitive help/validation now works properly in the Composer Voice XML Editors when opening imported VXML, CCXML, or GRXML files. In the previous release, context-sensitive help/validation only worked properly if the schema name was set in the top-level <ccxml>, <vxml>, or <grammar> tag. (ER# 175177135)

In this release of Composer Voice, generated code now works properly in the Subdialog block if the Location Type is URI and the path is a static value. (ER# 194549661)

In this release of Composer Voice, instructions for installing, configuring, and using ClearCase plug-ins are provided in the Composer Voice 8.0.1 Help system. (ER# 187537206)

Top of Page

Supported Operating Systems

New in This Release

This is the first release for this product. This release is under shipping control. This section describes new features that were introduced in the initial 8.0 release of Composer Voice.

• Graphical designer for building VoiceXML applications with undo and redo support
• Rich palette of pre-built components, including server-side blocks for invoking business logic, web requests, and SOAP- and REST-based web services
• Full Project Management capabilities for managing all the files in an application, such as callflow files, audio, video and grammar resources, hand-coded VXML pages, and server-side logic pages
• Integrated real-time debugger for graphical callflows and VoiceXML with the ability to add breakpoints, monitor watch variables, perform single-step debugging, view call traces, and execute ECMAScript
• Callflow annotations and error indicators
• Full-featured Java Server Page (JSP) editor
• Full-featured CCXML 1.0 and VoiceXML 2.1 editors with context-sensitive help
• GRXML 1.0 development editor with context-sensitive help
• Bundled Tomcat 6.0 for testing and debugging applications
• Voice Application Reporter palette objects for transaction reporting
• Ability to build IVR-controlled and URS-controlled SIP Server-based CTI applications
• Easier to load balance applications, as all session states are stored on the VXML Browser side with the ability to pass state to the server-side logic pages
• Customizable code template library for CCXML, VXML, and GRXML editors
• Ability to raise SNMP traps by the VXML application

Corrections and Modifications

This release includes the following corrections and modifications:

No corrections or modifications have been made in this release.

Top of Page

Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.

The database connection profiles editor may show errors for correctly specified profiles if one or more profiles contain errors. If the editor is closed while errors still exist, these errors are not shown when the editor is re-opened. Workaround: Fill out required parameters for all profiles and save the file before closing the editor. (ER#  262234521)

In Windows 7, the Welcome screen is not displayed when Composer is first launched. Instead, the Overview page is shown. Workaround: Click Help > Welcome to access the Welcome page. (ER#  258854811)

The Log block for Callflows does not show a validation error if logging details are not specified. Workaround: Specify logging details. (ER#  253689341)

Query Builder and Stored Procedure Helper dialogs of the DB Data block do not provide an option to create new variables. Workaround: Create variables using the Entry block or Access Diagram Variables button on the toolbar. (ER#  258598836)

If Oracle Client Components are not installed on the application server machine, the runtime error is not handled gracefully. The root cause is a malformed JSON object. Workaround: None required. Install Oracle Client Components before running the application. (ER#  257973582)

Voice application projects in Composer contain a Workflows folder but not an Interaction Processes folder. Workaround: If required, create the Interaction Processes folder manually before adding an interaction process diagram to the project. This will be needed only if routing ability needs to be added to the project. (ER#  261882371)

The database connection profiles editor does not allow saving the file due to validation errors if a profile is deleted. Workaround: Close the editor and open the connection.properties file using a text editor. Right-click on the db/connection.properties file in the Composer project and select Open With > Text Editor. Remove the lines that start with the profile’s name. The database connection profiles editor can then be used to add or modify connection profiles (ER#  262234523)

Context-sensitive help may not bring up the correct block topic for certain Workflow blocks. Workaround: Search for the block name in help and click on the specific block topic. (ER#  262019584)

Published objects in Configuration Server are not deleted if a Composer project is deleted. Workaround: Delete the objects manually before deleting the project. Object names are shown in block properties in the interaction process diagram. (ER#  257981054)

An Out of sync error dialog is displayed if interaction process diagram-published information is reset and the diagram is open. Workaround: Dismiss the error dialog, click the Interaction Processes folder in Project Explorer and type F5 to refresh. (ER#  262301985)

Installation of third party plugins may fail on Windows 2008. The error Cannot complete the install because one or more required items could not be found is displayed. Workaround: Add the update site http://download.eclipse.org/releases/galileo/ to the list of available software sites. Name it Galileo. Try installing third party plugins again. Any dependencies will now be downloaded from the Galileo site. (ER#  2622590910)

The DBData block does not support accessing stored procedures using synonyms. Stored procedures must be accessed directly using their names. (ER#  258082401)

Prompt functionality for callflows supports specifying only one noinput or nomatch prompt for each retry prompt. Multiple prompts cannot be specified. As a workaround, Text to speech text can be prepared in a single variable and used for the single prompt. (ER#  255440957)

An interaction is sometimes not deleted on Universal Contact Server (UCS) when the Stop Interaction block is used and the option to notify UCS to delete the interaction is selected. This occurs when an e-mail or SMS message was created and an explicit Send Email or Send SMS block is used to send the interaction. As a workaround, do not use an explicit Send block by setting Create New Interaction to false in the Create E-mail block, or by not specifying a queue in the Create SMS block. The send will be taken care of implicitly by the platform on the system queue. (ER#  248489161)

Errors are shown for the JSP editor when the JAR files of dependent libraries are not available in the Project's lib folder. As a workaround, copy the libraries from the JAR files from the Project's WEB-INF/lib directory into the lib directory as well. (ER#  247823946)

Applications using the DB Data block sometimes have increased latency during runtime when NGI on GVP MCP is using HTTP/1.1 and using a HTTP/1.0 proxy such as Squid. As a workaround, configure http.version on NGI to 1.0 to match the proxy's capabilities. (ER#  245039961)

The Web Services block does not support <xsd:complextype> for input parameters in WSDL files. If the specified WSDL contains this tag, WSDL parsing fails and the block cannot be used. Workaround: Modify the Web Service implementation and avoid using complex types. If the Web Service cannot be modified, use a Backend block to invoke a custom backend page to invoke the Web Service. (ER#  242559091)

Expresssion Builder incorrectly adds single quotes around the second parameter for the _genesys.ixn.setuData() function. Workaround: Edit out the single quotes manually. (ER#  246887111)

The External Service block does not support passing user data to the ESP method when it is invoked. Therefore ESP methods that require user data cannot be used with the External Service block. Workaround: Use a SubDialog block to invoke a hand written SCXML page that invokes the ESP method using <session:fetch>. (ER#  246933472)

A validation error on the user name entered for a Custom Event for an Exception property will cause the OK button to be non-functional. To correct the invalid name, click Cancel in the current dialog, click Add Customm Event again, re-enter the name correctly, and click OK. (ER#  247467686)

In a Create Email or Create SMS block, if a queue is specified for the new interaction, the workflow linked to the specified interaction queue will not be invoked. Workaround: Use a Send Email or Send SMS block in the same workflow as the Create Email or Create SMS block to send the created message. (ER#  245051967)

The existing or current interaction is always stopped in a Route Interaction block and any workflow connected to the queue specified for the existing interaction will not be invoked. Workaround: None. (ER# 245143425)

When using Context Management blocks, a configuration error on Universal Contact Server referring to a non-existent Business Attribute may result in Error connecting to UCS being displayed in Composer. Check that your Universal Contact Server configuration referencing Business Attributes is valid. (ER#  247945860)

Deleting a Project will not delete published objects in Configuration Server. Workaround: Connect to Configuration Server, delete the interaction process diagrams one by one and then finally delete your Project. (ER#  248112964)

Setting a Target block to use Busy Treatments without any specified Busy Treatments will not result in a validation error. Workaround: Check the Treatments property of the Target block to ensure Busy Treatments are defined. (ER#  246781841)

The Route Interaction block is limited to handling one new interaction from a target e.g., a reply e-mail from an agent. The generated application will wait for the new interaction indefinitely and will complete processing after a new interaction is received. Workaround: None. (ER# 245143421)

Context Management Services blocks implicitly set the Media Type for Services and States to one of the enum values in _genesys.FMname.mediaType (provided by Orchestration Server) and do not map them to Media Type Business Attributes defined in Configuration Server. Workaround: Do not set Media_Type in Universal Contact Server. (ER#  248203442)

The Application property in the Media Server block in an interaction process diagram cannot be set to the type Literal when connected to Configuration Server. Instead, use type Configuration Server to configure the Application. (ER#  247921262)

Existing links from a Media Server block are not removed if a different Application object is selected. Workaround: Delete the link(s) manually from the interaction process diagram. (ER#  247524821)

If an interaction process diagram (IPD) is deleted from a Project and the option is declined to delete its Configuration Server objects, creating a new IPD with the same name and in the same Project followed by deletion of this newer IPD will delete this IPD’s Configuration Server objects, but also unexpectedly delete objects from the older IPD of the same name. (ER#  247524846)

An interaction process diagram does not generate code if voice and non-voice (e-mail, SMS) interactions are handled in the same interaction process diagram. No SCXML file(s) are generated. Workaround: Handle voice and non-voice interactions in separate interaction process diagrams. (ER#  247987101)

No error is shown in the Problems view if workflow variables used in the SubRoutine block as parameter values are deleted from the Entry block. Workaround: Open the dialog for the Parameters property in the SubRoutine block; appropriate error markers will be displayed in the dialog. (ER#  248073837)

When creating a new Project, Composer does not display an error message when the suggested Project name in the wizard is the same as an existing Project name although the Next and Finish buttons are correctly disabled. As a workaround, change the Project name to a unique name that does not already exist and Next and Finish will be enabled. (ER#  235596791)

When using a Web Service block in a .NET Composer project, if an input parameter named “CallUUID” (or any input parameter that is a variable) contains an array or a complex object, an exception may occur or parameters may be incorrectly passed to the Web Service. As a workaround for passing input parameters of type array or complex object, modify the Web Service block so that the input parameter is decomposed into multiple input parameters, each being a simple data type. (ER#  235610823)

Parameter names for a Web Request block cannot contain the “-” (hyphen) character. As a workaround, rename the parameters on the web server side responsible for accepting the web request and update the parameter names for the Web Request block to match the new parameter names. (ER# 235323181)

In a .NET Composer Project, when Composer executes a query with embedded application variables (previously specified in a DB Data block using query builder), it does not enclose application variable values in quotes when the values are of type String, Date or Currency. If the same callflow/workflow is used in a Java Composer Project, Composer adds single quotes when appropriate, based on the data type of the value stored in the application variable. As a workaround, in a .NET Composer project, modify the value of the variable using an Assign block to include or exclude single quotes. (ER# 235795371)

Generating code for a callflow/workflow fails with an error message Code Generation contained errors when it includes a Web Service block with no Output Result property assignment to a user-defined variable. As a workaround, set the Map Output Values to Variables to false and generate code. (ER#  235630891)

When opening an existing callflow/workflow that contains a Web Service block, properties Operations, Service End Point, Use Protocol, Available Services, and Bindings cannot be changed once they are set. Workaround: Clear the Service URL property, which will reset other properties for this block, then re-enter Service URL. This will cause the WSDL to be fetched and all dropdown lists will be populated in the Properties view. New values for all properties can be set at this point. (ER#  235624241)

When the Web Service block has property Map Output Values To Variables set to true, and the Web Service result contains an array, Composer only references the name of the array (i.e. uses arrayname instead of arrayname[i]), and does not expose the contents of each element of the array. Workaround: Access array elements by setting property Map Output Values to Variables to false and then assigning specific array elements to variables using the Assign block. The output response variable of the Web Service block will contain the entire response from the Web Service in JSON format. (ER#  232103181)

Database queries specified using the visual Query Builder in DB Data blocks are written in .sql files during code generation. These files do not immediately appear in the Project's db folder in the Project Explorer. To remedy this, you must manually refresh Composer's Project Explorer. (ER# 226754715)

Diagram upgrade will fail if the previous .studio_diagram has the same file name (without the extension) as an existing callflow file in the callflows folder. As a workaround, before upgrading the diagram, rename either the imported .studio_diagram file or the already existing .callflow file to avoid a naming conflict. For more information, see the section on diagram file migration section in Chapter 3 of the Composer 8.0 Deployment Guide. (ER# 231335248)

During a Save operation, Composer performs validation and updates the Problems view with errors and warnings. Project folders in the Project Explorer also show markers in the case of errors in the Project. However, these markers are not shown on blocks. If you trigger validation manually, the block markers are correctly updated. The previous version of Composer did not have any validation during the Save operation. (ER# 227360698)

The Web Request block does not support parameter names that have any of “[^-]+“ characters. The Web Request block in the Voice feature does not support response data in JSON format. This limitation does not exist when the Web Request block is used in routing workflows. Input parameter values are not URL-encoded in the Web Request block for voice or routing. (ER# 231231761)

Disabling Voice related functionality in Composer through Capabilities does not disable all voice-specific functionality. Prompts Manager, which is applicable only for the voice feature, is still displayed. No workaround is needed for this; Prompts Manager cannot be used. (ER# 228059269)

Upgrading a Project that is already upgraded to 8.0.2 throws the following error dialog: Resource is out of sync with the FileSystem. To avoid this issue, refresh the Project Explorer after upgrading the Project for the first time. (ER# 231077681)

Renaming List objects created via the List Objects Manager view occasionally fails if the Description field is left blank. As a workaround, supply a Description field for the error triggering rename. After accepting the initial change, you may edit the item again to remove the description. (ER# 229412551)

The Set Call Data block allows adding more than eight (8) variables in the variables dialog. At that point, the dialog does not provide a default name for the additional variables and does not give a visual indication about the presence of additional variables. As a workaround, limit the number of variables to eight. (ER# 231158331)

For releases previous to 8.0.3, when debugging (stepping through) a workflow that contains a Play Sound block, the debugger requests information not pertinent to the Play Sound operation. This information is shown as a digits field. There is no workaround. (ER# 220587207)

Under certain circumstances, newly added files do not appear in the Project Explorer view. To remedy this, you must manually refresh the view. (ER# 224805101)

Project migration may overwrite the db.connection properties file in the db folder and replace it with a new one. This behavior is related to workspace refresh issues. If this happens, copy the db.connection properties file from the earlier workspace. The file does need to be migrated. (ER# 223467628)

Folder resources may render with a JS icon. This issue is visual only and causes no unwanted side effects. (ER# 224871851)

Notes regarding routing configuration are embedded in the diagrams of Project templates. Ignore references to URLs starting with http://portal.genesyslab.com/dir/engineering. To run or debug the applications in the respective project without changes to the diagrams in the template, follow the instructions in the rest of the note that describe the configuration prerequisites. (ER# 232013991)

Composer Help incorrectly states that raw audio .wav files are supported in Prompts Manager. Prompts Manager only supports playback and recording of .wav files with headers. (ER# 231902091)

Composer Voice Known Issues and Recommendations

Outlinks originating from the Entry block cannot be renamed or assigned a name through the Properties view. There is no workaround. (ER# 227094725)

Shadow variables cannot be used as return values in the Exit block. When enabling the Get Shadow Variables property on supporting blocks, those variables incorrectly become available as return values in that callflow's Exit block(s). Using these as return values will create semantic errors in generated VXML. Do not select shadow variables in this context. (ER# 229011211)

When non-alphanumeric characters are used to create a Connection Profile for a DB Data block, a runtime VXML/SCXML exception occurs when running the application. Restrict the Profile Name field to alphanumeric characters only. (ER# 230710381)

When adding multiple resource-type prompts to a Prompt block, resources added subsequently will default to the value provided in the previous entry. You must manually change these values to the desired settings. (ER# 229725281)

The Log block's Condition property does not let you select from a list of variables. You can specify variables by typing in text in the format "AppState.<variable_name>" where <variable_name> is the name of a Boolean variable from the Variables property in the callflow's Entry block. (ER# 228580236)

Composer does not properly handle Global commands that are triggered via numeric DTMF when they interrupt prompts that are set with Immediate playbackset to true. When possible, do not use the Immediate Playback feature on interruptible prompts in callflows where root commands are necessary. (ER# 230102731)

When WSDL types are defined with a reference to another definition with the same name, the WSDL Parser goes into an infinite loop and causes a stack overflow error. Example:

<xs:element name="execute" type="tns:execute"/>

<xs:complexType name="execute">
<xs:sequence>
<xs:element minOccurs="0" name="wmaAction" type="ns1:action" />
</xs:sequence>
</xs:complexType>

<xs:complexType name="execute">
<xs:sequence>
<xs:element minOccurs="0" name="wmaAction" type="ns1:action" />
</xs:sequence>
</xs:complexType>

(ER# 230764647)

Certain blocks that contain prompts, such as the Menu block, do not properly handle prompt reorganization via Prompt Manager. To reorder prompts, the Prompts field of the relevant block must be changed directly. This issue does not apply to the Prompt block itself. (ER# 228871706)

Composer does not properly populate several diagram date fields: Created on and Last Modified on. There is no workaround. (ER# 215931045)

Installation of Composer in a non-default location may sometimes fail if Composer has previously been installed and uninstalled on the machine. The root cause is an issue with Windows Installer. As a workaround, reboot the machine and reinstall Windows Installer. For more information, see the section on installing Composer on Windows in Chapter 2 of the Composer 8.0 Deployment Guide. (ER# 220449421)

Validating a diagram validates all the diagrams in all Projects of the workspace. (ER# 224406070)

Diagram notes, text, and note attachments do not have automatic text wrapping. After keying in text, you must manually resize to increase the height, at which point text wrapping works correctly. (ER# 222450995)

You must always follow the reboot request at the end of Composer installation. For more information, see the Pending Operations Message section in the Installation Chapter of the Composer 8.0 Deployment Guide. (ER# 226747951)

The Prompts Manager does not support the Undo operation when changes are made from the Prompts Manager.(ER# 213873640)

A .Net Voice Project is automatically deployed to IIS when it is created. However, after renaming the project, it is no longer deployed to IIS. Use one of the following workarounds:

• Before renaming, undeploy the project and then deploy after renaming.
• If you have already renamed the project, deploy the project. From the IIS Manager console, delete the virtual directory pointing to the older name of the project.

(ER# 215231108)

The Query Builder does not support working with table columns that have a space in their names. As a workaround, use a custom query to work with table columns that have spaces in their names. (ER# 214467872)

The DB Data block does not handle database rows where all column values are null. (ER# 217123017)

The Grammar Menu block does not check for the presence of .grxml files exported from its associated Gbuilder file. As a workaround: export .grxml files using the Grammar Builder each time you change Gbuilder files. (ER# 215507361)

The DB Prompt block does not repeat the name of the column before playing back the corresponding value in each row. (ER# 214307377)

The DB Prompt block plays back data as text and not in Date or Currency format. (ER# 214467878, 214492603)

In the Subdialog block, if the Location Type is URI and the path is a static value, the generated code does not work. As a workaround, use a Variable value to specify the location, or if the path is a location inside the Voice Project, specify the Location Type as ProjectFile. (ER# 194549661)

An Editor could not be initialized error occurs when you open more than two instances of a VXML, CCXML, or GRXML file from the History window. The file opens in text mode only. (ER# 171109266)

Tomcat is unable to access the drives created by ClearCase dynamic views. Therefore, Voice Projects are not able to be deployed in the Workspace created inside a ClearCase view. Use snapshot views if you want to make test calls or debug calls for such a Voice Project. (ER# 187537206)

Watch expressions are not created from the Variables window in the VXML Debugging perspective. Create the watch expression manually and prepend AppState. to the desired variable name. (ER# 191088123)

The Validate option accessed by right-clicking a file name from within the Project Explorer does not perform callflow validation. When validating a callflow, use the Validate option from the Diagram menu or the Validate toolbar icon. (ER# 193499151)

When opening imported VXML, CCXML, or GRXML files, context-sensitive help/validation only works properly in the Composer Voice XML Editors if the schema name is set in the top-level <ccxml>, <vxml>, or <grammar> tag. Create a new file of the same type in Composer Voice, then use that as a reference for setting the proper value inside your imported file. (ER# 175177135)

Mapping of WebService output key responses to separate variables using the Map Output Values to Variables property may not work when this property is set to true. Therefore, Genesys recommends setting the Map Output Values to Variables property to false, which collects the entire WebService response to a single variable. Use the Assign block to extract the key responses of the WebService output to individual variables.

Note that the WebService Response will be returned as a JSON object. See the Composer Voice Help topic (in the Troubleshooting section) called "JSON Objects and JavaScript Keywords" for more details on JSON usage. (ER# 191370766)

If a Java Voice Project is renamed, you must reprovision the Voice Project manually in order to make test calls. Right-click the Java Voice Project name in the Project Explorer, select Properties, then select Tomcat Deployment and click the Deploy button. (ER# 194134262)

Test calls will not work if Voice Project names contain spaces. (ER# 194202243)

The Designer does not provide blocks for Full Call Recording. If a voice application needs to use this feature, use the VXML Editor to write custom code. Refer to the Genesys Voice Platform documentation set for further details. (ER# 191977552)

The Designer does not provide Hotword support in transfers. If a voice application needs to use this feature, use the VXML Editor to write custom code. Refer to the Genesys Voice Platform documentation set for further details. (ER# 189037481)

The VXML editor does not automatically add the genesys: prefix for NGI-specific attributes in VXML tags. As a workaround, add this prefix manually in the editor. (ER# 215640342)

The user must ensure that a number value is never passed to the PlayBuiltinType.js functions. When using a variable and Interpret-As Currency or Date, the variable must always be a string. The following steps will ensure this:

1. When using Watch Expression or Query Console to change variable values, add single quotation marks around a number to ensure a number is evaluated as a string. This is only necessary for number values, because strings automatically use single quotation marks. For example, type AppState.myVar = ‘2000’ rather than AppState.myVar = 2000.
2. When using the Assign block to change variable values, add single quotation marks as above. Or, if using a dynamic value from a function, wrap the result in the String() constructor. For example, use String(myFunction()) where myFunction() returns a number.

(ERs# 218099101)

Renaming a callflow (.studio_diagram) file while it is open in the callflow editor does not change it in the editor, and any changes made since the last save are lost. As a workaround, close any callflow files before renaming them. (ER# 213201511)

The Subdialog block's property page popup for the URI property does not function when the Properties view is maximized to fill the entire work area. As a workaround, do not maximize the Properties view while working with blocks that have popup Property pages. If you encounter this error, restore the Properties view to a non-maximized size, click on some other block, and then click the original block. The popup Property pages will function. (ER# 216609158)

Transfers of type blind and consultation do not work when a test call is made using the built-in debugger. The call will reach the Transfer block, but then it will hang and not proceed and you will need to terminate the call or debugging session manually. A partial workaround is to set the Transfer Type property to bridge before debugging. The transfer will proceed, but the debugging session and the call will terminate immediately afterwards. Genesys recommends that you do full testing for Transfer applications by provisioning the application in Genesys Administrator and making test calls directly from the SIP phone. Additional information can be found in the Validation, Debugging & Deployment book of the Composer 8.0 Help. See the Limitations topic. (ER# 191411868)

The Save As option is not available for studio_diagram files. To make a copy of a studio_diagram file from the Project Explorer, right-click the file name and select Copy, then go to the desired location/project and select Paste. (ER# 169842128)

In Windows Vista, renaming files in the Project Explorer fails if you click the mouse outside the rename box to complete the renaming operation. The name reverts back to its original value unless you press the Enter key. (ER# 192486070)

When debugging both callflows and workflows, the following error message can occur if you deleted a project and then created it again with the same name. For example:

Could not locate resource root: /MyComposerProject/debugging-results

To resolve this issue, create the missing folder manually. Right-click on the project folder and select New > Folder. When prompted for the name of the folder to create, enter:

debugging-results

Top of Page

Discontinued Support

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.

There is no discontinued support to report for this release.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

• Composer 8.0 Deployment Guide describes how to deploy Composer, an Integrated Development Environment (IDE) used to develop applications for Genesys Voice Platform and the Genesys Universal Routing Platform.

• Composer 8.0.4 Help (accessible inside Composer's Eclipse Help System) provides integrated help information about using Composer to develop voice and routing applications.

• Composer 8.0 Routing Applications User's Guide introduces the Composer interface and the process of building routing applications, including creating interaction process diagrams and workflow diagrams.

Product documentation is provided on the Technical Support website, the Genesys Documentation wiki, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.

Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Technical Support 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.

Top of Page