New in Release 8.1.4

8.1.450.33 August 2018 Release

Starting with this release, Composer's DB Data blocks support Microsoft SQL Server 2017 in both Callflows and Workflows.
This release supports French Canadian localization.
Composer now supports fetching HTTPS URLs in the Web Request and Web Service blocks.
A new view, Strategy Manager, is added to the Composer Workbench to list all routing points from the connected Configuration Server.
A new feature to refactor variables across blocks in a diagram file is introduced.
A new wizard, Composer Bulk Manager, is introduced to manage bulk deployment of projects.

8.1.450.20 April 2018 Release

The Tomcat version bundled with the Composer installation package is upgraded from 7.0.69 to 8.5.27.
Starting with this release, Composer backend server side-pages are analyzed for security and performance issues using CheckMark Scan, a security analysis software.
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.
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.

8.1.450.08 December 2017 Release

A new block, HTTP Rest, is added to the Server Side category for both workflow and callflow diagrams. Prior to this release, it was not possible to send a JSON or REST request to the backend without intermediate JSP or ASPX processing. The new HTTP Rest block is used for both routing and voice applications.

8.1.450.04 October 2017 Release

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.

8.1.440.18 May 2017 Release

Composer supplies a sample application to capture run-time metrics in a JSON format.
Composer adds the following blocks to the palette:
- The Update UCS Record block—Updates the properties of an interaction in the Universal Contact Server database. Can be used for both interactions currently in process and interactions already processed.
- The Update Interaction block—Updates the properties of interaction(s) in the Interaction Server database including interaction(s) that are not currently being processed in the workflow.
- The Set Agent State block—Dynamically manages agent resource states via ESP methods. Allows users to set agent Do Not Disturb (DND) state, set the Media state, or Force-logout the agents.
- The Find Interactions block—Retrieves a list of interactions matching some specific condition.
Composer now supports Context Services 8.5 based on Genesys Mobile Engagement (GMS) features.
The Server Side palette adds a URS Function block applicable to workflow diagrams, which can be used to call any Universal Routing Server (URS) function.
eService blocks that contain a Standard Response property now show Autoresponse, Acknowledgement, and Notification type standard responses as defined in eServices Knowledge Manager.
The Queue Interaction block, Interaction Queue property, supports selecting a queue dynamically through a variable.
The Route Interaction block Workbin property now supports selecting a Workbin dynamically through variable.
The Timeout property in the Target, Route Interaction, Update, Web Service, Web Request, Wait Event, and Response blocks are set to valid default timeout values.
The Web Service block, Password property, now allows you to select from a variable.
The Workflow block used for interaction process diagrams adds a Maximum Interactions Default Limit Property to specify the maximum number of interactions allowed for a strategy to process at any given time.
The Business Rule block, Rules Engine URL property, now allows you to specify a variable.
Composer adds support for sub-directories when updating/using following: Generate All, Project Locales, Command Line Code Generation, Command Line Upgrade, Command Line Publish, Java Project Export, ORS Debugger, Project Upgrade, SubModules handling auto-synchronization of parameters, New callflow/workflow file creation.
Composer provides support to optionally include dynamic prompts supporting JavaScript files in the generated VoiceXML. Users shall be able to enable or disable dynamic prompts through a Prompts Management property.
Composer Assign blocks now generate logging statements as part of code generation. With this enhancement, ORS and MCP logs will show the Assign variables and expressions.
Workflow diagram blocks Exceptions property now supports adding Conditions for the events.

8.1.430.06 May 2017 Release

Composer adds support for the French Canadian language.

8.1.430.14 September 2016 Release

Composer supplies an IVR Recording block that allows you to control and record an IVR application from a Composer IVR self-service application.
New properties Activity and Cut Off Time in the Target block allow you to specify a Workforce Management Activity for routing and a related Cut Off Time.

8.1.420.14 July 2016 Release

This release of Composer includes Tomcat 7 as part of the Composer installation package.
Support for the Orchestration Server <ixn:createmessage> tag associate attribute in the Create Email, Create SMS, Email Forward, and Email Response blocks. Controls whether a new interaction is associated with the session that created it.
The Route Interaction block, Queue for Existing Interaction and Queue for Outgoing Interaction properties, adds support for variables.
The User Data block adds a new property, Internal Key Prefix, which is used to verify whether the interaction.udata.changed event has been received in the case of a workflow using parallel User Data blocks.

8.1.420.14 July 2016 Release

This release of Composer includes Tomcat 7 as part of the Composer installation package.

Support for the Orchestration Server <ixn:createmessage> tag associate attribute in the Create Email, Create SMS, Email Forward, and Email Response blocks. Controls whether a new interaction is associated with the session that created it.

The Route Interaction block, Queue for Existing Interaction and Queue for Outgoing Interaction properties, adds support for variables.

The User Data block adds a new property, Internal Key Prefix, which is used to verify whether the interaction.udata.changed event has been received in the case of a workflow using parallel User Data blocks.

8.1.410.14 February 2016 Release

The following eServices blocks are no longer hidden on the palette: Identify Contact, Update Contact, Create Interaction, and Render Message.

The External Services block can now connect to a Social Messaging Server Application type.

An Analyze block is added for enhanced content analysis through Knowledge Manager.

A Select Ideal Agents block is added, which enables you to select the most ideal agent to handle an interaction when more than one agent is available.

An NDM block is added to add support for the Nuance Dialog Modules.

Composer can now be installed in an offline environment. Note: Customers still need to download and install Eclipse before hand to make this offline install work.

A new "skip targets" feature can improve the efficiency of finding an agent by enhancing or relaxing the target criteria without waiting until the routing timeout is reached in the Target block.

The Play Sound block adds a property to specify the number of times an audio file is to be played.

Composer Projects now have a default root VXML file (ComposerRoot.vxml) bundled inside the src folder. This file, used for Project-level defaults, is present in newly-created Projects and upgraded Projects.

Composer implements the userID attribute in the following blocks: Play Message, User Input, and Create User Announcement. The Prompts dialog adds a new userID column.

Composer now validates the Project version during Generate All and Project Upgrade processes.

The following blocks now allow you to choose a queue referenced in another Project: Email Forward, Create SMS, Email Response, Queue Interaction, Create Email, and Chat Transcript.

Composer checks for any missing resource files during VXML code generation for the following blocks: Prompt, Menu, Input, Grammar Menu, and Record.

When processing eServices/child interactions, the Entry block interaction.deleted event handlers are updated with guard conditions. They now check for deletion of the current interaction and whether the interaction.deleted event is from an interaction deletion and not from a detach operation.

When upgrading from the command line, you now have the option to Publish.

Eclipse Kepler, Mars, and Luna environments are supported.

June 2015 Composer 8.1.4 CD Update

Composer supports interaction process diagram (IPD) file minor version upgrades, which improves the upgrade logic for getting the latest contents as compared to major version upgrades.

Interaction process diagrams improve the process of handling media-specific interactions by categorizing the system handlers, such as voice, multimedia, and so on.

The interaction process diagram upgrade process from 8.1.3 and 8.1.4 versions is improved to preserve custom changes to the event handlers.

Workbin block published objects, if the Workbin is configured with a Private Queue, now allow the custom view to pull the interactions and not the Private view.

The Composer command line Project upgrade now updates the common files and the Project version numbering to the IP version.

The new Project and upgraded Project IPD system event handlers support both consult call and ISCC transfer scenarios for voice.

The Menu block Repeat Menu option supports using the block-level language value while repeating the Menu options.

The Web Request block getWebRequestData.jsp now supports parsing JSON Array contents.

Composer-generated .WAR file MIME types are updated to support deployments to Weblogic application servers.

Composer supports pulling eServices interactions during an Interaction Server failover.

The Assign block allows inserting a new assignment between assignment

November 2014 initial 8.1.4 release

A new Workflow block property lets you specify the maximum number of interactions allowed for a strategy to process at any given time. Note: This block property is only relevant for interactions queued on Interaction Server and takes precedence over any settings configured in Interaction Server and on the Annex tab of the Interaction Queue.

Composer supports the new Orchestration Server/Interaction Server feature of enhanced pulling of multimedia interactions, which uses the strategy name and allows different priorities to be set for different types of interactions.

In an interaction process diagram, the connection between an interaction View and a routing workflow is represented by a Submitter, which supplies parameters that control how Interaction Server will submit interactions to Orchestration Server. This is applicable when using the Orchestration Server enhanced pulling mechanism described above and Use Interaction Submitters is set to true within Composer.

External events can optionally be used for triggering the transition of interactions out of blocks or states.

Composer adds support for automated deployment of application Project files to an application server. SCXML files, VXML files, JAR files and so on, can be deployed for both voice and e-services.

The Entry block improves the process of working with application variables by categorizing them into groups.

The Target block adds a configurable option that allows you to play back the estimated waiting time to callers and define the repeat interval.

When using the Target or Route Interaction block to route based on the value of a statistic, you can specify a Stat Server as a variable.

When using the Target or Route Interaction block, you can select Transaction List objects as targets or specify them by name if not connected to Configuration Server. The Web Service block allows the Service End Point property to be specified as a variable. Proxy settings are supported. You can directly specify SOAP messages to better translate SOAP definitions.

The User Data block allows you to specify the maximum time to wait for attached User Data to change. When the timeout is exceeded, processing continues on with the next block.

The Sub-dialog block provides fetchaudio and fetchtimeout options for the maximum time to wait for audio to be played.

The Menu block allows you to automatically define variables to hold an output result.

Composer blocks used to build routing applications (with the exception of the Disconnect and EndParallel blocks) add a new Orchestration Server Extensions property (Show Advanced Properties button). This property gives the ability to use any attribute Orchestration Server supports in addition to the SCXML standard.

When using the Web Service block, you can specify a proxy server to act as an intermediary server when making requests for Web Services from other servers.

The existence of Resource Type prompts is now validated during code generation.

Validations are added to detect Infinite loops in workflows.

During login, you can choose whether or not to connect to Configuration Server.

Copyright

Complete information about Genesys proprietary intellectual property, including copyrights, can be found here.

Trademarks

Genesys and the Genesys logo are registered trademarks of Genesys Cloud Services, Inc. in the U.S.A. and other countries. Complete information about Genesys proprietary intellectual property, including all trademarks, can be found here.

All other trademarks are the property of their respective owners.

Third Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. Please contact your customer care representative if you have any questions. The following list describes specific third-party code and functionality for this product:

This product includes xxHash hash algorithm, developed by Yann Collet.
Copyright (C) 2012-2016, Yann Collet.
BSD 2-Clause License (http://www.opensource.org/licenses/bsd-license.php)

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

You can contact the author at : - xxHash source repository : https://github.com/Cyan4973/xxHash

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).

This product contains cryptographic software written by Eric Young, (mailto:eay@cryptsoft.com).

Part of the software embedded in this product is gSOAP software distributed under terms of the gSOAP Public License. Portions created by gSOAP are Copyright (C) 2001-2004 Robert A. van Engelen, Genivia inc. All Rights Reserved.

THE SOFTWARE IN THIS PRODUCT WAS IN PART PROVIDED BY GENIVIA INC AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This product includes software developed by the Apache Software Foundation (http://www.apache.org).

NOTICE OF RESTRICTED RIGHTS FOR ORACLE PRODUCTS LICENSED TO THE US GOVERNMENT Oracle Programs delivered to the United States government subject to the DOD FAR Supplement are 'commercial computer software' and use, duplication, and disclosure of the programs, including documentation,shall be subject to the licensing restrictions set forth in the applicable license agreement therefor. Otherwise, Oracle programs delivered subject to the Federal Acquisition Regulations are 'restricted computer software' and use, duplication, and disclosure of the programs, including documentation, shall be subject to the restrictions in FAR 52.227-19, Commercial Computer Software-Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

New in Release 9.0.0

8.1.400.81 - January 2019 Release (CD Version 9.0.000.01)

This release supports the CentOS Linux 7 operating system.
A new option is included to control if an arbitrary URL can be used as a value for the src parameter in a <session:start> action or an /scxml/session/start web request, when starting a new session.
ORS now supports TLS connections to the Message Server when parameters for the TLS connections are specified in the host object.
ORS now supports the Red Hat Kernel-based Virtual Machine (KVM).
ORS now supplies RequestorInfo data in all ESP requests that it generates.
ORS on Windows OS uses the Microsoft Visual Studio C++ 2013 Redistributable Package. The 2013 Redistributable Package is included in the ORS IP and is installed automatically.
A new configuration option, use-only-enabled-script, is introduced that controls whether or not ORS uses Enhanced Routing Script objects for session creation, based on object state.
In a blind transfer scenario to Route Point, ORS now generates an error.interaction.redirect event after it receives an EventError for the <ixn:redirect> action applied to a consultation call which is deleted due to transfer completion. A new configuration option, fin-acts-on-calldeleted, enables ORS to finalize all pending actions associated with a call upon receiving a CallDeleted event after the call is disconnected.
The fetch-timeout ORS option is exposed at the ORS Application object level as well.
The SCXML engine now properly caches DNS responses. The new ORS option, http-curl-dns-cache-timeout, defines the TTL value for entries in the internal DNS cache (in seconds).
The inqueues and outqueues properties of the hints attribute are supported in the <ixn:redirect> action for multimedia interactions, provided the destination type is a workbin.
ORS introduces a new SCXML extension, Agent, which can be used for implementing agent management features like logout, DND, and ability to change agent state for voice media.

8.1.400.73 - February/March 2018 Release (CD Version 9.0.000.00)

This release supports Cassandra internal authentication. New options, username and password, support this feature.
By default, ORS now attaches interaction properties to ESP requests. A new attach_ixn_data attribute for the <session:fetch> action of the esp method can be used to enable/disable attachment of interaction properties.
With this release, the ORS option, http-ssl-version, supports additional values TLSv1_0, TLSv1_1, and TLSv1_2.
ORS installation includes an Orchestration Plug-in to provide a real-time view of sessions currently being executed by ORS.
This release supports Cassandra 3.9.
Support for Windows Server 2016 64-bit native is added.
ORS enhances its Elasticsearch real-time reporting capabilities with the addition of the following new features.
- Explicit mapping of session and performance indexes
- A new Orchestration SCXML extension, elasticconnector
- Kibana Visualization samples
ORS now supports Elasticsearch releases 5.x, starting from 5.3.0.
With this release, ORS is enhanced to support a graceful shutdown.
Users can configure an ORS cluster using a dedicated Transaction object of type List. In addition, options for all ORS applications in a cluster may be configured within that object. This eliminates the need to individually configure the options in every ORS application.
ORS now provides the capability to define arbitrary headers for the HTTP requests generated by the SCXML engine to retrieve SCXML strategy documents. A new configuration section, scxml-doc-request-headers, is introduced to define additional headers.

application.secondary-audio-out-device Documentation:OS:Deployment:Avail:8.1.4

success

|Microsoft SQL Server]]

yes

Documentation:ICON:PDMDB2:GDict:8.1.5

GNINE Test Page

Documentation/GIM#85PDMs

MPandian
https://docs.genesys.com

Copy the installation binary file (*.tar.gz) to every server in the cluster. Make sure you follow recommendations about user and location as described in single-host installation.
Unpack the Installation Binary File On Every Server in the Cluster
To unpack, follow these steps:
1. Copy the IP_JOP_PRR_<version_number>_ENU_linux.tar.gz installation binary file to the desired installation directory. We recommend that you use the PM_USER home directory as the destination for JOP installation package.
2. From a command prompt, unpack the file using the following command to create the IP_JOP_PRR_<version_number>_ENU_linux directory:
```
tar -xvzf IP_JOP_PRR_<''version_number''>_ENU_linux.tar.gz
```
- Note the following points:
  - All scripts for installing and operating JOP in an HA setup can be found in the IP_JOP_PRR_<version_number>_ENU_linux/ha-scripts/ directory.
  - You must have configured the server host names for every server in the cluster (as detailed above, under "Hardware Requirements") before starting the installation procedure.

The user searches on Twitter or Facebook for the company’s handles and tweets or posts a message, which could be related to an issue being faced or a query targeted to customer care.

The application monitors the Twitter and Facebook handles through pre-defined events and filter messages based on keywords to determine the next action.

The application verifies if the corresponding contact already exists in the Contact History. The user is identified in the Contact History by their Facebook or Twitter handle (if available).
If the user does not exist (that is, social handles are not associated with a registered user), the application creates a user in the Universal Contact Database based on available data. Any further messages and agent replies are stored under this user.
The application then verifies if the day is a normal operational day. If not, a special day message is sent stating that the user’s query will be answered once the service is back online. The special day message is sent as a public message or a private message.
The application has the ability to determine if the operating hours of the service match the current time and day – if not, a standard message is sent in response stating that the query will be answered once the service is back online. This message is sent as a public message or a private message.
In addition, it is possible to define an emergency message that will be sent either as a public message or a private message, if the emergency process is activated.
If within operating hours on a regular day, the application searches for an available agent with the correct skills.

If an agent is available, the interaction is routed to an agent.
If no agent is available, the interaction is queued until an agent becomes available.

The interaction is sent to the agent for an appropriate response.
The agent decides if the interaction requires private comments.

The user searches on Twitter or Facebook for the company’s handles and tweets or posts a message, which could be related to an issue being faced or a query targeted to customer care.
The application monitors the Twitter and Facebook handles through pre-defined events and filter messages based on keywords to determine the next action.
The application verifies if the corresponding contact already exists in the Contact History. The user is identified in the Contact History by their Facebook or Twitter handle (if available).
If the user does not exist (that is, social handles are not associated with a registered user), the application creates a user in the Universal Contact Database based on available data. Any further messages and agent replies are stored under this user.
The application then verifies if the day is a normal operational day. If not, a special day message is sent stating that the user’s query will be answered once the service is back online. The special day message is sent as a public message or a private message.
The application has the ability to determine if the operating hours of the service match the current time and day – if not, a standard message is sent in response stating that the query will be answered once the service is back online. This message is sent as a public message or a private message.
In addition, it is possible to define an emergency message that will be sent either as a public message or a private message, if the emergency process is activated.
If within operating hours on a regular day, the application searches for an available agent with the correct skills.
1. If an agent is available, the interaction is routed to an agent.
2. If no agent is available, the interaction is queued until an agent becomes available.
The interaction is sent to the agent for an appropriate response.
The agent decides if the interaction requires private comments.