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 Composer.
Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on any third-party software used in this product, see the Legal Notices for Composer. Please contact your Customer Care representative if you have any questions.
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
This release includes important security fixes for the Angular JS and .jQuery vulnerabilities. In particular, Angular JS and .jQuery have been removed, and the existing Java libraries are now used.
(COMPOSER-16643, COMPOSER-16659)
This release includes important security fixes related to the json-java 20070829 (CVE-2022-45688) vulnerability. In particular, the json-java JAR file has been updated from 20070829 to 20231013.
(COMPOSER-16763)
This release includes important security fixes related to Netty Jar vulnerability.
(COMPOSER-16740)
This release includes important security fixes related to Jetty Jar vulnerability.
(COMPOSER-16655)
This release includes an upgrade of Java from 8 to 17 and Eclipse from Photon (4.8) to 2024-09 (4.33). (COMPOSER-16647)
OpenJDK 11.0.2 (64-bit) has been replaced with OpenJDK 17.0.2 (64-bit) in j2sdk.zip.
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 Composer.
Important Notes
This issue will be fixed in future releases.
This release includes important security fixes related to the Apache Ant 1.9.0 (CVE-2021-36373) vulnerability. In particular, the Apache Ant library included with Composer has been upgraded from version 1.9.0 to 1.10.14.
(COMPOSER-16580)
This release includes important security fixes related to the dom4j (CVE-2020-10683) vulnerability. In particular, the dom4j JAR file has been updated from 1.4 to 20040902.021138.
(COMPOSER-16582)
This release includes important security fixes related to the Log4j (CVE-2021-44832) vulnerability. In particular, the log4j-api and log4j-core JAR files have been updated from 2.17.1 to 2.23.1.
(COMPOSER-16604)
GMF tooling update site is no longer available in eclipse sites. You must install the GMF runtime using this Eclipse site. The required GMF tooling JAR (org.eclipse.gmf.tooling.runtime_3.2.0.201409171321.jar) is now bundled along with Composer.
(COMPOSER-16683, COMPOSER-16672)
Tomcat is no longer bundled with Composer. During installation, you will be prompted to specify the location of your Tomcat installation. In Tomcat Preferences, you must also provide the Composer installation location. Additionally, a new button, Update tomcat configuration has been introduced to switch between Tomcat versions and ports. Note: Only Tomcat 10.1.x versions are supported.
(COMPOSER-16575, COMPOSER-16693)
A new category, Composer Export has been added under project properties with a checkbox. When enabled, the web.xml file from the Java project will be included in the export; when disabled, the default web.xml file will be used. This fixes the issue where the web.xml file in the WEB-INF folder of Java projects was not included during WAR export, and a default web.xml was added instead.
(COMPOSER-16739)
The issue where HTTP REST block execution returned a 204 No Content response and resulted in the call getting terminated prematurely has been fixed. The call now proceeds to the next block as expected. (COMPOSER-16541)
The issue where the log level automatically changed to DEBUG when the Database block was called is now fixed. (COMPOSER-16576)
The issue where the Input block was not functioning correctly when Number of Retries Allowed was set to a double-digit number is fixed. (COMPOSER-16566)
The issue where the Web Service block did not function properly in Java 11 due to the removal of SOAP-related JARs in JDK 9 is now fixed. This involves bundling the following JAR files along with Composer:
(COMPOSER-16555, COMPOSER-16671)
The issue related to End of Life and security vulnerabilities in Composer JARs is now fixed. This involves the following updates:
(COMPOSER-16673)
The issue where adding a project-level variable (for example, v_test1) in the Email Response block automatically resulted in the addition of _data.v_test1 is now fixed. The _data.v_test1 variable is no longer be added. (COMPOSER-16515)
In .NET projects, the issue where special characters such as @, #, !, and so on were correctly URL-encoded but not properly URL-decoded, has been fixed. (COMPOSER-16736)
In .NET projects targeting Windows 11, the Enum values for SecurityProtocolType in the getWebRequestData.aspx and getWebServiceData.aspx files have been updated to their equivalent hexadecimal values. (COMPOSER-16756)
Oracle JDK 1.8 has been replaced with OpenJDK 11.0.2 (64-bit) in j2sdk.zip. (COMPOSER-16744)
The issue where Composer could not be launched from the Dev Workbench has been fixed.
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Composer now supports the following operating systems for runtime deployment and execution of WAR files. See the Supported Operating Environment: Composer page for more detailed information and a list of all supported operating systems.
(Composer-16486, COMPOSER-16487)
Starting with this release, Composer's DB Data blocks support Microsoft SQL Server 2019 in both Callflows and Workflows.
See the Composer page in the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported databases.
(Composer-16488)
This release includes important security fixes related to the Apache Log4net vulnerability (CVE-2018-1285). In particular, the Log4net library included with Composer has been upgraded to 2.0.14.0. (Composer-16491)
The Route Interaction block will stop polling the queue after the specified target selection timeout configured in the block properties occurs. (Composer-16494)
Custom connection strings in DB connection profiles are now generated successfully without any error messages. (Composer-16495)
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
The jquery-latest.js file is upgraded from version 3.4.1 to 3.5.1. (Composer-16361)
The xmlsec-1.5.8, jdom-2.0.6, and commons-codec-1.3.1 JAR files are now upgraded to newer versions, xmlsec-2.3.0, jdom2-2.0.6.1, and commons-codec-1.15 respectively. (Composer-16444, Composer-16467, Composer-16477)
This release addresses a potential memory leak in the backend which resulted in threads not being released properly when SSL-related exceptions were thrown from server-side blocks, such as the Web Request and Web Service blocks. (Composer-16344)
Composer supplied audio files are no longer distorted and are played properly after projects are upgraded. (Composer-16471)
Code is enhanced to avoid overwriting the pattern layout in the log4j2.xml file, in environments where IBM WebSphere is used as the application server. WebSphere servers now look for pattern layouts available in the log4j2.xml file for logging. (Composer-16451)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
Support for the following databases as of Feb 08, 2022. (Composer-16450)
See the Supported Operating Environment: Composer page for more detailed information and a list of all supported databases.
This release includes important security fixes related to the Apache Log4j 2 vulnerability (CVE-2021-45105). In particular, the Log4j library included with Composer has been upgraded to 2.17.1.
Composer must be upgraded to the latest version and existing WAR files must be regenerated to ensure that the fix in Log4j version 2.17.1 is applied successfully.
(Composer-16457)
The Backend.jspf file is updated to address the performLogic
duplicate method error. (Composer-16456)
The commons-io.jar file is upgraded from version 2.4 to 2.11.0. (Composer-16428)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
This release includes important security fixes related to the Apache Log4j 2 vulnerability (CVE-2021-44228 and CVE-2021-45046). In particular, the Log4j version included with Composer has been upgraded to 2.16.0.
Composer must be upgraded to the latest version and existing WAR files must be regenerated to ensure that the fix in Log4j version 2.16.0 is applied successfully.
(Composer-16455)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
This release includes important security fixes related to the Apache Log4j 2 vulnerability (CVE-2021-44228). In particular, the Log4j version included with Composer has been upgraded to 2.15.0.
Composer must be upgraded to the latest version and existing WAR files must be regenerated to ensure that the fix in Log4j version 2.15.0 is applied successfully.
(Composer-16452)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
Personally Identifiable Information (PII) is no longer recorded in the ORS logs. To facilitate this change, event.toSource() logging details are removed from all IPD handlers and project log levels are added in missing instances. The _Log statement is removed from the RouteFeature.js file. (Composer-16411)
The growth size for the _data.system.context.errors and data.system.context.uncaughtApplicationEvents objects are now limited to a maximum size by introducing a variable, systemArraySize, in the common.js file. Also, a new project variable, systemArray_BlockList, is introduced to enable users to specify a list of events to be excluded from the _data.system.context.uncaughtApplicationEvents object. (Composer-16381)
The date/time string that is passed to the Web Request and Web Service blocks now uses the right date format in both the getWebRequestData.aspx and getWebServiceData.aspx files. (Composer-16379)
The irdListGetSize() function is now properly returning the size of the list. On setting the bDoNotCountEmptyItems boolean parameter to true, values without keys are not counted towards the list size. However, there is a limitation to this behavior as noted in the Known Issues and Recommendations section of this RN. (Composer-16375)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
The Web Service and Web Request blocks now support connecting to external web services using port numbers that contain more than 4 digits. Previously, port numbers with more than 4 digits were truncated. (Composer-16407)
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Composer now supports Eclipse Photon version 4.8. (Composer-16310)
The Tomcat version that is bundled with Composer is upgraded to version 9.0.36. (Composer-16318)
The WebRequest and WebService blocks' HTTPS certificate handling is enhanced through a configurable flag, web.https.productionMode
(default: false
), which can be set through the composer.properties file. If the new flag is enabled, Composer only validates the server certificates for expiry and signature, and no longer adds them to the trust store. Previously, Composer only added the server certificates to the trust store. (Composer-16272)
The WebRequest block is now enhanced to fetch the error stream (for all error codes except 200 OK
), attempt to retrieve the response message, and then propogate the message to the invoking application (that is ORS or GVP). (Composer-16273)
The WebRequest and WebService blocks in Composer .NET projects are updated to use the new HTTPS Proxy Client Authentication
API method. (Composer-16276)
Composer now supports the _es_store
ORS attribute for the <state>
and <transition>
elements. (Composer-14254)
Changes have been made to ensure that the SSL configuration details of the corresponding WebRequest or WebService block are correctly detected and executed. Previously, only the first WebRequest or WebService block's SSL configuration details were detected and executed. (Composer-16289, Composer-16313)
The Composer-generated unique 10-digit internal key is now always within the integer range. Previously, the value of the internal key was at times outside the integer range and as a result, caused ORS to run into an error and move interactions to the error queue. (Composer-16317)
When upgrading a Java Composer Maven project, the corresponding pom.xml file is also upgraded to include the latest Composer dependent JAR files. If the pom.xml file is missing for a project, the file is recreated during the project upgrade. (Composer-16286)
The backend.jspf file now uses the updated path of log4j2 for logger reference in the file. (Composer-16349)
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Composer now supports OpenJDK 8, for both design time and runtime execution of Eclipse IDE and WAR file deployments. (Composer-16262).
Composer now supports OpenJDK 11, only for runtime deployment and execution of WAR files. (Composer-16074)
See the Supported Operating Environment: Composer page for more detailed information and a list of all supported prerequisites.
Starting with this release, a new project type, Java Composer Maven Project, is introduced to support Maven builds. Maven projects will provide a pom.xml file to customize project builds. (Composer-16216)
For more information, refer to the Maven Support for Building Java Projects section in the Project Types and Directories topic in Composer 8.1.5 Help.
Composer's Java backend logging support has been upgraded from log4j1 to log4j2. This enables sensitive information to be masked in the Composer Tomcat logs using configurable patterns. A new field, Composer Log Masking Regex Pattern, is included in the Default Logging project-level property, to specify the regex pattern to be used for masking. The user specified regex pattern is stored in the makingPattern.json file located in the WEB-INF\lib folder within the corresponding Composer project folder. (Composer-16192)
For more information, refer to the Masking Sensitive Information in Composer Tomcat Logs topic in Composer 8.1.5 Help.
Callflow and Workflow diagram blocks' logging properties have been enhanced to use block-level or project-level logging. This helps mask sensitive information in ORS/GVP application logs. (Composer-16191).
Composer now adds a new entry to the trust store with the alias as the principal name (key value) of the certificate. Previously, URLs were stored as the key value. The key value is used to verify the certificate in the trust store for server communication and as the URL parameters differed each time, this resulted in a new entry in the trust store for every web service call and key store tampered errors. (Composer-16265, Composer-16228)
User Data block for workflow diagrams has been enhanced to use a unique key for the user data change event handlers. Previously, the same key was generated for all User Data blocks in a strategy, resulting in a race condition. (Composer-16255)
The DB Data block's stored procedures logic has been modified to not create two table entries on execution. This issue occurred in Composer versions 8.1.540.07 and 8.1.541.07. (Composer-16245)
For server-side Web Service blocks, computational timeout processing is optimized to return an error when the first connection request fails, without waiting for a read timeout also to occur. (Composer-16222)
The Tomcat Preference page now displays a warning message if an older version of the composerBackend.jar file is used in the configured Tomcat location. (Composer-16161)
Composer DB Data block's backend handler now closes all connections after execution. Previously, pooled data sources were not cleaned during context exit resulting in memory leaks at times. (Composer-16150)
The mchange-commons-java-0.2.15.jar file is now added to the list of Composer backend JAR files and is included in a project's WAR export file. Previously, this JAR file was not included in the WAR export file when upgrading from an earlier version to version 8.1.540.07, and as a result, connection pooling did not work for DB Data blocks. (Composer-16256)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
The callflow/VXML debugging feature now works as expected. In some previous releases, the JDOM conversion (XML to Java Object and vice versa) was incorrect and as a result, the debug voice callflow feature did not work as expected. (Composer-16231)
The workflow/SCXML debugging feature now works as expected. In some previous releases, the JDOM conversion (XML to Java Object and vice versa) was incorrect and as a result, Composer-ORS debugging did not work as expected. (Composer-16233)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is an update for this product. This release contains the following new functionality:
Composer's command line interface has been enhanced to return different exit codes to help identify which command line operation has failed. (Composer-16194)
For more information, refer to the Command Line Code Generation section in Composer 8.1.5 Help.
Composer is enhanced to support simplified backend logging for WebSphere Application Server (WAS) and Tomcat without the need for manually configuring system properties. If the Log4j.xml file is present within the project folder, application-level logging takes precedence. When the Log4j.xml file is present in the server and not within the project folder, server-level logging is performed. Default logging is performed if the Log4j.xml file is not found within the project folder and the server. (Composer-16199)
The commons-io.jar file is upgraded from version 1.4 to 2.4. (Composer-16217)
Composer now checks the result set of the executeQuery()
function for NULL and validates its column count to ensure that the executed stored procedure returns a valid result set. Previously, the executeQuery()
function always returned a result set (NOT NULL) even if the columns were empty on executing the given SQL stored procedure. (Composer-16198)
Custom headers are now included in the web request for both Web Request and Web Service blocks in .NET Composer projects. (Composer-16177)
Now, if context services information is not specified or is incorrect in Preferences when selecting LCA as the Target type, an error message is displayed stating the reason for the unsuccessful connection in the Targets dialog of the Target and Route Interaction blocks. (Composer-16009)
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Composer now supports the Eclipse integrated development environments Neon (4.6) and Oxygen (4.7). (Composer-16141, Composer-16142)
For more information, refer to this section in the Composer 8.1.5 Deployment Guide.
Composer IPD diagrams now support adding external JS file URLs and during code generation the URLs are part of the generated SCXML code. (Composer-16143)
Composer's command line interface now displays a report in text format at the console, indicating the status of the operation being performed (success/failure), and returns an exit code of 0 or 1. 0 indicates success and 1 indicates failure. (Composer-16132)
For more information, refer to this section in Composer 8.1.5 Help.
The Web Request and Web Service blocks now support mutual authentication (where both client and server authenticate each other's identities before actual communication occurs) when fetching HTTPS URLs. The existing property category, HTTPS Server Authentication, has been renamed to HTTPS SSL Authentication, and the following new properties have been introduced under the HTTPS SSL Authentication category to support mutual authentication: Authentication Type, certificateStoreName, Certificate Alias, Certificate Or Keystore Location, Key Algorithm, Key Store Password, and Private Key Password. (Composer-16169)
For more information, refer to the Web Request Block and Web Service Block topics in Composer 8.1.5 Help.
The Skill Expression Builder now supports the sitex()
function, which can be used to route interactions to targets based on their location. (Composer-15682)
The jquery-latest.js file that is shipped with Composer has been upgraded from version 3.0.0 to 3.4.1, for both Java and .NET Composer projects. This file is located in the Reports folder within Composer projects. (Composer-16180)
During project upgrades, errors and exceptions associated with Transfer blocks are now preserved. Earlier, errors and exceptions associated with Transfer blocks were lost during project upgrades and thereby removed from the blocks' exceptions list, resulting in orphaned output links after a project upgrade. (Composer-16168)
User provided custom functions in the customprompts.js file are no longer overwritten during project upgrades. (Composer-16054)
The DB Data block's backend handler now closes all connections after code execution. Previously, not all connections were closed on exit and this resulted in memory leaks. (Composer-16150)
When exporting a Composer project as a WAR file, the build.xml file now references the upgraded versions of the following JAR files: commons-fileupload-1.4.jar, c3p0-0.9.5.4.jar, xmlltooling-1.4.5.jar, xmlsec-1.5.8.jar, and wss4j-1.6.19.jar. Earlier, the build.xml file was referencing older versions of these JAR files. (Composer-16165)
In the Web Request and Web Service blocks, if a string enclosed in quotes is specified as a value for the Login Name and Password properties instead of a variable, an extra pair of quotes are not added now during code generation. Earlier, in similar scenarios, when upgrading projects from certain older versions to a newer version, the value with quotes was enclosed within another pair of quotes during code generation and authentication failed as a result. (Composer-16146)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
In the Web Request and Web Service blocks, the backend code that handles HTTPS certificate additions has been optimized so that the KeyStore timestamp is not updated if there has been no change to the list of certificates in the KeyStore. The timestamp is updated only when there is an actual change to the certificate list. Earlier, the KeyStore timestamp was updated with every web request, irrespective of any change to the KeyStore. (Composer-16098)
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Starting with this release, Composer supports the ability to overwrite published queues. A confirmation dialog is now displayed enabling users to selectively overwrite and republish configuration objects. (Composer-16040).
Both Java and .NET Composer projects now support Asynchronous HTTP connections. The Web Request and Web Service blocks have been enhanced to use Asynchronous HTTP connections to avoid timeout issues on the IIS server when request volumes are high. Previously, as part of Hot Fix v8.1.453.03, this change was limited to .NET Composer projects. This enhancement helps increase performance and responsiveness of applications, and reduce the number of active threads consumed by applications. (Composer-16053, Composer-16068)
In the Web Request and Web Service blocks, backend code that handles HTTPS certificate additions has been improved to avoid multiple updates to the given certificate alias for the keystore. (Composer-16098).
The c3p0-0.9.1.2, wss4j-1.6.1, xmlsec-1.4.5, xmltooling-1.3.1, and commons-fileupload-1.3.3 JAR files are now upgraded to newer versions, c3p0-0.9.5.4, wss4j-1.6.19, xmlsec-1.5.8, xmltooling-1.4.5, and commons-fileupload-1.4 respectively, to address security vulnerabilities. (Composer-16093, Composer-16079)
Composer project versioning issues with manual project upgrades (for Composer versions 8.1.5+) have been addressed as part of this release. (Composer-16077)
UI text and descriptions of sample applications in Composer versions 8.1.5+ are now displayed in English. Previously, they were displayed in French as file references were pointing to French files. The file references are now updated to point to English files. (Composer-16054).
Composer now supports direct project upgrades from version 8.1.2 to versions 8.1.4 or 8.1.5. Previously, only incremental upgrades were supported, and also an error occurred and interrupted the upgrade. (Composer-16101, Composer-16087)
In the Menu block, every retry count generates 2 entries in the Retry dialog (one noinput and one nomatch). Previously in such scenarios, the warning message associated with the mismatch in retry prompts and number of retry counts was displayed. The validation logic is now updated to validate the mismatch correctly. (Composer-16087)
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Starting with this release, Composer supports routing interactions to the Last Called Agent (LCA), that is, the most recently contacted agent. This is supported for both voice and non-voice multimedia interactions through the Target block and the Route Interaction block respectively. To enable this functionality, a new target type, LCA, is added to the Targets dialog accessed through the Targets property in the Target block and the Route Interaction block. (Composer-15944)
For more information, refer to the Routing to the Last Called Agent topic in Composer 8.1.5 Help.
Bulk Manager is now launched when the Composer application is started. This behaviour is controlled through a new option, Launch Bulk Manager on Composer startup, and is enabled by default. (Composer-15946)
For more information, refer to the Launching Bulk Manager on Composer Startup topic in Composer 8.1.5 Help.
A new property, Exception, is added to the GoTo block to allow users to define exception events that can be handled within the block. (Composer-15943)
For more information, refer to the GoTo Block topic in Composer 8.1.5 Help.
Support for SSL proxy tunneling is now extended to .NET Composer projects. Previously, as part of Hot Fix v8.1.500.05, support for SSL proxy tunneling was limited to Java Composer projects. (Composer-16053)
See the Supported Operating Environment: Composer page for more detailed information and a list of all supported databases.
The selected audio source no longer plays repeatedly when the Sound Type is configured as ARM in the Play Sound block. Earlier, in such scenarios, the audio source played repeatedly irrespective of the value of the Music Repeat Count option. (Composer-15947)
The attachCategory
function's description within the Composer application has been updated to indicate that the relevancy function argument must be specified as a string. Previously, this was indicated incorrectly as integer. (Composer-15710)
Values of variables used in custom headers are now passed correctly. Previously, the variables were passed instead of their values. (Composer-16023)
On changing the default name of a Web Request block in a diagram, the modified name is now reflected in the generated SCXML code. Previously, the modified name was not reflected in the generated SCXML code. (Composer-15990)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
Important! The composerbackend.jar file is automatically updated on installing this hot fix and no manual changes are required to be made to existing projects. However, Java Composer projects that were exported and deployed as WAR files must be compiled again for the new functionality to be effective.
Beginning with this release, Composer implements SSL proxy tunneling. In previous releases, SSL connections in the Web Request and Web Service blocks did not consider the proxy settings and resulted in a timeout error when establishing connection with HTTPS services. (Composer-16028)
Note: SSL proxy tunneling is applicable only for Java Composer projects using the Web Request and Web Service blocks.
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Starting with this release, Composer supports Microsoft Windows 2016 Server. (Composer-15902)
See the Composer page in the Genesys Supported Operating Environment Reference Guide for a list of all supported operating systems.
The Assign Data property in the User Data block now supports variables for the key value in the Skills option. (Composer-15942)
Composer Bulk Manager is enhanced to support upgrading multiple projects. Also, a new tab, Logs, is introduced to configure the log level for the various server-side pages. (Composer-15863).
For more information, refer to the Upgrading Multiple Projects and Configuring Log Levels topics in Composer 8.1.5 Help.
The Composer Diagram Editor now supports searching for a block in an active diagram using the CTRL+J shortcut key. (Composer-15864)
For more information, refer to the Simple Search section in the Diagram Search topic in Composer 8.1.5 Help.
Workbench level Advanced Diagram Search is also supported allowing users to search for blocks by name or type in diagrams across all projects. (Composer-15898)
For more information, refer to the Advanced Search section in the Diagram Search topic in Composer 8.1.5 Help.
Composer now supports the latest .NET Framework version 4.7.2 and the bundled Newtonsoft.Json.dll file is upgraded to version 11.0. (Composer-15862)
Note: In order to run the existing callflow/workflow strategies with the updated DLL files, you must update the .NET version in IIS Server from .NET 2.0 to .NET 4.5 under Application Pool in Advanced Settings (Default Site > Advanced Settings... > Application Pool).
The getANI()
utility method for callflow diagrams is updated to return an empty string for invalid formats of P-asserted-identity
values. (Composer-15856)
The Timeout property in the Web Request block is now applied correctly for all POST methods. Earlier, readTimeout
was not triggered correctly in certain scenarios. (Composer-15777)
The DBData block's backend dbRequest.jsp file is updated to work with Oracle WebLogic Server 12c. (Composer-15837)
Transition output and sub-state are now added correctly in the User Data block when Timeout
is set to 0
. Earlier, _reserved_UserData1_outputTransition
was missing when Timeout
was set to 0
. (Composer-15858)
Transition conditions using _genesys.ixn.interactions
, in workflow diagrams, have been updated to include a null check to avoid error.illegalcond
errors. (Composer- 15867)
Event names have now been made unique across diagrams in a workflow to avoid blocks terminating prematurely or resulting in any unexpected behavior when two or more blocks with the same name run in parallel. (Composer-13500)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
For .NET Composer Projects, the Web Request and Web Service blocks have been changed to use Asynchronous HTTP connections to avoid timeout issues on the IIS server when request volumes are high (30,000 to 40,000 requests per day). (Composer-15991)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
The Composer DB Backend servlet now implements a fallback mechanism to use asynchronous execution of DB queries and if that fails, synchronous execution is applied. (Composer-16044)
Note: The implementation of this fallback mechanism will not have an impact on existing applications.
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Starting with this release, Composer's DB Data blocks support Microsoft SQL Server 2017 in both Callflows and Workflows. (Composer-15627)
See the Composer page in the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported databases.
This release supports French Canadian localization. (Composer-15638)
For installation information, see the Locales topic in the Composer 8.1.4 Deployment Guide. Also see the Internationalization section of this release note.
Composer now supports fetching HTTPS URLs in the Web Request and Web Service blocks. A new property category, HTTPS Server Authentication, with two properties, Trust Store Location and Trust Store Password, is introduced to extend support for HTTPS URLs. (Composer-15616)
A new view, Strategy Manager, is added to the Composer Workbench to list all routing points from the connected Configuration Server. This view provides options to directly deploy Composer-generated strategies to routing points in Configuration Server. (Composer-15661)
For more information, refer to the Strategy Manager View page in Composer 8.1.4 Help.
A new feature to refactor variables across blocks in a diagram file is introduced. The new feature allows users to select variables to be refactored in the different impacted blocks of a diagram when they rename any variable in the Entry block. Previously, when a variable was refactored, Composer displayed validation error messages to notify users to change the variable name in other impacted blocks only when that particular diagram was validated. (Composer-15649)
For more information, refer to the Refactoring Variables section in Composer 8.1.4 Help.
A new wizard, Composer Bulk Manager, is introduced to manage bulk deployment of projects. (Composer-15663)
For more information, refer to the Deploying Multiple Projects section in Composer 8.1.4 Help.
A new property, Timeout, is introduced in the Identify Customer block to specify the number of seconds that the application will wait when fetching data from UCS. (Composer-15608)
Server-side exceptions from the Web Request and Web Service blocks are now optional. A new flag, web.throwServerException
, is introduced. On adding the flag to the composer.properties file in the respective project and setting it to true
, the Web Request or Web Service block throws an error.com.genesyslab.composer.servererror
error for failures. If the new flag is set to false
, the Web Request or Web Service block updates the errorMsg
entity in the JSON response. If the particular configuration option is not found in the composer.properties file, the Web Request or Web Service block updates the errorMsg
entity in the JSON response (as when the flag is set to false
). (Composer-14112)
The jQuery library bundled with Composer projects for the Project Upgrade report is upgraded from v1.6.4 to v3.0.0. (Composer-15691)
The commons-fileupload.jar file bundled with Composer WAR files for Java Composer projects is upgraded from version 1.2.1 to 1.3.3. (Composer-15729)
The IPD Diagram Submitter Script Object now points to the Workflow Enhanced Routing Script Object when a Workbin Block with a Private Queue is used. Earlier, the IPD Diagram Submitter Script Object pointed to PrivateQueue.Routing
. (Composer-15603)
Composer now verifies the value of the interaction content in the Screen Interaction block before passing it on to the setudata
function. If the Value field is empty, the setudata
function is ignored. Only if the Result Type set to ALL, the Key Value Pair and Categories can be added to the user data. (Composer-15583)
Response messages from the Backend block now contain the relevant JSON content when valid data is returned through the performLogic
function of a custom JSP page. Previously, an empty response was returned in such scenarios. (Composer-15692)
The HTTP Rest block no longer generates a username and password in the code if the corresponding properties are not set in the block. Previously, null values were generated for empty properties which caused MCP to generate an Authorization header. (Composer-15703)
The bargeintype
property is now set correctly in the code generated when an Input block is configured with the Interruptible property set to DTMF
. (Composer-15666)
The DB Data block now overrides the JNDI namespace option at runtime, if specified locally in the block. The Java Composer Projects WAR Export wizard is enhanced to include an optional, custom ibm-web-bnd.xmi file. If provided, the Composer supplied file is replaced with the custom one. (Composer-15679)
Composer now has the ability to pass context parameters across sessions when the Use Platform option is selected under Project Properties > Orchestration Options > Interaction Detach and the Detach property is set to true
in the Route Interaction block. (Composer-15664)
When specifying integers (or constants) in SQL queries, users must enclose them within single quotes (for example, '0123') in the DB data block. (Composer-15599)
Callflow Diagram exceptions now populate the following system variables: AppState.LAST_EVENT_ELEMENT, AppState.LAST_EVENT_MSG, AppState.LAST_EVENT_NAME, AppState.LAST_EVENT_LINE
, and AppState.LAST_EVENT_URL
. (COMPOSER-15758)
Workflow Diagrams now consider the TMediaNativeSMS interaction media types in the initializeRoutingSystemVariables
method. (COMPOSER-15698)
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
The Tomcat version bundled with the Composer installation package is upgraded from 7.0.69 to 8.5.27. (Composer-14460)
Starting with this release, Composer backend server side-pages are analyzed for security and performance issues using CheckMark Scan, a security analysis software. (Composer-15555)
Support for the following databases:
Composer now supports Oracle Database version 12c Release 2. To support this enhancement, the OJDBC driver is updated from version 6 to 8, and the J2SDK bundled with Composer has been upgraded to JDK 8. (Composer-15443)
Starting with this release, Composer's DB Data blocks support Microsoft SQL Server 2016 in both Callflows and Workflows. The SQLJDBC driver is upgraded from version 4.1 to 6.4. (Composer-15422).
See the Composer page in the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported databases.
The Analyze Interaction block has been enhanced to include an additional item, UCS, in the Type drop-down on the dialog displayed when specifying the value for the Analyzing Data property. The UCS option is selected in the drop-down by default. (Composer-15413)
SSL certificate validation code is disabled as Composer does not utilize this code for HTTP requests. If required, this code can be enabled on-demand by setting the web.legacyCertificateCode
option to true
in the composer.properties file. In previous versions, this code was always enabled. (Composer-15589)
The correct code is now generated when the Categories option is selected in the Configure Assign Data dialog while specifying a value for the Assign Data property in User Data blocks. Earlier, the conditions in the code generated for the User Data block were incorrect when the Categories option was selected. (COMPOSER-15557)
The error.notallowed
event is now handled correctly in the User Data block. In previous releases, single quotes were missing in the code generated. This resulted in a syntax error and the error.notallowed
event was not handled based on the correct user data state. Calls were not routed appropriately at times. (COMPOSER-15607)
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
The new HTTP Rest block is used for both routing and voice applications.
In routing applications, the HTTP Rest block supports the native HTTP Fetch functionality in Orchestration Server and uses the ORS SCXML <session:fetch>
element to fetch arbitrary XML, JSON, and Text data from a server. The data fetched by the <session:fetch>
element is bound to an ECMAScript object through a named variable.
In voice applications, the HTTP Rest block supports the native HTTP Fetch functionality in GVP and uses the GVP VoiceXML <data>
element to fetch arbitrary XML, JSON, and Text data from a document server. The data fetched by the <data>
element is bound to an ECMAScript object through a named variable.
For more information on the new block, see the HTTP Rest Block page in Composer 8.1.4 Help.
Zeroes are now played back correctly by intelligent prompts in Prompt blocks. Earlier, zeroes in numbers were played incorrectly by intelligent prompts in Prompt blocks. (Composer-14462)
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 Composer.
Important! Whenever a Project is imported into the workspace while upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Two new blocks, Facebook and Twitter, are added to the Social Media category for workflow diagrams. Using the new Twitter and Facebook blocks, an organization's Twitter and Facebook handles can be monitored through pre-defined events, and messages filtered based on keywords to determine the next action. (COMPOSER-14270)
To support the two new blocks the following changes have also been made:
system.InteractionMediaType
variable in the Entry block of the workflow diagram is now automatically populated with the media type of the interaction for Facebook and Twitter (attr_itx_media_type [str] = "facebook"
or attr_itx_media_type [str] = "twitter"
). Skill expressions are now validated even when they contain multi-byte characters (for example, Japanese characters). Also, single quotes are not added automatically for multi-byte characters, if not provided by the user in the expression. (COMPOSER-14470)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality.
The To property for the following eServices blocks adds a variable option: Email Response, Email Forward, Create Email, and Chat Transcript. (COMPOSER-13519)
This release includes the following corrections and/or modifications:
The From property for the following eServices blocks adds a variable option: Email Response, Email Forward, Create Email, Send Email, and Chat Transcript. (COMPOSER-14478)
The Stop Interaction block now disables the Application Name property when the Notify UCS option is selected in the Notify Dialog. To notify any applications that interaction processing has stopped (including a specific UCS), use the Notify Third Party Server option. (COMPOSER-14456)
The Create Email block no longer generates invalid code when the Output Result property is set with User Data. (COMPOSER-14450)
The Set Ideal Agent block no longer truncates values in variables and variable-related expressions. (COMPOSER-14469)
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 Composer.
Important! Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Code generation and Upgrade actions now work for Projects created in multi-byte characters sets. (COMPOSER-14251)
Extra <variable> lines no longer appear in callflow diagrams. Previously, every time a change was made to a callflow diagram, one instance of ComposerRoot.vxml and User variables were created, which caused Composer to generate the following error message: Variable Name <xxxx> already exists. (COMPOSER-14404)
Worklfow diagram Cancel Event Block upgrades successfully from pre-8144 versions. (COMPOSER-14313)
Web Service block Password properties are now hidden by asterisks. (COMPOSER-3428)
Interaction process diagram, Branching block, Conditions property variable selection adds _data prefix for Project variables. (COMPOSER-14257)
DBInput block is improved to support DB data in Arabic and UTF-8 languages. (COMPOSER-14316)
Application Root variables are now preserved after a Project upgrade (COMPOSER-14365)
Route Interaction block and Target block code generation has been improved to handle the "collage" method in the threshold attribute value. (COMPOSER-14392)
Transfer Block Variables property works now for Literal type Key and Variable type Value combination. (COMPOSER-14218)
The Email blocks To property now validates duplicate entries. (COMPOSER-3439)
The DB Input block now generates DTMF grammar for Integer DB values. (COMPOSER-14346)
Supported Operating Systems
Supported Languages
New in This Release
Corrections and Modifications
The following table lists the languages supported by this release.
ARA | CHS | CHT | CSY | DEU | ESM | ENU | FRA | FRC | ITA | JPN | KOR | PLK | PTB | RUS | TRK |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
X | X |
There are no restrictions for this release. This release contains the following new features or functionality.
Language and country settings. The following option is added for language and country settings:
For installation information, see the Locales topic in the Composer 8.1.4 Deployment Guide on the Composer documentation website. Also see the Internationalization section of this release note.
Important! Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
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 Composer.
Important! Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
A new Configuration Server preference, Fetch Timeout, can be used as the timeout for fetching from Configuration Server queries. (COMPOSER-14160)
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 Composer.
Important! Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Composer eServices child interactions handling is improved with support for the <ixn:createmessage> associate attribute. (COMPOSER-14150)
The Add Record Block Calling List property is changed to a mandatory property. (COMPOSER-14143)
The irdUTCFromString utility function is improved to check for null and undefined parameters. (COMPOSER-14128)
The User Data block Wait for Event property is improved to reliably check user data attachments. (COMPOSER-14084)
The Workflow diagram Exit block now allows adding SCXML extensions. (COMPOSER-14081)
The Interaction Queue block now validates the View name for space and slash characters. (COMPOSER-5082)
Composer internal block events for the eService detach operation is renamed to use the composer. prefix. (COMPOSER-13496)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality.
Important!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
(COMPOSER-14099)
The Play Application block no longer validates Output Parameters when the Use User Data property is set to false. (COMPOSER-14090)
The Target and Route Interaction blocks no longer print error messages in Orchestration Server logs when the Target Deviation from Ideal Agent property is not set. (COMPOSER-14072)
The User Data block now properly cancels the wait event upon a successful transition. The cancellation occurs if the Timeout and Wait for Event properties are configured in the User Data block and the transition is successful (interaction.udata.changed is received). (COMPOSER-14097)
Supported Operating Systems
New in This Release
Corrections and Modifications
Important Note!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
This release contains the following corrections or modifications.
The Generate All operation is updated to deploy .NET Composer Project to Internet Information Services. (COMPOSER-13692)
Composer Java Project validation is updated to ignore Tomcat-generated_web.xml errors. (COMPOSER-13684)
The 8.1.4 workflow diagram upgrade is improved to handle Hints property values containing double quotes. (COMPOSER-13675/13663)
The .NET Project Web Service block internal server error for HTTP methods no longer occurs. (COMPOSER-13648)
The Assign Block Expression Builder now shows newly added variables. (COMPOSER-16631)
The Web Service Block code generation now generates the error.com.genesyslab.composer.webservice.badfetch error. Previously, Composer did not generate this exception. (COMPOSER-13602)
The Web Service block code generation now generates the error.com.genesyslab.composer error. Previously, Composer did not generate this exception. (COMPOSER-5431)
The Web Request block proxy properties are now used. (COMPOSER-13554)
The Prompt block now reads negative number currency. (COMPOSER-13511)
The interaction process diagram Interaction view Publish is updated for the default-limit segmentation option. (COMPOSER-5345)
The Generate All and Project Upgrade operations now validate the Project version. (COMPOSER-5425)
The detach property operation in the Email and SMS blocks is improved to poll for the presence of new interactions. (COMPOSER-5361)
Composer code generation no longer freezes when treatment blocks are connected in a loop. (COMPOSER-5318)
The Output Result property of the Web Service block now lists Project Variables for selection. (COMPOSER-5061)
The TLib block is temporarily disabled. Genesys recommends using the SCXML State block instead. (COMPOSER-13709)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
The ComposerBackend.dll file, for Composer .NET projects, has been recompiled in Release mode. Previously, the ComposerBackend.dll file was compiled in Debug mode and this might have caused performance issues. (COMPOSER-15604)
For Existing Projects: Importing and Upgrading the project will replace the old DLL file in the bin folder. Diagram file upgrades are not required for this update. To skip Diagram file upgrades, use the Uprgade Common Project Files option in the Upgrade Project dialog.
For New Projects: No additonal steps are required. All new projects will use the new DLL file.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
When creating an interaction process diagram (IPD) and defining Views in the Interaction Queue block, the following properties are now optional: Check interval (Main tab) and Default Segment limit (Segmentation tab). Setting empty values will not publish default-limit and freeze-interval in the Interaction View object. You must re-publish all the IPDs in order for these changes to take effect. (COMPOSER-14092)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
Important Note!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
To change this option, you must generate code for all the interaction process diagram files in a Project. By default, this option is not enabled. As result, older applications will continue to start the workflow diagram SCXML upon receiving the interaction.added event.
Note: This option should not be enabled for multimedia (non-voice) interactions.
(COMPOSER-13642)
This release does not contain any corrections or modifications.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
This release includes the following corrections and/or modifications:
Composer Web Request Block Input and Output parameters are now correctly transcoded in UTF-8 encoding format. (COMPOSER-13515)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
Important Note!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
Selecting Use Platform in the dialog sets the attribute value to true and instructs Orchestration Server to detach an interaction from the current session before routing to the specified target, which can free Orchestration Server to start processing the next session. Keeping the default Use Application does not use the detach attribute, in which case the <ixn:detach> tag will be used by the generated SCXML application.
Notes: Previously created Projects upgraded to this version will have the Use Application detach option and generate the <ixn:detach> tag for the detach operation. Also, the default value of the Detach property for the above Routing blocks is changed to true. Any new Routing blocks added will have the Detach property default set to true. Diagrams upgraded to this version will continue to have the previously set values for the Detach property.
For more information, see the Composer 8.1.4 Help, Preferences for Routing Applications, Detaching Interactions. Also see the Orchestration Developer's Guide, Orchestration Extensions chapter, Interaction Interface Action Elements section, <redirect> Action. (COMPOSER-5331)
This release includes the following corrections and/or modifications:
When you export a Java Composer Project as a .WAR file, diagrams (callflow, workflow and interaction process diagram (IPD)) are no longer exported. Previously, only callflow diagrams were not exported. (COMPOSER-4652)
Composer improves its handling of detach scenarios. You are no longer prompted to add an interaction.deleted handler when setting a Detachable block Detach property to true. The interaction.deleted event handlers are updated with a guard condition that checks events that are recognized as the result of a detaching operation. (COMPOSER-5293)
The Detach property in the Queue Interaction block no longer resets the Detach property value to false. (COMPOSER-5429)
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 8.1.400.33 release of Composer.
Important Note!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
This release includes the following corrections and/or modifications:
After a Composer 8.1.4 Project upgrade, chat workflows now successfully re-generate code. (COMPOSER-5326)
After a Composer 8.1.4 Project upgrade from an 8.1.3 version, interaction.present handlers are now updated. (COMPOSER-5324)
A Composer 8.1.4 command line Project upgrade now updates the Project version. (COMPOSER-5319)
The interaction process diagram (IPD) handler no longer incorrectly sets system.ThisDN to the agent extension when a called is held. (COMPOSER-5308)
The Workbin block, Private View object now has view/WorkbinView=true so that interactions no longer get pulled from Private Views. The Workbin block, Custom View object for a Private Queue, now has view/WorkbinView=false so that interactions will now get pulled from this view. (COMPOSER-5299)
Composer-generated code for a disabled and unconnected block no longer causes Orchestation Server compile errors. (COMPOSER-5285)
In the Project/Application Variable dialog, validation of variable names is now case-sensitive. (COMPOSER-5244)
Composer IPD Diagram event handlers now support ISCC-transferred Consult calls for Voice. (COMPOSER-5232)
Diagram upgrades from 8.1.1 do not support the implicit block variables and this has been documented in the Upgrading Projects and Diagrams section of the Composer 8.1. Deployment Guide. (COMPOSER-4735)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
This release includes the following corrections and/or modifications:
Email Interactions no longer get stuck during an Interaction Server switchover from primary to backup. Interaction process diagram (IPD) system event handlers are updated in this release to listen for re-queued interactions after a switchover happens. Genesys recommends using interaction process diagrams with interaction.added event handlers for Voice interactions and interaction.present event handlers for eServices interactions.
IPD template diagrams in this release are updated to create Voice, eService and interaction-less handling diagrams with appropriate event handlers. For example, the eServices IPD template will have interaction.present and the Voice IPD template will have interaction.added in the Events property.
IPD Diagram Upgrade
IPD system handlers in the Events property are updated in this release. To obtain this change, follow the steps below.
From 8.1.3 versions to this version:
A Composer Project Upgrade will automatically upgrade the IPD diagrams. No other manual changes are required.
IPD diagrams handling eServices interactions have the interaction.present event instead of the interaction.added event in the Events property. Use the IPD diagram Events property dialog to add or remove appropriate events.
If interaction.present was already handled in the diagram, follow the below steps to update it manually.
From 8.1.4 versions to this version:
IPD diagrams handling Voice interactions do not require any changes.
IPD diagrams handling eServices interactions update the Events property to have the interaction.present event instead of the interaction.added event.
If interaction.present was already handled in the diagram, follow the below steps to update it manually.
When using a DB Data block, database errors (such as failure to connect to a database) no longer result in invalid JSON messages being returned to the workflow or callflow application, which could cause the application to fail. This release corrects the issue with an update to the database access library. (COMPOSER-5257)
Parameters for multiple stored procedures are now organized and are no longer shown as duplicates in Composer's Stored Procedure Helper if there are duplicate stored procedure names and the current user has access to those objects. (COMPOSER-5260)
Previously, the Classify Interaction and Screen Interaction blocks in a workflow diagram did not validate variables, which could cause an application to fail if invalid variables existed. This release fixes this issue by adding variable validation. (COMPOSER-4907)
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.4 release of Composer.
Important Note!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
In previous versions, when creating an ICM-enabled Composer Project, ICM variables were not added to the Entry block of the main callflow. This behavior is fixed in Composer 8.1.4 and ICM variables are added correctly when the Project is created. (COMPOSER-4722)
The WAR file export wizard is changed to show more accurate error messages if it encounters errors during export. Previously, it could display a generic error message. (COMPOSER-4681)
While upgrading older Projects in Composer 8.1.3, there could be cases where an upgraded diagram displayed a validation error marker complaining about not being able to open a referenced diagram. This is fixed in Composer 8.1.4. (COMPOSER-4719)
Configured proxy settings are now propagated to generated code as expected for both Java and .NET Composer Projects. Previously, although the settings were displayed in the Web Services block, because they were not propagated, they were not used during runtime. (COMPOSER-4962)
Previously, validations did not catch cases where variables were not specified as output parameters to store values. This could lead to runtime errors during calls. In Composer 8.1.4, validations are added to the output variables dialog to catch these errors. (COMPOSER-4669)
In Composer 8.1.3 and earlier versions of Composer, the Project Upgrade task dialog did not show task progress. This behavior is fixed in Composer 8.1.4. (COMPOSER-4667)
Composer now correctly updates variables mapped in the Log Block/Logging Details property. (COMPOSER-4574)
Diagram validation is now implemented when prompts are missing according to the Number Of Retries Allowed property value. (COMPOSER-4535)
The check box and text field of the Encryption user interface in the Database Connection Profile no longer becomes editable when switching on the different Connection Profiles. (COMPOSER-4238)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality. After installing Release 8.1.301.02, you must perform a Project Upgrade and an Interaction Processing Diagram (IPD) Upgrade.
Project Upgrade
The common include/*.js files and diagram code generation will get updated with this process.
IPD Upgrade
IPD system handlers in the Events property are updated in this release to initialize system variables. To obtain this change, follow the steps below to manually update an IPD.
This release includes the following corrections and/or modifications:
Parameters for multiple stored procedures are now organized and are no longer shown as duplicates in Composer's Stored Procedure Helper if there are duplicate stored procedure names and the current user has access to those objects. (COMPOSER-5248)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality. After installing Release 8.1.301.01, you must perform a Project Upgrade and an Interaction Processing Diagram (IPD) Upgrade.
Project Upgrade
The common include/*.js files and diagram code generation will get updated with this process.
IPD Upgrade
IPD system handlers in the Events property are updated in this release to initialize system variables. To obtain this change, follow the steps below to manually update an IPD.
This release includes the following corrections and/or modifications:
IPD system handlers in the Events property are updated in this release to initialize system variables for the Mute Xfer case. (COMPOSER-5117)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
This release includes the following corrections and/or modifications:
In previous releases of Composer, sub-workflow Entry block initialization did not correctly preserve the value of the InteractionID system variable if it was changed after the workflow started executing. This is now fixed by changing the initialization to not update system variables. (COMPOSER-5099)
If Single-Session treatments (see Release 8.1.300.92) were enabled in Composer 8.1.3, and if an Orchestration Server session was recovered while the Disconnect block was being executed, this situation could result in the Orchestration Server session getting stuck. This release of Composer now properly handles this scenario so that ORS sessions are correctly terminated. (COMPOSER-5102)
In previous releases of Composer, in certain scenarios, the Classify Interaction block could incorrectly assume a classification match. The Classify Interaction block now properly returns a no-match if classification results return a no-match. (COMPOSER-5101)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality:
Important Note!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
This release includes the following corrections and/or modifications:
In this release, bundled audio resources now have the proper encoding and play correctly on GVP. Running an upgrade of the Project with Common File Upgrade checked will update files in existing Projects. (COMPOSER-5054)
You can now set a language in the Prompt block even if it is the default Project language. In earlier versions of Composer 8.1.x, setting a language explicitly in the Prompt block could result in a runtime script error. (COMPOSER-5055)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality.
This release includes the following corrections and/or modifications:
In earlier versions of Composer, including previous 8.1.3 versions, if the Interaction Queue block used an existing queue, and the Project was imported into Composer, published information was cleared from the interaction process diagram. This resulted in incorrect code generation and validation errors. Composer now uses the selected queue property rather than the published object information. (COMPOSER-5064)
The Business Rules block now works correctly with fully-qualified classnames in GRS rule packages. In previous versions, the package name was always prepended and this would cause the request to fail. (COMPOSER-5044)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality.
Important Note!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
This release includes the following corrections and/or modifications:
In previous releases of Composer, the Web Request block did not correctly decode the "+" character in the response. This issue has now been fixed. (COMPOSER-5049)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. After installing Release 8.1.300.78, you must perform a Common File upgrade only if the single VXML session model is being used as described below.
This release contains the following new functionality.
This release includes the following corrections and/or modifications:
When building an expression in Composer's Expression Builder, selection of operational parameters no longer adds parentheses at the end. (COMPOSER-4688)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new functionality.
Important Note!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
This release includes the following corrections and/or modifications:
Configured proxy settings are now propagated to generated code as expected for both Java and .NET Composer projects. Previously, although the settings were displayed in the WebServices block, because they were not propagated, they were not used during runtime. (COMPOSER-4962)
In previous versions of Composer 8.1.3, parameters could not be edited if the Type property was set to URL. This issue is resolved and parameters can be edited. (COMPOSER-5001)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features/functionality:
Important Note!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
This release includes the following corrections and/or modifications:
An application could be blocked when executing a UserData block if no appropriate interaction.udata.changed event was received. This may occur due to race conditions on the platform as well as for other reasons. To address this case, the UserData block now has a Timeout property, which defines the maximum amount of time to wait for the interaction.udata.changed event before transitioning to another block. (COMPOSER-4947)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains the following new features/functionality:
Important Note!
Whenever a Project is imported into the workspace as part of the process of upgrading to a newer version, you must perform a Project Upgrade. Composer applications will not work or will work unpredictably unless the Project is successfully upgraded.
This release includes the following corrections and/or modifications:
ThisDN variable initialization logic has been changed to assign the system.StartEvent.data.focusdeviceid value. If the focusdeviceid value is not present, the DNIS value will be assigned. (COMPOSER-4893)
This release optimizes system.InteractionID initialization logic to assign the value of the effective interaction (system.StartEvent.data.interactionid) instead of the parent interactionID. (COMPOSER-4857)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. After installing Release 8.1.300.56, you must perform a Common File upgrade.
This release contains the following new features/functionality:
This release includes the following corrections and/or modifications:
In previous versions of Composer 8.1.2 and 8.1.3, the Wait block did not transition correctly for certain events and always used the default transition. This is now addressed so that the correct transitions are taken as depicted in the diagram. (COMPOSER-4870)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. After installing Release 8.1.300.54, you must upgrade your Composer Projects.
This release contains the following new feature/functionality:
This release includes the following corrections and/or modifications:
Previously, the Attach block did not work correctly when the ixnid was specified using a variable as it did not take into account the scope of the variable. This issue is now fixed. (COMPOSER-4806)
Earlier versions of Composer 8.1.3 did not generate the correct format of SOAP messages if the service endpoint did not accept any parameters. This issue is now fixed. (COMPOSER-4809)
Previous Composer 8.1.2 and 8.1.3 versions failed to connect to databases in .NET Composer Projects if the connection profile had special characters in it. In this release, this issue is fixed in the .NET support code. (COMPOSER-4803)
The implementation of the getuData(key, ixnid) function implementation is changed to use the system.InteractionID if an ixnid is not specified. Previously, the function used to infer the "current" interaction based on the last interaction-related event received by the session. The new implementation is more predictable and reliable. (COMPOSER-4836)
Earlier versions of Composer 8.1.3 ignored the Transfer Audio property in the Transfer block if the Type was set to Consultation. This behavior is now fixed. (COMPOSER-4854)
Support for using variables of type Input is added to the Custom SOAP Envelope property of the Web Service block. (COMPOSER-4831)
Previously in Composer 8.1.3, the Custom SOAP Envelope was incorrectly propagated to any custom blocks. This issue is now fixed and the Custom SOAP Envelope is not stored in a custom block definition. (COMPOSER-4855)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. After installing Release 8.1.300.51, you must upgrade your Composer Projects.
This release contains the following new features or functionality:
This release includes the following corrections and/or modifications:
Previously, resetting an interaction process diagram's published information (from Project settings) would, in certain cases, reset the Route Interaction block's Workbin property. This issue is fixed. (COMPOSER-4791)
View segmentation in interaction process diagrams for chat was using the msgbased object in Composer 8.1.3. This has been changed to fall back on xdata and now works correctly for both chat and e-mail interactions. (COMPOSER-4787)
The QueueQuery and QueueCancel subroutines in Composer previously used JSON.eval(), which caused an error in Orchestration Server. These are changed to use only eval(), which is compatible with ORS. (COMPOSER-4760)
In previous versions of Composer 8.1.3, the upgrade process changed SCXML State blocks with target-less transitions into transitions with targets. This issue is fixed in the upgrade feature to preserve the target-less nature. (COMPOSER-4768)
Previously, Composer encountered an issue when Genesys Rules Development Tool plugins were installed. If a Template Project was created, and many items were added to the rules template, the user could experience a slowdown when saving from the rules template editors. This issue is fixed. (COMPOSER-3590)
Switching the default locale in Composer voice Projects did not update the default language settings in callflow diagrams in previous versions of Composer. This version of Composer propagates this change to specified callflow diagrams to keep them in sync with the Project-level default locale. (COMPOSER-4755)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and/or modifications:
In previous releases of Composer, parameter synchronization did not work correctly in the SubDialog block for Genesys Voice Platform applications if the SubCallflow had multiple Exit blocks returning parameters. Previously, this resulted in a runtime error on GVP and is addressed in this release. (COMPOSER-4736)
In previous releases, an exception dialog was displayed in the Prompts Manager if the highlighted Project contained ICM variables. It did not impact the runtime behavior of the application. This issue is now fixed. (COMPOSER-4737)
Automatic upgrade of Orchestration diagrams did not work correctly for Queue properties of certain blocks during an upgrade from 8.1.2 to 8.1.3. Issues were not listed in the Project upgrade report. This issue is now fixed. (COMPOSER-4738)
Previous releases of Composer 8.1.3 could not launch a new debugging session on OS X immediately after the previous session was forcefully/manually terminated. An error, Address already in use, was displayed. A new session could only be started after 30 seconds. This issue is now fixed. (COMPOSER-4742)
The Web Service block is enhanced to allow control over prefix generation for method and attribute elements. Prefix generation, its scope, and the prefix itself can be specified via new advanced properties. (COMPOSER-4727)
In previous releases, Stat Server names could only be specified as literals or selected from Configuration Server in the Target or Route Interaction blocks. This release adds support for specifying Stat Server as a variable. (COMPOSER-4721)
In previous releases, the system.LastSubmitRequestId variable was not updated if an error event was received in the Target block. It tracked requests only if they were successful. This behavior is changed and the variable now also tracks failed requests in the Target block. (COMPOSER-4718)
This is an optimization. The Branching block would previously fire an internal event to transitions in the default case, which logged an unexpected event entry in Orchestration Server logs. Now all branches use this event. There is no change in the block functionality. (COMPOSER-4714)
In previous releases, floating blocks were not detected if one of their multiple outputs was not connected, which led to invalid code being generated in some cases. This issue is now fixed. (COMPOSER-4726)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and/or modifications:
The Validate All operation in Composer 8.1.3 used to error out while validating objects in Universal Contact Server/Context Services referenced in multiple workflows and Context Services validation was switched on. This was caused by a limitation in the third-party library used to invoke Context Services APIs. This version of Composer switches to a different library that does not have similar constraints, which resolves the issue. (COMPOSER-4707)
Previously in Composer 8.1.3, in certain cases, an application upgraded from a previous release would remain stuck in the interaction process diagram and not enter the workflow if one or more system event handlers, including the global exception handler, were defined. This issue is now resolved and workflow processing is started correctly. (COMPOSER-4701)
A new attribute, Extensions, is now available in interaction process diagram properties. This attribute allows arbitrary attributes to be added to the root <scxml> element and is used by Orchestration Server to control persistence, session recovery, and other functionality. Refer to Orchestration Developer's Guide for more details. (COMPOSER-4698)
Supported Operating Systems
New in This Release
Corrections and Modifications
Note: Mac OS X is a partially supported platform. Support for Mac OS X is removed from this release. It is now available as a restricted release with a separate installation package. Contact your Genesys representative to request it.
There are no restrictions for this release. This section describes new features that were introduced in the 8.1.3 release of Composer.
Support for Eclipse 3.7 (Indigo) and 4.2 (Juno).
Composer is installed as a set of plug-ins.
Localization support. Language Packs that provide translations for Composer can now be produced and then installed on top of Composer, allowing Composer to run in languages other than English. Localization of generated VXML and SCXML applications is also supported.
Mac OS X is not a supported platform. This release previously indicated that MAC OS X was a partially supported platform.
Database passwords in Connection Profiles can be encrypted.
Common-bundled Composer Project files can be updated at any time.
Command line code generation.
Composer Projects can track change revisions, and revision history can be viewed by the user.
Customizable global system event handlers in interaction process diagrams.
New properties in the Target block to support updating the DN of the reserved resource to include the access code returned by Universal Routing Server.
The ECMAScript block is now also available in callflow diagrams, similar to its workflow/IPD counterpart.
New blocks for workflow diagrams:
Voice and Route:
This release includes the following corrections and/or modifications:
SOAP Web Services blocks no longer throw an exception during parsing the specified WSDL. In earlier versions, an exception was written to logs, but there was no impact to functionality. (ER# 316271385, COMPOSER-4251)
Encryption settings in the Database Connection Profiles editor are enabled correctly while switching between multiple profiles. Previously they were enabled in some cases even if the current profile did not have encryption switched on. (ER# 315824841, COMPOSER-4238)
Blank entries are no longer displayed in the dialog for customizing perspectives. This issue has been addressed in Eclipse Juno and Indigo. (ER# 306242508, COMPOSER-4001)
Any interactions routed to a Workbin are correctly depicted in the corresponding interaction process diagram. Previously, they were not shown.(ER# 302446063, COMPOSER-3951)
Transport Layer Security connection now works correctly for Context Services (COMPOSER-3582, COMPOSER-3358, ER# 276671871)
Debugging over a secure connection now works in a 64-bit operating system. (COMPOSER-3358, ER# 283883750)
The VXML editor now generates the genesys prefix for GVP-specific attributes. (COMPOSER-657)
Interaction process diagrams are automatically refreshed when IPD Publish Information is reset. (COMPOSER-2849)
.NET Composer Projects now properly create quotes for non-numeric variables when submitting SQL queries. (COMPOSER-1802)
Oracle Database errors are now correctly handled by the Composer backend, and will be reported as an error event in the voice or routing application. (COMPOSER-2740)
Composer now shows a warning if logging details are not provided in the Log block. (COMPOSER-2439)
Composer no longer shows a warning when exporting a Java Project as .WAR file. (COMPOSER-3501)
The Composer Help for the Create User Announcement block, Announcement ID property, now states to select a variable or enter a literal value. (COMPOSER-3557)
The dialog for the Output Queue property now shows all queues from the interaction process diagram, including unpublished queues. (COMPOSER-3119)
The Composer Help adds information on using a string variable to pass a number value to the PlayBuiltinType.js functions. For more information see Known Issue COMPOSER-713.
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release contains no new functionality
This release includes the following corrections and/or modifications:
This release corrects the getWebRequestData.jsp file so that it can now receive input JSON data in UTF-8 format. For Projects created prior to 8.1.2, upgrade the Project using the Upgrade Composer Project option. For Projects created in 8.1.2 releases, manually update the include/getWebRequestData.jsp file from a new Java Composer Project. (COMPOSER-5159)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and/or modifications:
This release fixes SCXML code generation so that the max_digits attribute of a voice treatment is properly handled as a number. (ER# 324973720) (COMPOSER-4630)
This release fixes VXML code generation to use the proper Locale path. (ER# 325225741) (COMPOSER-4598)
When using DB Data blocks, thread usage is optimized. Composer now creates a separate thread pool for each application context thereby preventing any possible thread leaks. To apply this fix to an existing Project, update the WEB-INF/web.xml to add the following:
<!-- initializes a thread pool when starting up the servlet context -->
<listener>
<listener-class>
com.genesyslab.studio.backendlogic.ComposerServletContextListener
</listener-class>
</listener>
Alternatively, create a new Java Composer Project, and copy its WEB-INF/web.xml into the existing Project. Also, update the gvpBackend.jar file in any application servers by copying it from the Composer-installed bundled Tomcat. (ER# 324725503) (COMPOSER-4550)
This release addresses three database-related issues when using the Stored Procedure Helper:
For some database configurations, the connection profile created in Composer's Connection Profile Editor did not work for both the JDBC design-time environment and the .NET runtime environment. To increase flexibility, the .NET connection string is now editable in the Connection Profile Editor.
When enabling the Custom Connection String checkbox, the text field containing the connection string becomes editable. In particular, the Password string needs to be edited from the masked value ("***") to the actual password. Alternately, the password and username can be provided using runtime values by setting them in the Connection Properties field of the DB Data block.
Composer's Stored Procedure Helper now properly handles a NullPointerException when connecting to a database schema containing only synonyms.
(ER# 322104204)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and/or modifications:
View segmentation logic in Interaction Queues reverts back to using an xdata view property instead of a message-based object. This is the same behavior as Composer 8.1.1 and works consistently for e-mail and chat interactions. (ER# 322059214)
Composer no longer displays a validation error for media servers due to an invalid check when connected to a single-tenant configuration server. (ER# 321651173)
The Target and Route Interaction blocks can now be used without an interaction to reserve a target in advance. Previous versions of Composer did not have this capability even though a null interaction ID could be specified in the block via a variable. (ER# 321867315)
The structure of subroutines bundled with Composer is changed to address an infinite loop issue introduced due to incorrect exception handling. If upgrading Projects created in 8.1.1 and earlier with this build, Composer will upgrade the subroutines to the new structure. For Projects created in earlier builds of 8.1.2, create a new Project and copy over the affected SCXML files from the /src folder of the new Project into the older Project. (ER# 322770841)
Supported Operating Systems
New in This Release
Corrections and Modifications
There are no restrictions for this release. This release does not contain new features or functionality.
This release includes the following corrections and/or modifications:
In the 8.1.201.52 release, Composer required you to connect workbin views to one or more workflows. Floating workbins are now allowed that are not required to be connected to Workflow blocks. This allows interactions routed to workbins to remain in workbins until they are pulled out by agents. (ER# 318899681)
An out-of-bounds index error is no longer displayed if an Entry block variable begins with the restricted prefix of App_. The prefix remains restricted, but Composer now gracefully handles the situation. (ER# 318601911)
Previously, generated SCXML for eServices blocks that set Detach property to True did not execute correctly on Orchestration Server (ORS) due to the use of an initial attribute. Code generation is changed to use the initial element to avoid this issue on ORS. (ER# 318539081)
In the 8.1.201.52 release, the callflow Record block exited the session if the user disconnected during recording, thereby preventing any non-media operations to be performed. The block is now changed to enable handling the disconnect event and continue with non-media operations. (ER# 318899695)
In the 8.1.201.52 release, upgrading a .NET Composer Project did not overwrite the web.config file to preserve any user-added custom entries. This behavior is changed to rename the previous web.config file to web.config.bak.<timestamp>. A new file is added to the Project that includes any new entries added in the 8.1.2 release. (ER# 318898346)
In previous releases, the Web Service block would only process schema (.xsd) files that were included by the last schema at each level in a multi-level schema inclusion scenario. Composer now correctly processes all included schemas in the hierarchy. (ER# 318918677)
Previously, Email blocks relied on receiving a specific sequence of events from ORS. Under certain circumstances, events from ORS are not received in the expected sequence resulting in an application waiting indefinitely for events. Generated code for these blocks is changed to not rely on the sequence of events. (ER# 318696011)
The TenantId system variable is now correctly initialized for non-voice interactions in interaction process diagrams. (ER# 318539084)
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 8.1.2 release of Composer.
Common Features Across Applications:
The Composer Help is available on the Genesys Documentation. As a result, users can access the most up-to-date information. A Japanese version of the Composer Help is also available. To switch to the Japanese help, change a Composer preference as follows:
The Business Rules block works directly with Genesys Rules Engine and does not require going through the Genesys Rules Authoring server at runtime. This simplifies the usage of Genesys Business rules in Orchestration workflow (SCXML) or Voice callflow (VXML) applications.
Enhancements made to Database blocks support Database clusters and secure connections; this enables users to connect to Oracle RAC and SQL clusters.
Database Connections can use service names in addition to SIDs. Connection strings can be dynamically generated and support variables. This helps developers to simplify the usage of database connections.
Blocks in either SCXML or VXML can be disabled. For example, you may wish to temporarily remove a block during debugging or during development. Disabled blocks do not participate in the application at runtime.
New properties for Logging are available for all blocks. Additional support for Alarms is added to workflows. This feature allows developers to minimize insertion of Log blocks and improves readability.
Support for Outbound Campaigns in callflows. New Outbound blocks enable callflow applications to update, add or delete records in Campaign Calling Lists and work as a solution in tandem with Genesys Outbound Solutions. Users can also update Do Not Call lists in an Outbound Solution through callflow diagrams.
Callflow applications (VXML) can use the Operation Parameter Module (OPM) and Audio Resource Management (ARM) features of Genesys Administrator Extension. OPM enables simplification of the overall solution by allowing business users to easily control and manage callflows.
This release adds a new utility function to access SIP header values in callflows.
A new VXML code block allows the embedding of VXML code directly into callflows through <subdialog>. This feature provides developers the flexibility to modularize callflow diagrams.
Users can specify custom formats for Voice prompts in a VXML applications. Custom formats can be created via ECMAScript functions in callflows.
Input and ICM variables defined in callflow Entry blocks are initialized to default variables if no value is supplied at runtime. This behavior is controlled by a flag. Older version of callflows will continue to have this flag reset to maintain backward compatibility.
Enhanced debugger support provides the ability to debug SCXML applications. The Composer interface provides full debugging functionality for Composer-generated and hand-coded applications.
New Outbound Campaign blocks support integration with Genesys Outbound Contact features, such as adding, deleting, and updating Calling List records; updating Do Not Call lists; and other Calling List manipulation features. This functionality provides more robust integration between Routing logic and Genesys Outbound Contact functionality.
New blocks support the SCXML <parallel> functionality allowing developers to define applications that can simultaneously perform multiple operations. Entry, Subroutine and Begin parallel blocks in workflows and sub-workflows support target-less transitions, which could be based on some condition.
Support for Genesys Administrator Extension Operation Parameters (OPM) and Audio Resource Management (ARM) functionality in SCXML applications. This feature simplifies the solution and provides control to the end user, addressing Total Cost of Ownership (TCO).
Voice Treatment blocks provide direct access to Extension data returned after treatment completion. Composer now supports Orchestration Server-based treatments instead of Universal Routing Server-based treatments.
Support for multiple views for Workbins and existing queues within interaction process diagrams (IPDs).
This release includes the following corrections and modifications:
New Projects now use UTF-8 as the default encoding. Previously, server-side pages in earlier versions of Composer incorrectly used ISO-8859-1 encoding, which caused issues with JSON data. (ER# 308306201)
The Troubleshooting Overview in the Composer Help now includes a link to the Checkin Error Source Control topic. (ER# 302896571)
Email blocks no longer continue to wait for an interaction.udata.changed
event when the Output Result property is set to User Data. (ER# 302549675)
When deleting Workbin blocks from an IPD, the corresponding Script object is now deleted from Configuration Server. (ER# 302446061)
When the IdentifyContactVariables Mapping property is set, its user defined value is no longer overwritten, causing the variables mapping definition to be lost. (ER# 302251369)
Email blocks in workflows are now reflected correctly in any interaction process diagrams that refer to the workflow diagram. If the Email block puts the email interaction into an interaction queue, the corresponding Interaction Queue block in the interaction process diagram is correctly linked to the Workflow block. (ER# 302045214)
Renaming a file in a Composer Project and removing the file extension no longer causes an exception. (ER# 301882373)
When an Interaction Queue block is updated with a different name, any linked blocks connected to it are now updated correctly. (ER# 297853293)
The color of the Stop Interaction block and Log block is now consistent with other action blocks. (ER# 297461273)
You can now enter numeric values when using the Test function in the Business Rule block Facts property dialog. (ER# 284482622)
Non-primitive data types used by the Genesys Rules Server are now displayed
as Custom
in the Business Rule block Facts property dialog. (ER# 284095003)
Any diagram upgrade failures are now reflected in the overall Project upgrade outcome. Previously, Composer did not consider results of all diagrams being upgraded as part of a Project upgrade, and in certain cases reported inaccurate overall outcome of the upgrade process. (ER# 284081684)
The F1 context-sensitive help key now correctly points to the corresponding help documents for various blocks, including (but not limited to) Business Rule, ICM Route Request, & ICM Interaction Data blocks. (ER# 283515625)
.NET Composer Projects no longer shows this warning in the Console View:
include\getWebServiceData.aspx(482): warning CS0618: 'Microsoft.Web.Services3.SoapContext.Security'
is obsolete: 'SoapContext.Security is obsolete. Consider deriving from SendSecurityFilter
or ReceiveSecurityFilter and creating a custom policy assertion that generates
these filters.'
(ER# 277966454)
The user is no longer allowed to enter literal text as the expression field of a parameter in the Backend block parameter dialog, because only variables are allowed during validation. (ER# 276267465)
The F1 context-sensitive help key now correctly brings up the corresponding help topic for workflow blocks. (ER# 262019584)
Objects published to Configuration Server are now deleted when you delete a Project. Composer now prompts for confirmation to delete individual objects, as well as allowing deletion of a subset. (ER# 257981054)
Objects published to Configuration Server are now removed when a Project is deleted. Composer now displays a list of objects to be removed and prompts for confirmation while deleting a Project. (ER# 248112964)
Composer now gives better control over deleting objects published to Configuration Server. A new dialog allows selection of individual objects that should be removed while deleting a Project or interaction process diagram. Composer also now uses a unique identifier to associate published objects with an interaction process diagram, so that it can identify the configuration objects to be more reliably deleted. (ER# 247524846)
The WebService block of Composer now supports xsd:complextype
for input parameters in WSDL files. Composer now also supports complextype,
imported schemas, and SOAP arrays. (ER# 242559091)
When Web Service block's Map Output Values To Variables
is set
to true
, and the Web Service result contains one or more arrays,
results are now parsed correctly. To help accomplish this result, Composer now
supports the maxoccurs=unbounded
attribute. (ER# 232103181)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections/modifications:
Composer-generated SOAP requests no longer wrap complex object properties individually in parent tags. Composer now encloses all complex object properties together in a single parent tag. Because this change introduces new internal (hidden) properties, you must reconfigure existing Web Service blocks that are affected by this change. To reconfigure, use the instructions in ER# 317421329.
(ER# 316111385)
Using WSDL files with multiple levels of referenced schemas previously resulted in WSDL parsing errors. To correct this, the Web Service block adds support for multiple levels of schema includes. Because this change introduces new internal (hidden) properties, you must reconfigure existing Web Service blocks that are affected by this change. To reconfigure, use the instructions in ER# 317421329.
Note: Web Service block-generated SOAP messages do not have a prefix in the SOAP elements. As a result, Web Services created using the Metro/JAX-WS Framework will return Null Pointer Exception or Unexpected Result due to the prefix limitation.
(ER# 317140695)
The Web Service block now supports multiple levels of schema includes. As a result, parsing WSDL files with multiple levels of referenced schemas no longer generates WSDL parsing errors. Because this change introduces new internal (hidden) properties, you must reconfigure existing Web Service blocks that are affected by this change. To reconfigure:
(ER# 317421329)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections/modifications:
Previously HTTP basic access authentication was not recognized correctly by Server-Side pages, which resulted in Web Service block failure. This issue has been resolved. (ER# 311778148)
The Transfer block now correctly uses the specified transferaudio when the Type is set to consultation. Previously the block ignored transferaudio. (ER# 313355139)
Previously a database timeout of less than 10 seconds resulted in the event being received after 10 seconds due to delays in closing connections in database libraries. Composer-provided backend libraries now handle this behavior so that timeout events are correctly received by the application. (ER# 314222379)
The ordering of different type of variables in the Entry block of callflow diagrams is fixed so that interdependencies are resolved. This fix also resolves an issue with the user interface when reordering a long list of variables. (ER# 307294303)
Server-Side pages in earlier versions of Composer incorrectly used ISO-8859-1 encoding, which caused issues with JSON data. The encoding has now been changed to UTF-8. New Projects will use UTF-8 as the default encoding.
Note: Server-Side pages in existing Projects must be replaced by pages copied from a new Project. (ER# 310206275)
The Target and Force Route blocks add a new RouteType, Unknown. (ER# 314293536)
All Routing blocks and eServices blocks that support Detach now have a new property to specify a list of events that will be ignored for the duration of the block. (ER# 314293690)
When multiple Business Rule blocks are used in the same diagram, duplicate internal states are no longer generated. (ER# 314139581)
The Target and Route Interaction blocks add a new optional property to introduce a delay after Universal Routing Server interactions. This delay is needed under certain circumstances when interactions are detached from the current session before they are routed. (ER# 314293737)
The Play Application block adds support for retrieving extensions returned as part of treatment execution. Additional support is added for Orchestration Server providing this treatment instead of Universal Routing Server. (ER# 314293729)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections/modifications:
The Common.js file now uses the correct condition to determine if a given expression is a URL. Previously, the code did not correctly identify rtsps:// URIs. (ER# 303846000)
The Looping block no longer generates incorrect code when using a variable to iterate over a JSON array returned from the DB Data block. (ER# 304673224)
Debugging callflows that point to a root document no longer prints an error in the console indicating that JSON is not defined. Previously, an error was printed, although it did not impact functionality. (ER# 304817528)
The getuData() function is fixed to handle cases where an Interaction ID is not passed to it. (ER# 305526167)
Creating a new List in a new folder via the List Object Manager correctly displays the new List and does not require a reconnect to Configuration Server. Previously, it was necessary to disconnect and reconnect to Configuration Server to see the newly-added List object. (ER# 302737632)
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 8.1.1 release of Composer.
New features for creating SCXML-based routing applications include:
New features for creating voice applications for GVP:
New Voice & Route Application Features:
This release includes the following corrections and/or modifications.
The Menu block can now use the utterance value from the menu's shadow variable instead of the return value. Previously, it always used the return value. (ER# 291115929)
Exporting custom tools from earlier versions of Composer no longer throws an error during the export process. (ER# 288108575)
The Send Email block works correctly with literal e-mail addresses in the From and Exclude fields. (ER# 302719396)
Stored procedure parameters are correctly displayed even if the current user does not own the schema object. In earlier versions of Composer, parameters were not displayed in such scenarios. (ER# 295759667)
The list of network interfaces is correctly displayed in Debugger Preferences if the IP address of the previously selected interface is changed. (ER# 292795735)
The Play Application block now works correctly when the Resource property is specified as an application variable. (ER# 297745227)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections/modifications:
Server-side pages in earlier versions of Composer incorrectly used ISO-8859-1 encoding, which caused issues with JSON data. When attempting to parse such JSON data, Media Control Platform's <data> generated a semantic error. The encoding is changed to UTF-8. New Projects now use UTF-8 as the default encoding. This hot fix requires updating existing Projects created in Composer 8.1.010 as well as certain DotNet Projects. See 8.1.010.47 in Known Issues and Recommendations. (ER# 308306201)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections/modifications:
The Microsoft JDBC driver bundled with Composer is upgraded to version 4.0, which supports secure database connections. (ER# 306452061)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and/or modifications:
Parameters can now be included in the URL in the Web Request block. The block forms the URL correctly if no querystring parameters are specified via the Parameters property. (ER# 298946580)
The Play Application block generates correct code when Resource is specified as a variable. (ER# 301070763)
The Project Upgrade operation upgrades the correct set of files for the Web Service block and does not generate errors for missing files. (ER# 296440651)
The Web Service block supports all Namespace prefixes defined in imported schemas in WSDL files. (ER# 300878082)
Prompts specified as URLs (http, https, rtsp), where Type=Variable and Interpret-As=Audio, are no longer treated as local files in generated VXML code.(ER# 300283881)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections/modifications:
Composer adds support for WSDL Imports and WSDL types Schema Import. In addition, the following features are added: the ability to handle prefixes based on the elementFormDefault attribute, support for the <extension:base> tag, and prefix filtering in the incoming Web Service response. (ER# 292537753, 293146654)
When working with parameters in the Web Service block, Composer now preserves the Input Parameters list if the option to not synchronize parameters is selected. (ER# 292428744)
This release fixes the behavior of the Prompts dialog box so that Type can be Value and Interpret-As can be set to Text. (ER# 294162443)
This release fixes <sequence> tag processing. In addition, the following features are added: support for WSDL Imports and WSDL types Schema Import, the ability to handle prefixes based on the elementFormDefault attribute, support for <extension:base>, and the addition of the <Complex:type> tag. (ER# 294201141)
Composer adds support for WSDL Imports and WSDL types Schema Import in addition to the ability to handle prefixes based on the elementFormDefault attribute, support for the <extension:base> tag, and prefix filtering in the incoming Web Service response. This fixes the issue where certain input parameters were not displayed in the Input parameters dialog of the Web Service block. (ER# 289607635)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following correction/modification:
A new Entry block optional variable, USE_LCASE_USERDATAKEY, is added to control the case lookup of session.com.genesys.userdata. By default the value of this variable is 0, which instructs Composer to use the original case of the UserData key to get the array value. When the variable is set to 1, the generated VoiceXML code uses a lowercase key lookup. This modification addresses a change in GVP's Media Control Platform starting with 8.1.410.24+, where the default behavior is not to convert UserData SIP headers to lowercase. (ER# 288596235)
Supported Operating Systems
New in This Release
Corrections and Modifications
This is a hot fix for this product. This release does not contain new features or functionality.
This release includes the following corrections and/or modifications:
Composer no longer displays a timeout dialog when the connection to Universal Contact Server stays idle. (ER# 284482624)
When upgrading an 8.0.x Project to 8.1, Composer now allows underscores in database connection profile names. (ER# 285335211)
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 Composer.
An Email Response block combines the functionality of IRD's Acknowledgement, Autoresponse, and Create Notification objects.
A Chat Transcript block allows you to generate a reply e-mail to a chat interaction and attaches a chat transcript.
An Email Forward block combines the functionality of IRD's Forward E-mail, Redirect E-mail, and Reply E-mail from External Resource objects.
A Screen Interaction block allows you to screen a text-based interaction for specific content (specific words or patterns), and then (optionally) segment the interaction to different logical branches based on the result of the screening query.
A Classify Interaction block allows you to classify a text-based interaction based on content, and attach one or more Classification categories to the interaction.
For classification segmentation, an ECMAScript function determines if a particular category name or ID exists in the array of category objects represented by an application variable. This variable can be the output of the Classify Interaction block, enabling the Branching block to be used for segmentation based on category.
For manually attaching categories to an interaction, the User Data block can be used and then a branching block can be (optionally) used to segment interactions to different logical branches based on the different categories.
An Update Contact block allows you to update customer profile information in the UCS Database, based on data attached to an interaction.
An Identify Contact block can identify a contact based on the interaction User Data; return a list of matching Contact IDs based on the User Data; create a contact record in the UCS Database with information in the User Data if a matching contact is not found; or update the UCS Database record of the matching contact with information from the current interaction's User Data.
A Create Interaction block allows you to create an interaction record in the Universal Contact Server Database for a customer contact. This saves the current interaction being processed by the strategy in the database.
A Render Message block provides the ability to render Field Codes in arbitrary text.
Composer's existing Create E-mail block is enhanced to allow you to: pick up standard response text from User Data; specify that the "To" address be picked up from the Customer Profile in the Universal Contact Server Database; and use Field Codes in standard responses that will later be filled in with user-specific values.
Composer's existing Route Interaction block now allows you to create applications where routing is based on schedules from Genesys Workforce Management.
The Flow Control palette for routing applications contains a new SCXML State block. When used in a workflow diagram, it allows you to write custom SCXML code that Composer will include in the SCXML document that it generates based on the workflow diagram.
The Flow Control palette for routing applications contains a new User Data block for updating an interaction's User Data and for attaching Business Attributes, Categories, and Skills.
When an interaction process diagram (IPD) uses a Workflow block, if the referenced workflow diagram contains an eServices block that names a server performing an action or operation, Composer adds a visual indicator in the form of a node (similar to an IRD strategy-linked node).
When developers work with Context Services, Composer accepts HTTP basic authentication credentials and uses them for authentication, including digest authentication for working with Web Services.
You can now use variables in Skill Expression Builder. You can also disable Skill Expression validation from the Configuration Server preference page.
You can now include your own custom JavaScript ( *.js)
files in workflows by placing them in the /include/user
folder.
The JavaScript functions in the specified .js file can then be used in
Assign or Branching block expressions.
Composer's database Query Builder and Stored Procedure Helper now support table synonyms.
A new Composer Route Project template is available: Forward to External Resource.
New Integrated Voice and Route Project templates are available: Load Balancing and Working Hour Routing, External File-Based Routing, and Play Application and Busy Treatment.
The Transfer block provides a property for setting an authorization code (authcode).
The Call Trace view used for debugging a callflow displays the line number for each incoming metric.
A "barge-in" option is available for prompts. The Interruptible property for the following blocks add a new option for DTMF-only barge-in mode: Prompt block, DB Prompt block, Input block, Menu block, Grammar Menu block, and DB Input block.
Automatic selection of language-specific pre-recorded prompts, grammars, and TTS prompts is now available during application execution. The following blocks add a new Language property: Prompt block, DB Prompt block, Input block, Menu block, Grammar Menu block, DB Input block, and Record block.
The Language property affects the language of grammars used for ASR input for the following blocks: Input block, Transfer block, and Route Request block.
The Record block's Capture Filename Prefix and Capture Location properties now allow selection from application variables in addition to accepting literal strings.
SSML tags can now be used in prompts.
You can now use the GVP ICM Adapter in VoiceXML applications, including invoking services, responding to requests, and sharing data. A new ICM Interaction Data block, available on the CTI Blocks palette, supports sending of variables to ICM. A new ICM Route Request block, also available on the CTI Blocks palette, supports routing the call to CTI.
Voice Projects now have a Enable ICM Project-level flag, which controls whether ICM variables are available for selection and assignment to variables within Composer's Entry block.
The Exit block's Return Values property dialog allows you to select the ICM variables to be returned.
This release includes the following security-related enhancements:
The Web Service block now supports certificate-based authentication. You can develop both voice (VXML) and routing (SCXML) applications that support secure mutual authentication and communication with a Web Service. Composer supports the use of both a digital client certificate and server certificate contained in a keystore file.
When creating a routing application and connecting to Configuration Server, Composer displays informational text associated with both successful and unsuccessful authentication.
You can configure an inactivity timeout for the connection to Configuration Server as well as when the timeout warning dialog should appear.
You have the option of having a configurable security banner appear when Composer is first launched, similar to other Genesys applications. For information on configurable items related to the banner, see the Genesys 8.1 Security Deployment Guide.
Composer supports secure connections when connecting to GVP's Media Control Platform and when connecting to Context Services for Universal Contact Server.
Composer now has Transport Layer Security (TLS) support and adheres to Federal Information Processing Standards (FIPS) in its connection to Configuration Server and to GVP's Media Control Platform.
When organizing custom blocks, you can also select from a set of bundled custom icons for the custom blocks that you create.
Expression Builder is enhanced as follows:
It now returns to its last state when re-opened, which includes displaying the tree and the location in the tree in the Expression Builder Data area.
The filter now works on the description of the functions in addition to the function signatures.
Data loading is optimized to run in a separate thread. As a result, dialogs remain responsive while data loading is in progress.
New operating system support for 8.1 is as follows:
Composer can run on the Windows 2003, Windows 2008 (32-bit and 64 bit in 32-bit compatibility mode), Windows XP, Windows Vista, and Windows 7 (32-bit and 64-bit in 32-bit compatibility mode) operating systems.
This release includes the following corrections and modifications that were made between Release 8.0 and the 8.1 release.
The Prompts Manager does not support the Undo operation. But unlike previous versions, it no longer generates an error if the user tries to undo a change. (ER# 213873640)
The Database Connection Profiles editor no longer shows errors for correctly specified profiles if one or more profiles contain errors. Previously, if the editor was closed while errors still existed, these errors were not shown when the editor was re-opened. (ER# 262234521)
Deleting Connection Profiles from the Connection Profile editor no longer creates validation errors. (ER# 262234523)
Installation of third party Eclipse plugins no longer fails on Windows 2008.
Previously, the following error was displayed: Cannot complete the install
because one or more required items could not be found
. (ER# 262259091)
The DB Data block now supports accessing stored procedures using synonyms (as well as synonyms for tables). (ER# 258082401)
Prompt functionality for callflows no longer supports specifying only one noinput or nomatch prompt for each retry prompt. Multiple prompts can now be specified. (ER# 255440957)
In a Create E-mail or Create SMS block, if a queue is specified for the new interaction, the workflow linked to the specified interaction queue is now invoked. (ER# 245051967)
The existing or current interaction is no longer stopped in a Route Interaction block. Any workflow connected to the queue specified for the existing interaction is now invoked. (ER# 245143425)
The Route Interaction block is no longer limited to handling one new interaction from a target; for example, a reply e-mail from an agent. The generated application no longer indefinitely waits for the new interaction. (ER# 245143421)
When non-alphanumeric characters are used to create a Connection Profile for a DB Data block, a runtime VXML/SCXML exception no longer occurs when running the application. (ER# 230710381)
The Log block's Condition property now lets you select from a list of variables. You no longer need to 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)
Could not locate resource root: /MyComposerProject/debugging-results
.(ER# 218696694)
A .Net Voice Project is automatically deployed to IIS when it is created. Now, after renaming the Project, it is re-deployed to IIS. (ER# 215231108)
This section provides the latest information on known issues and recommendations
associated with this product.
Found In: 8.1.561.24 | Fixed In: |
Found In: 8.1.550.08 | Fixed In: 8.1.561.19 |
Found In: 8.1.561.17 | Fixed In: |
getWebRequest
error is logged in the composer.log file even though a connection is established and a response is recieved. (Composer-16357)
Found In: 8.1.550.08 | Fixed In: |
Found In: 8.1.560.13 | Fixed In: |
For a workaround, refer to the to the Tomcat Service - File Permissions Issue topic in Composer 8.1.5 Help.
Found In: 8.1.560.07 | Fixed In: |
Found In: 8.1.510.01 | Fixed In: |
Found In: 8.1.451.02 | Fixed In: |
Found In: 8.1.450.30 | Fixed In: 8.1.450.33 |
Found In: 8.1.450.33 | Fixed In: |
Found In: 8.1.450.33 | Fixed In: 8.1.451.08 |
script
keyword in the Application
option of the Orchestration
section in the routing point DN when deploying scripts using Strategy Manager in the French Canadian localized Composer workspace, which results in an error when trying to run the strategy. To avoid this, the extra space must be removed manually. (Composer-15833).
Found In: 8.1.450.32 | Fixed In: 8.1.451.01 |
Found In: 8.1.450.32 | Fixed In: |
Found In: 8.1.450.31 | Fixed In: |
Found In: 8.1.440.18 | Fixed In: 8.1.450.16 |
Found In: 8.1.440.18 | Fixed In: |
The Transfer block throws a semantic error in runtime when the Variables property is set as Key=Literal and Value=Variable. (COMPOSER-14219)
Found In: 8.1.430.03 | Fixed In: 8.1.440.18 |
Found In: 8.1.410.14 | Fixed In: |
The Web Services block throws a syntax error when the Map Output Values To Variables property set to true and the Output Result expression contains a namespace prefix. Workaround:
Found In: 8.1.410.14 | Fixed In: |
Validation throws a Java "bad class" error on a Capture.jsp file when Composer installed on top of Java 8. This problem will not be fixed as it is related to third party software. The Record block will work as expected even though the "bad class" error appears. The error can be ignored or it can be deleted from the Problems view in order avoid a mix-up with actual errors . The following steps can be followed to delete the "bad class" error:
Found In: 8.1.410.14 | Fixed In: |
The Orchestration Options dialog allows you specify the detach method as described in Release 8.1.400.35. For the new Projects created in 8.1.400.35, the default value for Interaction Detach in Orchestration Options is Use Application, instead of Use Platform. Workaround: After creating a new Project, manually update the value of Interaction Detach as Use Platform in Orchestration Options. (COMPOSER-5436)
Found In: 8.1.400.35 | Fixed In: 8.1.410.14 |
Workbin details are updated instead of queue in PrivateView and CustomView objects. Workaround: After publishing an interaction process diagram with a Workbin block, update the following objects in the Scripts folder in Configuration Server:
This update must be done before mapping the Workbin to Workspace Desktop Edition (formerly Interaction Workspace). (COMPOSER-5379)
Found In: 8.1.400.33 | Fixed In: 8.1.400.35 |
When a Project is deleted in Composer, its published objects are not removed as part of this operation. Also an error message asking whether to delete the published objects manually is displayed. Workaround: Delete the objects manually. Another workaround is to delete the interaction process diagram (IPD) files first, let Composer delete objects when it prompts to, and then delete the entire Project after that. (COMPOSER-5230)
Found In: 8.1.400.17 | Fixed In: 8.1.400.17 |
If a variable is not assigned to hold the output of a Web Request block, this may lead to an error at runtime as the assignment is invalid. Workaround: Select a variable to hold the output result. (COMPOSER-4971)
Found In: 8.1.400.17 | Fixed In: 8.1.400.22 |
Double quotes in Input strings for the Prompts property of the Play Message block are not Escaped correctly. Workaround: Use " instead of " (double-quotes) around string values. (COMPOSER-4980)
Found In: 8.1.400.17 | Fixed In: |
Post Action code defined in an interaction process diagram Branching block, Condition property, does not take effect. Workaround is to connect an ECMAScript block to the Branching block outport for this condition and write the Post Action code in that ECMAScript block. Alternatively, if possible, move the logic into a workflow diagram and do the segmentation there. (COMPOSER-5226)
Found In: 8.1.400.17 | Fixed In: 8.1.400.18 |
Resetting interaction process diagram (IPD) Publish information removes the selection of existing queues in Interaction Queue blocks. This results in creation of a new queue when the IPD is published again. Workaround: After re-setting the IPD information, re-select the existing queue in the Interaction Queue block(s) and then Publish the IPD. (COMPOSER-5085)
Found In: 8.1.400.17 | Fixed In: 8.1.400.21 |
In certain situations on low-powered machines, Composer development hangs if it is minimized by pressing the Windows key + D while a code generation process is active. A workaround is to not minimize Composer during code generation step. In Composer 8.1.3, the Generate All option was added, which avoids this issue altogether. (COMPOSER-1175)
Found In: 8.1.400.17 | Fixed In: |
The Debugger with Transport Layer Security does not work in 64-bit Windows. Workaround: Debugging is used in a development environment and therefore not using TLS is an option. If TLS use is required, install Composer on a 32-bit operating system. This can be fixed by upgrading to the latest version of JDK 1.7 (COMPOSER-3358)
Found In: 8.1.400.17 | Fixed In: |
After pressing F1 on a block property and clicking the topic link in the Composer Help pane, the Welcome page of the Composer 8.1.4 Help appears instead of the topic page. As a temporary workaround, use the TOC on the right and navigate to the topic. (COMPOSER-4767)
Found In: 8.1.400.17 | Fixed In: |
The condition expression for event-related properties in interaction process (IPD) and workflow diagrams are not XML-escaped when generating the SCXML code. For more information, For more information, see ORS Compile Errors and Non-Escaped Special Characters. (COMPOSER-5185)
Found In: 8.1.300.80 | Fixed In: 8.1.400.22 |
VOX files included in Composer 8.1.3 sound muffled or garbled when played on GVP. This is due to incorrect file encoding. Workaround: If the 8.1.2 or an earlier version of Composer is available, copy the prompt files from there into the 8.1.3 Project. (COMPOSER-5054)
Found In: 8.1.300.80 | Fixed In: 8.1.300.92 |
The order of included PromptSwitch.js and language file xx-XX.js is not correct in the Prompt block. This causes runtime errors in playing prompts if Languagee is specified in the Prompt block. (COMPOSER-5055)
Found In: 8.1.300.61 | Fixed In: 8.1.300.92 |
The Composer toolbar Start Tomcat and Stop Tomcat buttons do not function on Mac OS X. To start and stop Tomcat, please use Tomcat's native command-line utilities. Note:Support for Mac OS X is removed from release 8.1.300.33. (COMPOSER-4782)
Found In: 8.1.300.51 | Fixed In: |
Composer adds a namespace entry (interaction process diagram Namespaces and workflow diagram/Namespaces properties) when upgrading Projects to 8.1.2. If that namespace was already added by the user, it will then be duplicated. The workaround is to edit the Namespaces property and to remove the duplicated namespace entry. (COMPOSER-4778)
Found In: 8.1.300.51 | Fixed In: 8.1.300 |
When creating an ICM-enabled Composer Project, the ICM Variables are missing from the Main.callflow Entry block. To create the ICM variables, open the Project properties (right-click on the Project and select Properties), and disable ICM Support. Click OK. Then, open the Project properties page again and enable ICM Support. (COMPOSER-4722)
Found In: 8.1.300.51 | Fixed In: 8.1.400.17 |
The WAR file export wizard is changed to show more accurate error messages if it encounters errors during export. Previously, it displayed generic error messages. (COMPOSER-4681)
Found In: 8.1.300.51 | Fixed In: 8.1.300 |
For some blocks (for example, Wait for Event), the banner title of the Properties view does not match the name of the block. Workaround: None required. This is only a cosmetic issue and has no impact on functionality. (COMPOSER-4710)
Found In: 8.1.300.51 | Fixed In: 8.1.400.11 |
While upgrading older Projects in Composer 8.1.3, there may be cases where an upgraded diagram displays a validation error marker complaining about not being able to open a referenced diagram. This usually happens if the referenced diagrams has not already been upgraded. Workaround: Upgrade the referenced diagram by right-clicking it in the Project Explorer and selecting the upgrade option. (COMPOSER-4719)
Found In: 8.1.300.51 | Fixed In: 8.1.400.17 |
While installing Composer 8.1.3, there is a step to download dependencies from Eclipse update sites. If the internet connection is lost during this process, or some other error occurs, the Installer does not detect it and incorrectly reports success. Error messages will appear in the scripts\composer-plugin-install.log file in the Composer installation directory, (for example, C:\Program Files\GCTI\Composer\scripts\composer-plugin-install.log). Workaround: Instead of letting the Installer add Composer plugins directly to Eclipse, add Composer plugins using Eclipse's "Install New Software" feature. (COMPOSER-4692)
Found In: 8.1.300.51 | Fixed In: |
The Query Builder and Stored Procedure Helper doe not display the database schema when connecting to a SQL Server instance that required Secure Sockets Layer (SSL). This is due to a known incompatibility in SQL Server with the Java 7 SSL implementation (http://support.microsoft.com/kb/2653857). Workaround: Run Composer with Java system property jsse.enableCBCProtection=false. Set the property by adding it to the eclipse.ini file, in the vmargs section:
Note that CBCProtection is a security patch, introduced in Java 6u29, that protects against the BEAST attack (http://en.wikipedia.org/wiki/Transport_Layer_Security#BEAST_attack). Disabling CBCProtection would leave it vulnerable to the BEAST attack. This issue will be addressed by Microsoft. (COMPOSER-4353)
Found In: 8.1.300.33 | Fixed In: |
When using the DB Data block to retrieve data from a SQL database and database errors occur (such as failure to connect to a database), under some circumstances, this results in an invalid JSON message being returned to the workflow/callflow application. In turn, this could cause the application to fail on requests to other data sources and affect interaction distribution. (COMPOSER-5254)
Found In: 8.1.300.33 | Fixed In: 8.1.301.02 |
The Preferences dialog box stretches across the screen on Mac OS due to label text being too long. This is a display issue only. Workaround: None required. Support for Mac OS X is removed from Release 8.1.300.33. It is now available as a restricted release with a separate installation package. Contact your Genesys representative to request it.(COMPOSER-4675)
Found In: 8.1.300.33 | Fixed In: |
The Web Services block Parameters dialog box does not validate if a value is specified for each output parameter. Missing values can lead to syntax error at runtime. Workaround: Select values for output parameters in the dialog. (COMPOSER-4669)
Found In: 8.1.300.33 | Fixed In: 8.1.400.17 |
The default color of gridlines on Mac OS is subtle, which makes the gridlines almost invisible unless a high contrast display scheme is used. Workaround: None. Support for Mac OS X is removed from Release 8.1.300.33. (COMPOSER-4668)
Found In: 8.1.300.33 | Fixed In: |
The Project Upgrade dialog box does not show a progress bar as it upgrades a project. This is a display issue only. Workaround: None required. Once a Project is upgraded, a completion message is shown. (COMPOSER-4667)
Found In: 8.1.300.33 | Fixed In: 8.1.400.11 |
Checkboxes appear left-aligned in tree structures in UIs like query builder instead of appearing next to child nodes in the tree. This is a display issue only. Workaround: None required. (COMPOSER-4596)
Found In: 8.1.300.33 | Fixed In: |
Logging expressions specified in Expression Builder are not displayed in the parent dialog unless focus moves away from the Logging Detail list, e.g., when OK is clicked. This is a display issue only. Workaround: Click elsewhere in the dialog or the OK button to display updated value. (COMPOSER-4574)
Found In: 8.1.300.33 | Fixed In: 8.1.400.17 |
The Menu block does not validate if the correct number of retry prompts are specified according to the number of retries set in the block. The property dialog validates this only after OK is clicked. Workaround: Click OK in the dialog to trigger validation or specify correct number of retry prompts. (COMPOSER-4535)
Found In: 8.1.300.33 | Fixed In: 8.1.400.12 |
The Menu block Repeat Menu Option gives the impression that multiple values can be specified by showing Add/Remove buttons. In this scenario, the UI behaves correctly and does not allow adding more than one entry. Workaround: None required. (COMPOSER-4531)
Found In: 8.1.300.33 | Fixed In: |
While importing custom blocks, corresponding block icons are not displayed. Correct icons are displayed in the palette after the import process finishes. This is a display issue only. Workaround: None required. (COMPOSER-4528)
Found In: 8.1.300.33 | Fixed In: |
In some workflow blocks, renamed output links are not retained. For example, this can occur in the SCXML State block if the link name or transition name is cleared first and a new name is specified. The dialog interprets this action as a new link. This is not an issue if the link name or transition name is changed to a new value without clearing it first. Workaround: Draw the output link again after renaming it. (COMPOSER-4510)
Found In: 8.1.300.33 | Fixed In: |
If a capture location is not specified in the Record block, recorded files are saved to the Windows system directory by default instead of the application server directory. Workaround: Specify the capture location. (COMPOSER-4462)
Found In: 8.1.300.33 | Fixed In: |
Some Preference page labels are not externalized and cannot be localized. Workaround: None required. This impacts only label XML Catalog and this preference is not usually modified. (COMPOSER-4382)
Found In: 8.1.300.33 | Fixed In: 8.1.410 |
The display for inferred or linked blocks continues to point to the previously specified queue in the interaction process diagram if a different queue is selected in the Output Queue property of an Email block. This is a display issue only. Workaround: Reset the Resource property of Workflow block in the IPD and set it again. This will show the updated linked block. (COMPOSESR-4300)
Found In: 8.1.300.33 | Fixed In: |
In certain situations on low-powered machines, the Composer development hangs if it is minimized by pressing the Windows key + D while a code generation process is active. Workaround: Do not minimize Composer during code generation step. (COMPOSER-1175)
Found In: 8.1.300.33 | Fixed In: |
In certain situations, Composer logs an exception when a new WSDL URL is specified in the WebService block. Workaround: None required; there is no impact to functionality. (ER# 316271385, COMPOSER-4251)
Found In: 8.1.201.52 | Fixed In: 8.1.300.33 |
This issue will not be fixed. The Composer Help, Common Properties for Callflow Blocks, Set Prompt Properties dialog box, contains details about ECMAScript data values and single quotes. (COMPOSER-713)
Found In: 8.0.001.87 | Fixed In: 8.1.300.33 |
If an IPD contains a Workflow block, the IPD is automatically synced with the contents of the referenced Workflow diagram. If an IPD appears to be out of sync, close it and reopen it, to force it to synchronize with the Workflow diagram. (ER# 315837796)
Found In: 8.1.201.52 | Fixed In: |
The checkboxes and text fields for encryption settings in the Database Connections Editor may become enabled incorrectly if the editor switches between multiple profiles. Workaround: None required. This is a display issue only, and does not affect specifying correct values for connection properties. (ER# 315824841, COMPOSER-4238)
Found In: 8.1.201.52 | Fixed In: 8.1.300.33 |
You cannot cancel the operation while testing a database connection using the Connection Profile editor. You must wait for the operation to complete. (ER# 315498283)
Found In: 8.1.201.52 | Fixed In: |
The Web Service Input Parameters dialog currently does not allow parameters to have the same name. (ER# 314822329)
Found In: 8.1.201.52 | Fixed In: |
You should not be able to edit the Name field in the Webservice Output property. Do not edit this field. (ER# 313788571)
Found In: 8.1.201.52 | Fixed In: |
If Media Control Platform (MCP) is running on a virtual machine (VM) and Composer is running on the physical machine that is hosting the VM, then you may have trouble running a GVP debugging session. Workaround: Run Composer on a separate machine, or on the same VM that is running MCP. (ER# 309375139)
Found In: 8.1.200.52 | Fixed In: |
The Target selection dialog of the Target block may throw an Invalid
Agent
message while attempting to select a StatServer. This occurs if
there are approximately 100 (or more) StatServers defined in the environment.
Workaround: Disconnect from Configuration Server and enter the name of the StatServer,
instead of picking it from a list. (ER# 312618644)
Found In: 8.1.102.00 | Fixed In: |
When the diagram grid and rulers are set to be visible in the preferences, newly created callflow and workflow diagrams will sometimes not initially display grid and rulers. Workaround: For each affected diagram, go to the Rulers & Grid tab of the diagram properties and enable the grid and rulers checkboxes. (ER# 306242562, COMPOSER-4003)
Found In: 8.1.102.00 | Fixed In: 8.1.300.33 |
The dialog for customizing perspectives incorrectly displays toolbar button separators as blank entries with no text or description. This is a bug in the version of Eclipse being shipped with Composer. Workaround: None required. There is no impact to functionality. (ER# 306242508, COMPOSER-4001)
Found In: 8.1.102.00 | Fixed In: 8.1.300.33 |
A few blocks (such as Assign, Disconnect, and WebServices) show a root. prefix for selected variables if the variables are present in a root document. This affects only the display of properties and has no impact on functionality. Workaround: none required. (ER# 296275472)
Found In: 8.1.101.88 | Fixed In: |
Adding an extension to a file name that previously did not have an extension displays an error. Workaround: Dismiss the error dialog. The file is renamed correctly. (ER# 301882373)
Found In: 8.1.101.88 | Fixed In: 8.1.201.52 |
An interaction process diagram that references a workflow routing an interaction to a Workbin, does not show a linked block for the Workbin. Workaround: None available. There is no impact to routing functionality. (ER# 302446063, COMPOSER-3951)
Found In: 8.1.101.88 | Fixed In: 8.1.300.33 |
The color of the Stop Interaction block is not consistent with other terminating blocks. Workaround: None required. This is only a display issue. (ER# 297461273)
Found In: 8.1.101.88 | Fixed In: 8.1.201.52 |
If a Queue Interaction block is updated with a new queue, this change is not reflected in linked blocks in the interaction process diagram. Workaround: None available. This is only a display issue. (ER# 297853293)
Found In: 8.1.101.88 | Fixed In: 8.1.201.52 |
If the queue in a Send Email block is updated, this change is not reflected in the interaction process diagram. Workaround: None required. This is only a display issue. (ER# 302045214)
Found In: 8.1.101.88 | Fixed In: 8.1.201.52 |
Variable mapping does not work in the Identify Contact block. Workaround: Assign the output of the block to a variable and then use an Assign block for equivalent variable mapping. (ER# 302251369)
Found In: 8.1.101.88 | Fixed In: 8.1.201.52 |
When the Output Result property for certain blocks (Chat Transcript, Create Email, Create SMS, Email Forward, and Email Response) is set to User Data, Orchestration Server will not transition out of the block. As a workaround, Genesys recommends assigning a variable to the Output Result property and then using the User Data block to update the interaction user data with the value of this variable. (ER# 302549675)
Found In: 8.1.101.88 | Fixed In: 8.1.201.52 |
If a Workbin object is deleted from an interaction process diagram, its associated objects in Configuration Server are not removed. Workaround: Use Genesys Administrator to manually delete the Interaction Workbin object and its view. (ER# 302446061)
Found In: 8.1.101.88 | Fixed In: 8.1.201.52 |
While debugging an interaction process diagram SCXML file, debugging skips over lines that include the workflow SCXML file using the <xi:include> tag. Workaround: None required. Debugging will step into the included workflow diagram or SCXML file. (ER# 297654802)
Found In: 8.1.101.88 | Fixed In: |
The Troubleshooting Overview in the Composer Help does not include a link to the Checkin Error Source Control topic. The Intergrating with Source Control Systems does link to the topic. (ER# 302896571)
Found In: 8.1.101.88 | Fixed In: 8.1.201.52 |
The 8.1.010.47 Hot fix includes an updated getWebRequestData.jsp page in the /include folder for Java Composer Projects. You must manually update any existing Projects created in Composer 8.1.010 with this new page if the Projects are affected by the issue described in ER# 308306201. Any Projects created in Composer 8.1 and earlier will automatically receive the updated page when the Project is upgraded in a later release of Composer. To update a Project:
You must update any DotNet Composer Projects that use non-English characters in custom ASPX pages with a new web.config file in the Project root folder. This file sets UTF8 encoding using the <globalization> element. To update an existing Project, create a new DotNet Composer Project and copy the <globalization> element settings from the new Project web.config file to the existing Project. When the Project is upgraded to the current release, any Projects created in Composer 8.1 and earlier will automatically receive the updated web.config file. (ER# 308306201)
Found In: 8.1.010.43 | Fixed In: 8.1.010.47 |
The preference page under Preferences > Composer
> Debugging may display the following error message:
Composer could not find a valid network interface.
If this happens,
check your network settings in Windows to ensure that network interfaces are
present. Restart Windows and Composer and retry. (ER# 297472721)
Found In: 8.1.003.55 | Fixed In: |
Composer sometimes incorrectly displays that it is connected to Configuration Server after a previously enabled network interface is manually enabled. This scenario can occur when the host wakes up after hibernation. Workaround: Restart Composer. (ER# 295556361)
Found In: 8.1.003.55 | Fixed In: |
The test function in the Business Rule block incorrectly interprets numeric literals as variables and prompts the user to provide a test value for these variables. Workaround: Specify a value for the numeric property and execute the rule. The rule will execute correctly. There is no impact on the application at runtime. (ER# 284482622)
Found In: 8.1.003.55 | Fixed In: 8.1.201.52 |
While working with Context Services, if the connection to Context Services is idle for some time, a dialog conveying a timeout error may be displayed. Workaround: This dialog can be dismissed and will not impact Context Services operations. If Context Services blocks are not being used, the Connect to Universal Contact Server when designing diagrams preference can be switched off to avoid this timeout. There is no impact on the application at runtime. (ER# 284482624)
Found In: 8.1.003.55 | Fixed In: 8.1.101.88 |
.NET Composer Projects may show a warning in the Console View:
include\getWebServiceData.aspx(482): warning CS0618: 'Microsoft.Web.Services3.SoapContext.Security'
is obsolete: 'SoapContext.Security is obsolete. Consider deriving from SendSecurityFilter
or ReceiveSecurityFilter and creating a custom policy assertion that generates
these filters.'
This warning can be ignored and no workarounds are needed. It will not show up as an error or warning in the Problems View. (ER# 277966454)
Found In: 8.1.002.32 | Fixed In: 8.1.201.52 |
The Debugger with Transport Layer Security does not work in 64-bit Windows. Workaround: Debugging is used in a development environment and therefore not using TLS is an option. If TLS use is required, install Composer on a 32-bit OS. (ER# 276671871, COMPOSER-3358)
Found In: 8.1.003.55 | Fixed In: 8.1.300.33 |
The Business Rule block does not correctly display Datatypes. Workaround: None required. Correct data types can be checked in Genesys Rules Development Tool. (ER# 284095003)
Found In: 8.1.003.55 | Fixed In: 8.1.201.52 |
An HTTPS Connection to Context Services during the design stage fails on Windows 7 (64-bit). Workaround: Composer is used in a development environment and therefore not using TLS is an option. If TLS use is required, install Composer on a 32-bit OS. (ER# 283883750)
Found In: 8.1.003.55 | Fixed In: 8.1.300.33 |
Unpublished queues are not available for selection in the Output Queue property of the Create E-mail block. Workaround: Publish the IPD if connected to Configuration Server. If not, specify the queue name as a literal. (ER# 269763181)
Found In: 8.1.003.55 | Fixed In: 8.1.300.33 |
The Backend block parameter dialog allows you to enter a literal. Workaround: Specify variables for parameter values. (ER# 276267465)
Found In: 8.1.003.55 | Fixed In: 8.1.101.88 |
In the Queue selection dialog of the Route Interaction block, there is no validation for missing variables or non-existing Configuration Database objects. Workaround: Manually check that the specified variables and/or Interaction Queue objects exist. (ER# 283684833)
Found In: 8.1.003.55 | Fixed In: |
The help for the Announcement ID property in the Create User Announcement block states to select a variable but literal values are also supported. Workaround: None required. (ER# 283915760)
Found In: 8.1.003.55 | Fixed In: 8.1.300.33 |
The Route Interaction block's Targets property dialog includes a field for Threshold, which is not necessary for this block and should not be used. Workaround: None required. (ER# 276862719)
Found In: 8.1.003.55 | Fixed In: 8.1.201.52 |
Composer displays a warning message when exporting a Java Composer Project as .WAR file. This warning comes while trying to find the lib folder in the base directory. It is not blocking any user operations. Workaround: None required. (ER# 281934142)
Found In: 8.1.003.55 | Fixed In: 8.1.300.33 |
When creating GXML files, the follow error dialog appears: A resource
exists with a difference case.
This dialog can be dismissed as it does
not impact functionality. Workaround: None required. (ER# 283282491)
Found In: 8.1.003.55 | Fixed In: |
The F1 help shortcut doesn't work in some E-mail blocks. Workaround: Launch help from Help Menu and search for the relevant email block name. (ER# 283515625)
Found In: 8.1.003.55 | Fixed In: 8.1.201.52 |
The Upgrade report shows "Success" when diagram upgrade fails. Workaround: Check diagram upgrade status in the report. If it fails, it will be highlighted in the report. (ER# 284081684)
Found In: 8.1.003.55 | Fixed In: 8.1.201.52 |
Composer allows making changes to diagrams even when they are not explicitly checked out from the source code control system and may be read-only but changes do not get saved. Workaround: Do an explicit check out of the diagram before making changes. (ER# 270944059)
Found In: 8.1.003.55 | Fixed In: |
When renaming Facts in the Business Rules Facts dialog box, the list on the left side of the dialog box does not refresh with the new names. However, the new names will be saved if you press OK. (ER# 278618973)
Found In: 8.1.003.55 | Fixed In: |
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)
Found In: 8.0.401.84 | Fixed In: 8.1.201.52 |
The Log block for Callflows does not show a validation error if logging details are not specified. Workaround: Specify logging details. (ER# 253689341)
Found In: 8.0.401.84 | Fixed In: 8.1.300.33 |
The 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 use the Access Diagram Variables
button
on the toolbar. (ER# 258598836)
Found In: 8.0.401.84 | Fixed In: |
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)
Found In: 8.0.401.84 | Fixed In: 8.1.300.33 |
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)
Found In: 8.0.401.84 | Fixed In: |
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)
Found In: 8.0.401.84 | Fixed In: 8.1.201.52 |
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)
Found In: 8.0.401.84 | Fixed In: 8.1.201.52 |
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)
Found In: 8.0.401.84 | Fixed In: 8.1.300.33 |
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)
Found In: 8.0.301.81 | Fixed In: 8.1.101.88 |
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)
Found In: 8.0.301.81 | Fixed In: 8.1.201.52 |
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 the Media_Type in Universal Contact Server. (ER# 248203442)
Found In: 8.0.301.81 | Fixed In: 8.1.101.88 |
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)
Found In: 8.0.301.81 | Fixed In: 8.1.201.52 |
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)
Found In: 8.0.210.60 | Fixed In: 8.1.300.33 |
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)
Found In: 8.0.202.59 | Fixed In: 8.1.201.52 |
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)
Found In: 8.0.101.11 | Fixed In: |
Composer does not properly populate several diagram date fields: Created
on
and Last Modified on
. There is no workaround. (ER# 215931045)
Found In: 8.0.101.11 | Fixed In: |
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)
Found In: 8.0.001.87 | Fixed In: 8.1.300.33 |
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:
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
.
String()
constructor. For example, use String(myFunction())
where myFunction()
returns a number. (ER# 218099101)
Found In: 8.0.001.87 | Fixed In: |
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)
Found In: 8.0.001.87 | 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. For more information on discontinued support for operating environments and databases, see "Discontinued Support" in the Genesys Supported Operating Environment Reference Guide.
Eclipse versions Luna 4.4 and Mars 4.5 are no longer supported.
Discontinued As Of: September 04, 2020; 8.1.560.15 |
Eclipse versions Juno and Kepler are no longer supported.
Discontinued As Of: 8.1.530.17 |
The RouteDone function is no longer supported.
Discontinued As Of: 8.1.003.55 |
Information in this section is included for international customers.
Support for the French Canadian language is available in releases 8.1.430.06 and 8.1.450.33. It is not included in subsequent releases unless specifically noted.
Additional information on Genesys Cloud Services is available on our Genesys Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.
The Composer 8.1.4 Deployment Guide describes how to deploy Composer, an Integrated Development Environment used to develop applications for Genesys Voice Platform and the Genesys Orchestration Server Platform.
Selecting the Composer 8.1.4 Help (accessible inside Composer's Eclipse Help System) directs users to Composer 8.1.4 Help, which is the Composer Help on the Genesys Documentation website.
The Composer 8.1 Routing Applications User's Guide, available on the Genesys Documentation website, introduces the Composer interface and the process of building routing applications, including creating interaction process diagrams and workflow diagrams.
The IRD to Composer Migration Guide, available on the Genesys Documentation website, shows how to migrate IRD routing strategies into Composer Projects as SCXML-based workflow diagrams.
Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.
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.