New in 8.1.4

{{{{{TMPL8}}} |Release=8.1.4 |Draft= |New=

• An Orchestration/Interaction Server protocol extension enhances the mechanism of getting the appropriate interactions for processing from Interaction Server. With enhanced pulling, the pull mechanism uses the strategy name and allows different priorities to be set for different types of interactions. This enhanced pull mechanism can result in improvements in performance and reliability. For more information, see the Orchestration Server 8.1.4 Deployment Guide, topic Interacting with eServices, section Pulling Multimedia Interactions from Interaction Queues.

  Notes:

  • The enhanced pulling functionality requires Composer 8.1.4 and Interaction Server 8.5.1. Other eServices components can be 8.5.0.
  • ORS retrieves the SCXML-based routing application from an application server and an interaction process diagram for this SCXML-based application must be published into Configuration Server using Composer 8.1.4.

• Orchestration Server supports Submitter objects configured in Composer. Submitters supply parameters that control how Interaction Server submits multimedia interactions to Orchestration Server.

• An Orchestration Server protocol extension supports the attachment of Virtual Queue data to multimedia interactions. The attached user data can then be used by a Reporting Solution, such as Genesys Info Mart. This feature requires Universal Routing Server 8.1.4. For more information, see the Orchestration Server 8.1.4 Deployment Guide, topic Interacting with eServices, section Reporting on Virtual Queues.

• Orchestration Server supports activation/deactivation of any specific routing strategy.

• Orchestration Server can now directly connect to Configuration Server and pull data. For example, when executing the GetListItemValue function, Orchestration Server can pull data without going through Universal Routing Server.

• Orchestration Servers configured as an HA pair can automatically synchronize voice treatment request data, thereby ensuring a smooth switchover.

• Orchestration Server can now terminate a session when the ixn.redirect action is successfully completed, and there is no other associated interaction attached to that session during the configured timeout. This functionality is enabled by the new Application-level option, ixnfm-idle-session-ttl, in the orchestration section.

The following new features were introduced in the June 2015 CD update of Orchestration Server:

• You can now monitor Orchestration Server performance using a set of performance-related counters and configure conditions that will both trigger and clear Management Layer alarms.
• A new detach attribute for the ixn:redirect action, which controls whether ORS should detach an interaction from the current session before routing to the specified target.
• A new option, http-verbose, which can be used to control the volume of HTTP Request logging.
• ORS can now request data directly from Stat Server instead of going through Universal Routing Server.
• A new resultof property is added to the interaction.notcontrolled event to provide a reason for a session not being able to control an interaction that it owns.
• A new option, getlistitem-binary-conversion, defines how binary-formatted Transaction List item attributes will be treated by the function _genesys.session.getListItemValue(list, item) when item is returned as an OBJECT of key/value pairs.
• Orchestration Server now supports Red Hat Enterprise Linux 6 and Windows Server 2012 native 64-bit.
• A new option, mcr-pull-cycle-quota, allows you to define how many multimedia interactions ORS will request to be pulled from queues in a given pulling cycle during enhanced pulling.
• ORS adds the capability to specify a reasons property in the hints attribute for the ixn:redirect action.
• ORS supports Debug Logging Segmentation, which provides more precise control of the logging when the log-trace-segments option is configured.
• Several performance improvements in the SCXML documents processing minimize session-creation time.
• Two new configuration options, max-assembled-cache-age and assembled-cache-reload-threshold, allow users to fine-tune the behavior of the Assembled Document Cache.
• ORS supports voice call and Open Media interaction User Data properties represented by a key-value pair of Unicode or Binary type.

}}